Why AltBase exists and what it means to ship a Rust-first backend platform with operator-facing apps in the same workspace.

Introducing AltBase

AltBase exists because too many backend stacks force teams to choose between performance, control, and product completeness.

We wanted a platform where the control plane, generated data APIs, auth, storage, realtime, workflows, integrations, vector search, GraphQL, and operator-facing apps all live in the same workspace and share the same project model.

What makes AltBase different

The control plane and API assembly layer are written in Rust.
The repository includes both the backend and the operator-facing apps.
PostgreSQL, Redis, and NATS are explicit runtime building blocks rather than hidden implementation details.

Design target

AltBase is trying to be an actual backend platform, not just a collection of helper services around a database.

The current shape

Today the repo already includes:

a Rust control plane and API engine
a React dashboard
JavaScript, React, Python, and Dart SDKs plus a workflow SDK
a CLI with schema introspection and type generation

What comes next

The project is still alpha, so the focus is on tightening APIs, improving docs, and making contributor workflows more predictable.