Join the rolling development program.

Named Operator License — unlimited systems

One license is assigned to one natural person who directly administers, operates, or customizes Bus Engine. That named operator may use the preview on an unlimited number of servers, virtual machines, containers, clusters, and other systems for personal or commercial purposes. Hosted application users and billing administrators who only purchase or assign seats do not consume paid operator seats.

Each license includes one individual account for official release access, updates, documentation, and customer issue-tracker support. Shared accounts are not permitted, and organizations may reassign licenses when an employee leaves or changes role.

Immediately after purchase

• Founding customer account and checkout enrollment.
• Current Bus Engine CLI, API, artifact, VM, QEMU, agent-runtime, and local-model integration documentation.
• Access to the development-preview communication and support path.

Development-program access

Founding customers receive continuously updated development builds through the development channel. These builds are pre-production. The development preview is not a complete production version of Bus Engine OS, and interfaces or formats may change.

AI access and support boundary

AI model access is configured separately. Third-party hosted-model usage, hosted agent access, local inference infrastructure, and other AI service fees are not included unless a plan explicitly says otherwise. Customers must provide a model backend supported by the deployed Bus AI integration modules. Unsupported providers require integration work before they can be used.

Support is best effort during the development preview. There is no production SLA, and rollback, recovery, update, installation, and production image guarantees are provided only after those capabilities are implemented, tested, and included in the applicable release terms.

Source, binaries, and release materials

The monthly subscription includes the Bus Engine product-line codebase under the Functional Source License. That Bus-owned code converts to the MIT or Apache 2.0 license two years after each covered version is released.

The one-time option includes the current Bus Engine product-line codebase under the MIT or Apache 2.0 license at purchase, plus one year of updates under the Functional Source License. Those update versions follow their included license terms.

Bus Engine OS release areas are expected to provide binary artifacts, checksums, package manifests, corresponding source for covered open-source components, patches, build definitions, license texts, copyright notices, third-party notices, and source-access instructions to the release recipients. Bus Engine does not offer source code publicly by default.

These FSL, MIT, and Apache 2.0 terms apply only to Bus-related code licensed by us. Third-party software keeps its own license terms. Proprietary BusDK userspace products remain binary-only where legally permitted. Open-source component licenses control where they conflict with commercial terms.

Founder persistent storage

Founding preview plans include a Bus Engine Persistent Storage allocation when that entitlement is shown in checkout or the written agreement. The allocation is for supported BusDK-hosted virtualized systems and is managed independently of individual development virtual machine rebuilds.

The checkout or written agreement defines the included capacity, duration, retention, export, backup, transfer, data-location, and additional-capacity terms. This page does not advertise lifetime hosted storage, perpetual hosted storage, high availability, backups, replication, transfer limits, throughput, IOPS, or zero data-loss guarantees.

Commercial terms still govern

The checkout and written agreement control billing, taxes, renewal, support, and entitlement details. The intended commercial model includes named-operator access, development-channel participation, and access to relevant Bus Engine release materials. Any broader BusDK binary-catalog entitlement must be confirmed in the final commercial terms before it is treated as a contractual deliverable.