Datadog spend is doubling year-over-year and the team is locked in by hundreds of dashboards and alert rules.
Datadog is the most common 'help us escape this' conversation we have, and the friction is real. Hundreds of dashboards, hundreds of monitors, custom tagging conventions, on-call routing rules, APM-instrumented services. A naive cutover loses visibility; a parallel-run is expensive. Most teams put off the migration for another year, and the bill grows another 50%.
Nova's migration path is dual-run by default. You ingest into both systems, build out Nova while Datadog stays live, then cut over once everything is green.
If your services already emit OTel, Nova consumes them with no code change. If they don't, the OTel collector pattern means a one-time instrumentation effort that's portable to any future backend.
Nova translates Datadog dashboard JSON, monitor definitions, and tag schemas into native Nova equivalents. Manual touch-up is for nuances; the bulk is automated.
Run dual-stack for two weeks, switch alerting to Nova, leave Datadog in shadow for another two weeks, then turn off the Datadog billing. Total time, six weeks for a typical mid-size shop.
Get Started Free, cancel anytime. Or book a 30-minute walkthrough with a founder.