Rocketic
Cracker — day-2 cockpit for NATS
The same cockpit discipline as Concord, aimed at NATS instead of Patroni. Coming soon — in design, not shipped.
Coming soon — in design, not shippedNATS estates get highly available fast and hard to operate safely soon after. The nats CLI has the same gap patronictl had before Concord: you can inspect streams and consumers one command at a time, but there's no single place to see the estate, judge whether an operation is safe, and act on it behind guardrails. Cracker is Rocketic's answer for NATS — not sold yet, not promised on a date, but real enough to name.
How it will work
1. View the topology
See every cluster, stream, and consumer across a NATS estate in one board — the same 'see the estate' job Concord does for Patroni.
2. Inspect streams and consumers
Drill into lag, pending messages, and consumer health with live evidence before deciding anything needs to change.
3. Guarded publish and ops
Run publish, purge, or consumer changes behind a preflight → typed confirm → audit flow — never a bare command against production.
Concord for Patroni, Cracker for NATS
Same company, same bar, same discipline — evidence before action, guardrails on anything destructive, an audit trail after. Concord proved the pattern on Patroni PostgreSQL; Cracker applies it to NATS. Neither is a tech-stack pitch — both exist to make one operator job trustworthy.