Continuous runtime tracing
Every request, job, and queue event is traced with sub-millisecond overhead — no sampling games, no blind spots between services.
Nimbus watches your services at runtime, learns what normal looks like for each endpoint, and blocks anomalies before they reach production — with traces your engineers can actually read.
SOC 2 Type II · 2,400+ engineers in the beta · one-command install
Capabilities
Most teams bolt a security tool onto an APM and reconcile two timelines at 3 a.m. Nimbus does both jobs from one agent.
Every request, job, and queue event is traced with sub-millisecond overhead — no sampling games, no blind spots between services.
Nimbus profiles each endpoint for seven days, then denies out-of-profile traffic at the edge — every block tagged with a plain-English reason.
Investigate without leaving the CLI you already live in: nimbus trace, nimbus block, nimbus explain.
How it works
No rules to write, no dashboards to babysit. Nimbus earns its keep in the first week.
One line in CI — or a single Helm chart — adds the Nimbus sidecar to every service. No code changes, no config files.
For seven days Nimbus profiles what normal means per endpoint: traffic shape, payloads, dependencies. Thresholds tune themselves.
Out-of-profile requests are denied at the edge and logged with a full context trace, so on-call trusts the block instead of fighting it.
From the beta
“We cut mean time-to-resolution from 40 minutes to six. Blocks arrive with a reason string attached, so on-call actually trusts them.”
“Nimbus replaced two tools and a spreadsheet of regex rules. Setup took one afternoon, and the traces read like our own logs.”
Pricing
Free while the beta runs. Upgrade when your pager agrees.
For side projects and kicking the tires.
$0per user / month
For production teams on call.
$29per user / month
For regulated and self-hosted stacks.
Customannual contract
FAQ
During a seven-day profiling window the agent builds a per-endpoint baseline of traffic shape, payloads, and dependencies. No rules, no regex — the baseline comes from your real production behavior and re-validates on every deploy.
Yes. On the Enterprise plan the control plane and trace store run fully self-hosted or inside your VPC. The agent is a single static binary, and no trace data ever leaves the boundary you define.
Every block ships with a full context trace and a reason string. One click adds a scoped allow rule, and the feedback folds back into the baseline — blocks are logged, reversible, and never silent.
Still have questions?
Join the public beta and get the full Team plan free until 1.0 — one command to install, and your feedback shapes the roadmap.
No credit card · SOC 2 Type II · Cancel anytime
Tell us about your stack and we’ll reply within one business day.