Introducing Usage + Operations Update

Full lifecycle visibility for every Nirvana resource

Usage is generally available today. Operations now shows you exactly what changed on every update. Both in the dashboard, API, and SDKs — built for teams operating Nirvana at scale.

TL;DR

Usage (new): every VM, volume, and IP, broken out by vCPU, memory, GB, and public IPs, tagged per project, with start and end timestamps.

Operations (upgraded): every Create, Update, and Delete is logged with its duration and outcome. Updates now include field-level diffs — see exactly which fields changed, with from and to values side by side.

Both available in the dashboard, the API, and the SDKs.

What's in it

Usage is a complete, dimensional view of what you're running on Nirvana. Resource-level detail, project-level attribution, time-bounded down to the second a resource started and ended.

Operations, which has logged every Create, Update, and Delete since launch, just got a lot sharper. Open any Update and you'll now see a Changes tab with field-level diffs — the autoscaling flip from true to false, the rename, the tag swap — each one displayed side by side with its prior value.

The same data flows three ways: the dashboard for teams that want to look, the API and SDKs for teams that want to build.

What Usage is for

Know what each project costs. Every resource carries a Project tag, so you can see — at a glance or via the API — exactly which team or workload is driving your spend. Run chargeback and showback cleanly. Tie spend to a launch, a quarter, a customer environment, or a single product line.

Build on top of the data. The API and SDKs give your platform team a real source of truth to integrate with. Pipe Usage into Datadog and treat billing as an observability signal. Send it to Snowflake for historical analysis. Wire it into your internal billing tool to reconcile against project budgets in real time.

Bill your own customers with precision. If you're an AI infrastructure company, GPU reseller, or managed-services provider operating on top of Nirvana, dimensional usage exposed via API is what you need to bill your end-customers, allocate margin, and honor SLAs.

What's new in Operations

Debug incidents faster. When something breaks, the first question is "what changed?" Operations always gave you the what and the when. Now it gives you the what specifically — the exact field, the prior value, the new value, all in one place.

Coordinate across teams. When more than one person can touch infrastructure, you need a shared, specific record of what was done. Operations is that record — now with the field-level detail that turns "someone updated the cluster" into "autoscaling was disabled at 4:08 PM."

Build change-management workflows. With change diffs exposed via API, you can wire mutations into Slack, PagerDuty, or your CI/CD pipeline — and your alerts can be specific to the fields that matter. Notify only when production tags change. Flag any time autoscaling is set to false outside the change window.

Together: a defensible record

For SOC 2 reviews, internal audits, and incident postmortems, Usage and Operations are the inventory and the change log. "What was running on the cluster at 03:47 UTC, and what changed in the hour before?" is now two API calls. Compliance gets an evidence trail. SRE gets a postmortem source. The data is real, queryable, and yours.

Try it

→ [Open the dashboard] · [Read the docs]

Nirvana: Modern Cloud for Real-time Workloads

Ultra-fast Block Storage with High IOPS, powering blockchain, AI and real-time systems.

Learn more at Nirvana Labs

Nirvana Cloud | Pricing | Blog | Docs | Changelog | Twitter | Telegram | LinkedIn