Integrations
Cloud, AI, GPU, Data, Monitoring, Database, Networking, Hosting, DevOps, and Billing. 23 cost sources are live today. On the event side, GitHub, GitLab, Salesforce, Jira, PagerDuty, Stripe Subscriptions, Vercel Deployments, Linear, Sentry, and News annotate your timeline independently of any cost data, and2 usage sources carry your own customers' consumption in to divide that spend by. 35 live sources in total, plus a FOCUS importer for everything else.
AWS
Cloud
Anthropic
AI
Hetzner
Cloud
GCP
Cloud
Azure
Cloud
DigitalOcean
Cloud
Scaleway
Cloud
OpenAI
AI
HuggingFace
AI
LambdaLabs
GPU
Paperspace
GPU
RunPod
GPU
Databricks
Data
Snowflake
Data
Confluent Cloud
Data
Datadog
Monitoring
MongoDB
Database
Neon
Database
Cloudflare
Networking
Fastly
Networking
Vercel
Hosting
GitHub Billing
DevOps
Stripe
Billing
Coming soon
A dedicated connector will never exist for every vendor you use. FOCUS is the FinOps Foundation's open billing-data standard, and it's how the rest get in. Point Plutus at the export a provider already publishes and it lands in the same charts, breakdowns, budgets and tags as everything above. No waiting on us to build it.
Custom (FOCUS Spec)
One importer covering every FOCUS-conformant provider: Temporal, Confluent, Modal, PlanetScale, Linode and the rest of the long tail.
Not every bill has an API. A Salesforce contract, an annual reserved-instance commitment, whatever your vendor only sends as a PDF. Enter the name and monthly amount once and it's folded into your totals automatically, every cycle after.
Manual recurring cost
No credentials, no sync. Just a name and a flat monthly line item that repeats.
Overlaid on the cost chart, so a spend spike arrives with an explanation attached.
GitHub
Annotate cost charts with PR merges and releases.
GitLab
Same idea, for teams shipping out of GitLab instead.
Salesforce
Onboarding, churn, opportunities, contracts and orders on your charts — plus won revenue and new customers as units to divide cost by.
Jira
Line up sprint and release activity with what it cost.
PagerDuty
See which incidents came with a spend spike attached.
Stripe Subscriptions
Overlay new and canceled subscriptions on cost charts.
Vercel Deployments
Overlay production deploys on cost charts.
Linear
Overlay newly created issues on cost charts.
Sentry
Overlay newly reported errors on cost charts.
News
Overlay vendor price changes, deprecations and capacity notices on cost charts, from any RSS or Atom feed you track.
Coming soon
Cost alone tells you what you spent. Pair it with what your own customers actually consumed and you get margin per customer, per plan, per feature. Push it from your backend, or let Plutus pull it from the metered-billing system you already invoice through.
Custom API
Stream your own end-customer usage events in from your backend — for spend that comes from no provider at all.
Metronome
Pull metered usage per end-customer and billable metric, straight from Metronome.
Coming soon
Everything above is about getting cost data in. Once it's here, it doesn't stay locked to how the provider billed it, or to this account at all.
Your data, in a format that isn't ours
Cost history exports as CSV under FOCUS column names, the FinOps Foundation's open vocabulary, on paid plans. Your spreadsheet, warehouse, or whatever you use next reads it without a translation layer. Leaving should cost you an afternoon, not a quarter.
The number your accountant recognises
An upfront Reserved Instance payment lands as one enormous day and eleven quiet ones. Switch any view to amortized cost and it spreads across the term it actually bought, so the trend reflects what you consumed rather than when you happened to be charged.
Bring your own client and ask about your spend in plain language.
AI
Connect Claude, ChatGPT, or Gemini with an MCP key and ask about your spend directly, scoped to one account. Read-only by default, optionally read-write.
Learn more→
