Your Observability Stack Costs More Than Your Infrastructure. Here's the Math.

Last month a founder sent me his AWS bill. $2,400. Then he sent me his Datadog bill. $1,850.

He was spending 77% of his infrastructure cost just to see what his infrastructure was doing.

This isn't an edge case. We've been running Quave for 13 years, managing cloud infrastructure for hundreds of small and mid-size engineering teams. This pattern shows up every single week.

The tools work great. The pricing doesn't.

How observability pricing actually works (and why it catches everyone)

A team of 8 picks Datadog or New Relic. Solid choice. Best tools in the market.

They start with infrastructure monitoring. $15/host. Reasonable.

Two weeks later someone adds APM because they're debugging a performance issue. $31/host. Still manageable.

Then logs, because you can't diagnose without them. $0.10/GB. Doesn't sound like much.

Then custom metrics because the default dashboards don't show what you actually need to see.

Eighteen months later the bill is $1,500/month and nobody on the team can explain exactly when it crossed $1,000.

We've watched this happen to our own customers before they migrated to us. It's also a recurring theme on r/devops and Hacker News. "Datadog pricing surprise" has become its own genre. Multiple front-page threads. Hundreds of comments. Same story every time.

The tools aren't bad. They're excellent for companies with 200 engineers and a dedicated platform team managing the observability pipeline.

For a team of 8, it's renting a 747 to fly across town.

What small teams actually pay in 2026

Based on publicly available pricing (Q1 2026), here's what a 10-person team running 10 hosts with moderate log volume pays per month:

Datadog (Infrastructure Pro + APM + Log Management): $700-1,500
New Relic (Pro plan, 8 users, 200GB data): $550-800
Grafana Cloud (Pro): $200-500
AWS CloudWatch (detailed monitoring + logs + dashboards): $75-200
Quave ONE (8 zclouds, hosting + observability included): $60

The tool cost is only half of it.

Someone has to configure dashboards, tune alerts, set up log pipelines, maintain integrations. For small teams, that's one engineer spending 15-20% of their week on it. Roughly $30K/year in engineering time that doesn't show up on any invoice.

Total cost of observability for a small team: $40-50K/year.
Total cost on Quave ONE: included at $0 extra.

Why we built it differently

For small teams, observability isn't a separate concern. It's infrastructure. You can't separate them without creating complexity that requires a dedicated person to manage.

So we didn't separate them.

When you deploy an app on Quave ONE, you get Prometheus metrics and Grafana dashboards automatically. CPU, memory, disk, response times, error rates, deploy markers. All there from deploy one. No setup. No configuration. No extra cost.

Three things that make this work:

1 - One screen instead of five. Logs, metrics, alerts, and deploy markers in the same interface. Instead of correlating timestamps across CloudWatch, Datadog, PagerDuty, and Slack, you see a deploy marker on the same graph as a latency spike. Root cause is obvious. PagerDuty's State of Digital Operations reports show median MTTR at 1-4 hours for most organizations. One screen cuts that dramatically.

2 - Opinionated defaults. We don't ask you what to monitor. We know what matters for your stack and we monitor it from deploy one. You can customize later. Most teams never need to.

3 - MCP-powered infrastructure control. This is where it gets interesting. Through the Model Context Protocol, you can connect Quave ONE to Claude, Cursor, or any MCP-compatible AI tool and manage your entire infrastructure through conversation.

Not just diagnostics. Actual operations.

"What's causing slow response times?"
→ "Database connection pool saturated at 100/100. Recommend increasing pool size or optimizing long-running queries on the /reports endpoint."

"Scale up the API service to 4 instances."
→ Done. Blue/green deployment triggered. Zero downtime. New instances healthy.

"Roll back the last deploy on staging."
→ Rollback complete. Previous version restored. Health checks passing.

"Show me what changed in the last 24 hours across all environments."
→ Summary of 3 deploys, 1 config change, CPU spike on worker at 03:12 correlated with cron job.

Diagnostics, deployments, scaling, rollbacks. All through natural language. For a team without a dedicated SRE, this turns your AI coding assistant into your ops team.

Who runs on this

QuickCoach (online coaching platform, 32,000+ professionals, 150,000+ managed clients) reduced hosting costs by 10x.

Caught (location-based platform, hundreds of thousands of daily users) cut infrastructure costs by 75-80%. Quote from their team: "We save 75 to 80% of our server running costs, and on top of that, receive better service."

CerradoX (VC-backed startup) scaled without hiring a dedicated DevOps engineer.

Ronald from CerradoX on our MCP integration: "Today I was debugging a deploy failure with Luciano and the speed this enables for interaction with agents is massive. You nailed it with this MCP."

How pricing works

$7.50/month per zcloud (0.5 GB RAM + 0.5 vCPU). Everything included:

• Full-stack hosting (apps + databases)
• Blue/green zero-downtime deployments
• Support for MongoDB, MySQL, PostgreSQL, Redis, RabbitMQ, Kafka, OpenSearch, Metabase, Typesense
• Full observability: logs, metrics, Grafana dashboards, alerts
• MCP integration for AI-powered diagnostics, deployments, scaling, and rollbacks
• Free white-glove migration

A typical small team app runs on 6-10 zclouds: $45-75/month. That includes the observability that would cost $700-1,500/month on Datadog alone.

One number. Predictable. No surprises when you check your logs more often during a rough week.

If your team is under 15 engineers, observability shouldn't be a separate project. It should just be there.

No credit card required. No sales call. Deploy in 5 minutes: quave.one

---

Common questions about cloud observability for small teams

What is cloud observability?

Cloud observability is understanding what's happening inside your infrastructure through logs, metrics, traces, and alerts. It goes beyond "is it up" monitoring to "why did it break and how do we fix it."

How much does observability actually cost for a small team?

Using standalone tools like Datadog or New Relic, a 10-person team typically pays $700-1,500/month. Add engineering time for setup and maintenance and total cost hits $40-50K/year. Platforms like Quave ONE include observability in the infrastructure price at no extra cost.

What's the best observability tool for startups?

Depends on team size. Under 15 engineers, an all-in-one platform that includes observability with hosting (like Quave ONE) is more cost-effective than assembling separate tools. Larger teams with dedicated SRE can justify Datadog and New Relic's deep customization.

What is MCP in cloud infrastructure?

MCP (Model Context Protocol) is a standard that allows AI tools like Claude and Cursor to interact with external systems. In cloud infrastructure, MCP lets you manage your entire stack through natural language. Not just ask questions, but deploy, scale, roll back, configure, and diagnose issues, all from your AI coding assistant.

How do I reduce cloud observability costs?

Three ways: consolidate tools into one platform instead of paying for 3-4 separate services, choose predictable pricing over per-GB/per-host models, and use a platform with built-in observability so you're not paying extra to monitor the infrastructure you're already paying for.

Datadog vs New Relic vs Grafana: which is cheapest for small teams?

Grafana Cloud is typically cheapest ($200-500/month) with a generous free tier and open-source options. New Relic ($550-800/month) is more predictable than Datadog ($700-1,500/month) due to its usage-based model. All three are significantly more expensive than platforms that include observability in the hosting price.