Datadog through Squiid

What Datadog is

Datadog is the comprehensive option. Agents on hosts and containers collect infrastructure metrics, APM traces requests across services with flame graphs, log management correlates lines with the trace that produced them, real user monitoring and synthetics cover the browser side, and LLM Observability tracks prompts, token usage, latency and quality signals for model calls specifically. Hundreds of integrations mean most of your stack reports in without custom code. Dashboards and monitors are defined in the UI or as code, and notebooks are used for incident analysis after the fact.

For AI-coded products the LLM observability piece is the interesting one, because it answers questions ordinary monitoring cannot: which prompt version is slower, where tokens are being spent, which chain step fails most often. The rest of the platform is relevant once an application has several services and a real user base, and overkill before that. Cost is the other consideration, because a Datadog bill can grow faster than the infrastructure it monitors if ingest is not managed.

Why connect it through Squiid

Datadog is on the Squiid roadmap. When it lands, Squiid will provision the organization, hold the API and application keys, and route ingest and query calls through https://api.squiid.io/v1/datadog/... with Authorization: Bearer $SQUIID_API_KEY, with SDKs and agents working by base URL swap (gateway convention). Hosts, ingested spans, logs and custom metrics will bill at Datadog's listed price on one Squiid invoice, which at least puts observability spend next to the infrastructure spend it is watching. Tags are the organising principle across every product, so a consistent tagging scheme decides how useful the platform becomes.

• One account, one key, one bill, one dashboard. Datadog sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Datadog credentials. Your code carries SQUIID_API_KEY, so DD_API_KEY, DD_APP_KEY, DD_SITE, DD_SERVICE never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Datadog costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Datadog organization with keys held by Squiid
• Metrics, APM traces and correlated logs
• LLM observability for prompts and token usage
• Real user monitoring and synthetic checks
• Datadog list pricing, no markup

How to connect Datadog

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces DD_API_KEY, DD_APP_KEY, DD_SITE, DD_SERVICE
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/datadog/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Datadog charges per host, per ingested and indexed log, per span and per custom metric across its products, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Datadog usage, with no markup and no per-request margin.

Datadog has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Datadog usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: historical data is exported where Datadog supports it and the project is re-created in your own account, with new events going to your own keys. Squiid never owns your code, your schema or your domain, and the gateway speaks Datadog's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Datadog through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Datadog usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.