What the editions share

Both editions provide event streams, versions, subscriptions, and projections. The main differences concern clustering, security integration, and operations.

Chronacta has no artificial event-count cap. Practical capacity still depends on hardware, workload, storage growth, and recovery requirements.

Chronacta: single node
Enterprise: high availability, security, integrations, disaster recovery
Chronacta supports single-node deployments. Enterprise adds capabilities for multi-node operations.
AreaChronactaEnterprise
DeploymentSingle-node applicationsMulti-node deployments
TopologySingle nodeHigh availability and replication
Stream APIAppend, read, read-all, list, and informationCore stream API and multi-node operations
SubscriptionsTransient and durableConsumer groups and additional delivery capabilities
ProjectionsBuilt-in projections: create, rebuild, result, and stateAdditional runtimes and diagnostics
Schema registryRegistration, retrieval, listing, and basic validationAdditional compatibility and governance capabilities
Identity and accessLocal users and rolesSSO, OIDC, LDAP, and extended role-based access control
Transport securityUnencrypted gRPC; TLS through a reverse proxyBuilt-in TLS and a production security profile
Backup and recoveryLocal backup, restore, export, and importRemote backups, scheduling, and disaster-recovery tooling
Data integrationExport and importPostgres read models, connectors, and NATS ingress
Gateways and administrationCLI and gRPCREST and WebSocket gateways, administrative UI
ObservabilityExternal process and infrastructure monitoringMetrics, tracing, and multi-node diagnostics
Multi-tenancyNot includedTenant management and quotas
Developer interfacesChronacta CLI and gRPCEnterprise CLI, gateways, and SDK publishing

Start with a single-node server

Chronacta supports event appends, reads, subscriptions, built-in projections, local backups, and data export. It can serve development and production workloads that fit a single-node deployment.

You operate the process and storage, configure external transport protection when needed, and provide monitoring and recovery procedures.

Extend your operational capabilities

Enterprise adds replication and high availability, corporate identity integration, remote backup management, additional integrations, and administrative tooling.

Evaluate these capabilities against your availability targets, security requirements, and recovery procedures. A cluster still requires deliberate deployment and operation.

Application
Chronacta
Postgres
NATS / Kafka
Chronacta stores the event history the application designates as authoritative. Postgres and message brokers may remain external read-model stores or transport.

Consider Enterprise when you need

  • replication, high availability, and visibility into replication lag;
  • built-in TLS and a production security profile;
  • SSO, OIDC, or LDAP integration;
  • scheduled remote backups and disaster-recovery tooling;
  • Postgres read-model integration and inbound connectors;
  • consumer groups and additional delivery controls;
  • additional projection runtimes and diagnostics;
  • tenant management and quotas.

Choose Enterprise for capabilities your deployment requires. Growth in event count alone is not a licensing trigger, but it can change capacity and recovery requirements.

How to choose

  • Choose Chronacta when a single node and externally managed operations meet your requirements.
  • Evaluate Enterprise when you need high availability, corporate identity integration, or additional recovery and administration tools.
  • Measure before deciding using realistic event sizes, write and read workloads, consumer lag, and restore or rebuild times.

Software licensing

Software editions and support tiers are separate choices. Enterprise software capabilities and commercial support commitments are not interchangeable.

  • Chronacta: $0 for the single-node edition. Review the source-available license included in the repository for usage terms.
  • Chronacta Enterprise: contact us to discuss licensing for your deployment.

Support tiers

Community support is provided on a best-effort basis through public issues. Standard, Premium, and Enterprise support offer commercial response commitments. See the operations documentation for the support matrix.

A support agreement defines assistance and escalation terms. It does not add Enterprise capabilities to the Chronacta single-node server.