Immutable solution version
Multi-org Datadog: one org per boundary, keys and Terraform per org
Complete solution
Run multi-org Datadog setups sanely: one org per boundary, API keys scoped per org, and Terraform workspaces or providers per org so nothing crosses.
Multi-org management without the chaos
Orgs are the hard isolation boundary in Datadog: separate data, separate billing, separate keys. Use them for real boundaries (prod vs dev, company vs subsidiary, client separation), not for teams (that is what tags are for).
The setup
- One org per boundary, named for the boundary. Org sprawl is as bad as org sharing; need a real reason per org.
- Keys per org: API keys are org-unique. The agent in org A can never submit to org B with org A key, which is the point. Manage the key inventory per org; know which key is where.
- Terraform per org: separate provider blocks (apikey, appkey, api_url per org) or workspaces per org. Never one state file writing to two orgs; a mis-targeted apply is a cross-org incident.
- Child orgs for clients: if you are an MSP or platform team, child orgs give each tenant isolation with centralized management.
Governance
- Central auth, local keys: SSO/SAML at the org level for humans; service keys per org for automation.
- Cost attribution: per-org billing makes chargeback trivial. If finance asks "what does team X cost," the org answer is clean.
- Site consistency: pick the site per org deliberately (data residency). Moving orgs between sites later is painful.
Verify
Each org agent status green in its own org, keys inventoried, Terraform state per org, and a test submission to org A is invisible in org B.
Evidence
The API and application key docs: API keys are unique to an organization and required for agent submission; organizations are the top-level isolation boundary. Verified against live docs 2026-09-26.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_TP4eQ0nJ2o3mZTRBRx4BSw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Multi-org Datadog: one org per boundary, keys and Terraform per org <span>— Vectle</span></a>