Platform

Platform overview

A Type 1, bare-metal platform built on KVM and implemented primarily in Rust, with one control plane and one operating model from a single node to a global footprint.

The architecture

Four domains under one control plane

Compute, storage, networking, and governance run under one architecture, not four products stitched together after the fact.

  1. 01The corebuilt on standards, not around them

    KVM is the virtualization core almost everyone else in the industry already runs. Basalt is not reinventing it, VMware is the one running something else. The control and security layer above it is written in Rust for its memory safety and performance, which rules out whole categories of memory-corruption vulnerability by construction.

  2. 02Native hyperconvergenceno proprietary hardware

    There is no separate storage appliance to buy or qualify. Basalt runs on a computer: storage and compute together, out of the box.

  3. 03The control planeglobal view, regional independence

    One global control plane sees every managed region on a single screen, but a link to that control plane going down does not touch a single running host: each region keeps operating on its own.

  4. 04The agent modeloutbound only

    Each host runs one agent that calls out to the control plane on its own schedule: nothing calls in. There is no inbound port to open or firewall exception to grant per host.

  5. 05What runs on itcompute, storage, networking, governance

    Four domains under a single architecture rather than four products stitched together.

Go deeper

We'd rather you catch an issue here than after you sign

Worried about trust? Security is below. Worried about price? Licensing is below. Worried about the move itself? Migration is below. Go pull on the details before you sign anything, not after.

Security & trust

Outbound-only management, audit depth, and certification status stated precisely.

Pricing & licensing

Deployment-scoped licensing, so consolidating does not create a new penalty.

Migration & evaluation

Prove Basalt beside the incumbent before the organization commits to anything.
Two ways to get started

Run the numbers, then try the platform

Run the numbers with your own infrastructure, then put Basalt beside your incumbent in a controlled environment, with a rollback story written down before anything moves.

Run the numbersPlan a controlled evaluation