Introducing Basalt

Why rebuild infrastructure

Enterprise infrastructure has spent more than a decade living inside choices made for another era. Earlier platforms made virtualization widely accessible and proved that open infrastructure could serve demanding environments. But many of those platforms also accumulated layers of services, integrations, and operational dependencies that make the management system nearly as difficult to run as the workloads it controls.

Basalt started with a different question: what should hyperconverged infrastructure look like if it were designed today around security, resilience, and automation? That led us toward a smaller, more explicit management plane. The goal is practical: reduce the number of moving parts an operator must trust, patch, and understand during an incident.

Why Basalt uses Rust

Rust supports that goal by preventing broad classes of memory errors while providing predictable resource use for long-running infrastructure software. It also helps us ship software with fewer external runtime dependencies, which simplifies deployment in constrained environments. Cryptographic operations follow the same focused model: Basalt uses a centrally maintained implementation rather than allowing each feature to choose or assemble its own.

A focused control plane

The design separates a few clear responsibilities. The central management plane provides the API, authentication, orchestration, and shared source of truth. Software on each host compares intended state with local reality and applies the required changes. A dedicated delivery path handles large software images, resumable transfers, and narrowly scoped transfer authorization. These boundaries keep failures contained without creating a maze of services for operators to deploy and debug. For a deeper breakdown, see the platform design.

Intelligence-native direction

This focused shape makes infrastructure easier for software to reason about, not just for people to click through. The Model Context Protocol integration is part of that direction. Instead of placing a chatbot over existing dashboards, Basalt exposes capabilities with explicit context, constraints, and authorization boundaries. AI systems can inspect available actions, understand operational state, and propose or execute changes according to policy.

That is what we mean by intelligence-native infrastructure. The platform still has to be predictable where it counts: deterministic operations, auditable state changes, and clear failure modes. But the interface can become more capable. Basalt is being built so operators, automation, and AI systems all work from the same source of truth. For how that design holds up from a disconnected laptop to a global footprint, read the platform overview.