Introduction

Plutus is a FinOps platform that pulls cost data from your cloud providers, AI/LLM vendors, and SaaS tools into one dashboard, and overlays it with a timeline of the business events (deploys, incidents, releases, customer churn) that often explain a spike.

Who this is for

Plutus is for teams whose spend is split across more than one provider — some mix of cloud infrastructure (AWS, GCP, Azure), AI/LLM vendors (OpenAI, Anthropic), data platforms (Snowflake, Databricks, MongoDB Atlas), and other SaaS tools. Each of those providers has its own billing console and its own invoice. Answering a question like “why did spend go up last week” normally means opening several of those consoles, reading the charts side by side, and separately trying to recall what shipped or broke that week. Plutus stores cost data from every connected source in one place and puts the events that tend to explain a change — a deploy, an incident, a big customer signing or churning — on the same timeline as the cost chart, so the two don’t have to be cross-referenced by hand.

Main navigation

After you sign in and connect at least one source, the sidebar has five main sections:

• Dashboard — a free-form canvas of widgets: spend by source, top cost movers, budget status, recent events, and other tiles. Tiles can be added, resized, or removed; layout is saved per account.
• Cost Explorer — the main cost chart, with breakdowns by provider, service, region, account, usage type, or a custom tag you’ve defined. This is where the event timeline overlay lives.
• Event Explorer — the business-event timeline on its own: deploys, incidents, releases, and customer lifecycle events (signups, churn) from every connected event source, searchable and filterable independent of any cost chart.
• Usage Explorer — usage telemetry pushed or synced in from your own backend or from a usage-metering provider (API requests, orders, active users), used as the denominator for unit economics like cost per 1,000 requests.
• Budgets — spend budgets scoped to the whole account, one cost source, one team, or one tag value, each with its own ok/warning/exceeded status and alert subscriptions.

The next pages in this section cover connecting your first source and reading the dashboard in more detail.