Crates

Riverbase is one Cargo workspace. All crates release together under one version, so pin them to the same revision. Every crate is added as a git dependency:

cargo add riverbase_core riverbase_proc riverbase_http --git https://github.com/riverbase-io/riverbase

Core

Kernel and macros every service needs.

riverbase_coreCommand and query engines, domains, Postgres datastore, audit log, message bus, configuration.riverbase_procProcedural macros: #[domain_action] and riverbase_namespace!.

HTTP

The axum portal: routes, auth, policy, realtime.

riverbase_httpRiverbaseApp, generated routes, OpenAPI, JWT/OIDC auth, Casbin, WebSocket, SSE, RxDB.

Extensions

Capabilities you add when a domain needs them.

riverbase_taskWorker runtime and job tracker: consume bus messages, record jobs.riverbase_fileMedia management over OpenDAL: filesystem, S3 or HTTP storage plus metadata.riverbase_formDeclarative forms, elements and document templates with validation.

Which crates do I need?

Building	Add
An HTTP service with domains	riverbase_core, riverbase_proc, riverbase_http
A worker that consumes bus messages	riverbase_core, riverbase_task
File uploads and downloads	+ riverbase_file
Declarative forms and document templates	+ riverbase_form

Dependency rules

Edges point only toward riverbase_core. Extension crates never depend on riverbase_http, so workers and CLIs stay free of axum. The full list is in Crates and features.