Browse documentation

Explanation

Native Rust integration

Put work outside the managed profile behind an explicit host interface.

Native Rust components connect the managed core to existing libraries, platform APIs and computation outside the profile. They have their own build process, OS permissions and failure behaviour.

Native components can use async libraries. Concurrency, actors and async Rust explains how they work alongside Septa.

The Services host

The Services host handles transport framing, authenticates incoming requests and connects adapters in ordinary Rust. Business operations run in the managed profile. The host calls the runtime through the public CLI and ops/v1 JSON.

HTTP / CLI / MCP
        │
        ▼
Native Rust host
  transport + authentication + adapters
        │ public runtime interface
        ▼
Managed operations
  typed inputs + decisions + durable state

The diagram shows what each component handles.

Define the integration contract

Specify request and result types, authenticated context, authority on each side, timeouts and retry behaviour. An existing SDK’s dependencies and credentials belong to the native component’s trusted boundary.

Floating-point computation, threads and OS APIs can live there. Their results cross an explicit interface. Native code does not automatically inherit the core’s bounds, determinism, effect enforcement or durable continuations.

Use a supported integration

A capability declaration does not implement its external operation. The Services host above is implemented. A native-driver specification does not mean an SDK for arbitrary handlers is available.

A crate that fits the supported profile can use the managed library workflow. Other crates need an integration design. Arbitrary Cargo dependencies are not drop-in core extensions.

For calls that may have acted before a timeout, follow external-effect handling.

Search concepts, guides and reference.