1. Start Chronacta

Use the chronacta/chronacta repository and follow its build and startup instructions. Configure a persistent data directory and connect a local client.

Keep an unsecured development instance limited to your local environment. Configure authentication and transport protection before exposing the service to other machines.

Practice creating and restoring a local backup before storing data you need to retain.

2. Implement an aggregate stream

Choose a stream identifier such as order-demo-1. Append an initial event using the API's new-stream condition, then append another event with the current expected version.

Read the events and reconstruct aggregate state. Attempt a second append with an outdated version and verify that it is rejected.

Test an uncertain append result by retrying the same request with the same idempotency key according to the API contract.

3. Add a projection and a subscriber

Use a transient subscription to observe events during development. Use a durable subscription when processing progress must survive a consumer restart.

Build an application-side projection that updates a small SQL table. Test duplicate handling and keep its checkpoint consistent with the derived data.

Rebuild the table from the event history. If you delete the read model, reset its processing position or create a separate rebuild consumer; a saved checkpoint does not rewind automatically.

Continue in the documentation

The quickstart covers initial setup. The Go SDK, CLI, and API references describe integration contracts. The operations documentation covers security, subscriptions, projections, backup, and recovery.

Chronacta: single node
Enterprise: high availability, security, integrations, disaster recovery
Chronacta supports single-node deployments. Enterprise adds capabilities for multi-node operations.