Browse documentation

Start here

What to build with Septa

Suitable workloads, reusable foundations and where native Rust fits.

Septa fits software whose important behaviour involves state, decisions, messages and work that must resume after interruption. It supports applications and reusable libraries. Frameworks and databases can build on the same runtime primitives.

Stateful applications

Use actors for responsibilities that keep receiving requests: orders, approvals, imports, accounts or job tracking. Typed messages define the interface; durable state records progress. This is familiar territory for Elixir and Erlang developers, with a different language and explicit authority model.

Actors can live in one runtime. A boundary does not require a microservice.

Domain services

Place an invariant with the actor that owns its state. Inventory can own stock and reservations; Checkout can own order progress. Other components request changes through typed contracts.

The Services architecture exposes managed operations through HTTP, CLI and MCP adapters in an ordinary Rust host. The host owns transport and authentication ingress; business rules execute in the managed profile.

Workflows and agents

Use durable progress for work that waits on a timer, a person or a tool result. An AI agent loop is one example; an approval workflow is another. Tool calls and provider requests cross effect boundaries with explicit retry and authority contracts.

Building agents is a runtime use case. Building with coding agents is the development workflow.

Libraries, frameworks and databases

The library workflow includes reusable Rust, declared consumers, tests and a watch loop. You can build domain libraries or higher-level frameworks on this foundation.

Graph is a temporal graph database library built on Septa. It stores temporal facts, supports indexed queries and uses durable storage with restart recovery. A complete query-and-rules language is planned separately. You could also build a web framework on these primitives; a Rails-like framework is not bundled.

Where the core is not a fit

Graphics, simulation and ML numerical kernels commonly depend on floating-point computation. The deterministic core excludes floats. Native Rust can supply those computations through an explicit integration boundary, with its own build process and authority.

Arbitrary Cargo crates are not drop-in managed dependencies. Cross-node execution, managed hosting and recovery after losing all local storage are separate capabilities.

Try a durable actor or a library. Read native integration for work outside the profile.

Search concepts, guides and reference.