Chronacta vs Enterprise
Chronacta is a lightweight single-node event store for real applications. Chronacta Enterprise adds high availability, built-in security integrations, and broader operational tooling as systems grow. The table below is a product comparison, not an artificial event-quota list.
| Area | Chronacta | Enterprise |
|---|---|---|
| Intended use | Real single-node applications | Multi-node / fleet production systems and teams |
| Topology | Single node | HA cluster / replication |
| Stream API | Append, read, read-all, list/info | Same core plus fleet-oriented operations |
| Subscriptions | Transient + durable (checkpoint, ack/nack, limited retry) | Consumer groups, fan-out, advanced delivery workflows |
| Projections | Builtin create/rebuild/result/state | Extended runtimes and operational diagnostics |
| Schema | Register/get/list + basic validation | Schema governance, richer compatibility and audit |
| Authentication | Local users/roles | SSO/OIDC/LDAP and advanced RBAC |
| Transport security | Plaintext gRPC; terminate TLS at a reverse proxy | Built-in TLS and Enterprise production security profile |
| Backup & recovery | Local backup/restore, export/import, verify | Remote backup, scheduling, retention automation, DR |
| Data integrations | Local export/import | Postgres read models, SQL generation, connectors, NATS ingress |
| Gateways & UI | None | REST/WebSocket gateways, Admin UI |
| Observability | Bring your own around the process | Metrics, tracing, fleet tooling |
| Multi-tenancy | Not included | Tenants, quotas, commercial controls |
| CLI / API / SDK | Chronacta CLI + gRPC | Full Enterprise CLI, gateways, SDK publishing |
When to upgrade
Section titled “When to upgrade”Move to Enterprise when any of these become real requirements:
- a second node, failover, or replication lag control;
- built-in TLS and an Enterprise production security profile;
- SSO / OIDC / LDAP for people and services;
- automated remote backup and disaster recovery;
- Postgres (or other) read models and inbound connectors;
- consumer groups or more demanding delivery semantics;
- richer projection runtimes and operational diagnostics;
- centralized multi-tenant operations, quotas, or commercial packaging.
Honest upgrade path
Section titled “Honest upgrade path”Chronacta is enough to run a real event-sourced application on one node and keep your data via local backup/export. Enterprise becomes justified when you need the reliability, security integrations, and operational capabilities the single-node edition deliberately omits — not because Chronacta hides an artificial event cap.

