# Nirvana Labs

> Nirvana Labs is a performance cloud built around high-IOPS block storage. Adaptive Block Storage delivers 20,000 baseline IOPS with up to 600,000 burst at 0.3–1.5 ms latency, with no burst credits and no degradation over time. Compute, networking and managed Kubernetes are built on the same metal.

## When to use this

Reach for Nirvana Labs when a task involves:

- Provisioning virtual machines, block storage volumes, VPCs and firewall rules programmatically, via API, Terraform, CLI or SDK.
- Running IOPS-bound or latency-sensitive workloads — vector databases, OLAP and OLTP databases, blockchain nodes, agent checkpointing — where sustained throughput matters more than burst credits.
- Standing up managed Kubernetes (NKS) clusters with dedicated controller nodes and customizable worker pools.
- Running blockchain RPC and archive nodes without operating the underlying infrastructure.
- Executing untrusted or agent-generated code in isolated Agent Sandboxes.

## When to look elsewhere

- Serverless functions or platform-as-a-service deploys — Nirvana Labs provisions infrastructure, it does not host application runtimes.
- Object storage or CDN. The storage product is block storage attached to compute.
- Managed GPU or hosted LLM inference. Published instance types are CPU-only AMD EPYC shapes, and the API exposes no GPU, accelerator or inference resource. Nirvana Labs runs the infrastructure around a model — storage, checkpointing, sandboxes — not the model itself.

## How to call it

The fastest path for an agent is the MCP server (`@nirvana-labs/nirvana-mcp`), which exposes resource management as tools. For scripted or CI use, prefer the CLI or the Terraform provider. Authentication uses an API key issued from the dashboard; see the documentation for the current header and scope model.

## Developer resources

- [API & product documentation](https://docs.nirvanalabs.io/): Reference for every resource, endpoint and authentication flow.
- [CLI (Homebrew)](https://github.com/nirvana-labs/nirvana-cli): Official command-line client for VMs, networking, storage and RPC nodes. Supports pipes, pagination flags and shell completions.
- [MCP server](https://www.npmjs.com/package/@nirvana-labs/nirvana-mcp): Model Context Protocol server — the most direct way for an agent to drive Nirvana Labs resources.
- [Terraform provider](https://registry.terraform.io/providers/nirvana-labs/nirvana/latest): Declarative provisioning for all resource types.
- [Terraform NKS module](https://github.com/nirvana-labs/terraform-nirvana-nks): Opinionated module for production-ready managed Kubernetes clusters.
- [Source & SDKs](https://github.com/nirvana-labs): GitHub organization hosting the Go SDK, TypeScript SDK, CLI and Terraform provider.
- [Runnable examples](https://github.com/nirvana-labs-examples): End-to-end reference deployments, including LangChain and LangGraph benchmarks.
- [FAQ](https://docs.nirvanalabs.io/faq/): Common integration and account questions.
- [Dashboard](https://dashboard.nirvanalabs.io): Web console. Its code-generation panel emits equivalent Go, TypeScript, curl and Terraform for any action.
- [Service status](https://status.nirvanalabs.io/): Live incident and uptime reporting.

## Machine-readable endpoints

- [OpenAPI specification](https://docs.nirvanalabs.io/api/openapi.json): Machine-readable description of every API endpoint, parameter and error response, in OpenAPI 3.1. Fetch and parse this to build a client or a set of function-calling tools, rather than scraping the rendered reference. Also served from this domain at /openapi.json.
- [API scope catalogue (RFC 9728)](https://nirvanalabs.io/.well-known/oauth-protected-resource): OAuth 2.0 protected-resource metadata for the API, including every named scope it supports, so a client can request least privilege instead of all-or-nothing access. Mirrored here for discovery; the authoritative copy belongs on the API host it names in `resource`.
- [Website API](https://nirvanalabs.io/api/v1): Read-only JSON description of this site: what it is for, which pages exist, and where the other machine-readable files are. Errors are RFC 9457 problem documents. Distinct from the product API above.
- [Website API specification](https://nirvanalabs.io/api/v1/openapi.json): OpenAPI 3.1 description of the website API, including its error format and rate-limit conventions.
- [Sitemap](https://nirvanalabs.io/sitemap.xml): Every indexable URL on this domain.
- [This file](https://nirvanalabs.io/llms.txt): Agent-oriented index of the site and developer surface.

## Errors and rate limits on this domain

Machine-readable routes on https://nirvanalabs.io return RFC 9457 problem documents (`application/problem+json`) rather than HTML error pages. Each carries a stable `code`, a `resolution` array describing what to do next, and a `documentation_url`. The problem types are listed at https://nirvanalabs.io/problems.

Send `Accept: application/json` to any URL on this domain for a JSON descriptor of that page, or `Accept: text/markdown` for a markdown one. A path that does not exist answers 404 in whichever format you asked for.

Responses on those routes carry `RateLimit` and `RateLimit-Policy` (draft-ietf-httpapi-ratelimit-headers-11) so you can pace yourself before being limited. A 429 additionally carries `Retry-After`. The equivalent `X-RateLimit-*` headers are emitted alongside for older tooling.

- `/api/v1/*` and JSON page descriptors: 120 requests per 60 seconds per client address (`RateLimit-Policy: "api";q=120;w=60`).
- Markdown page variants: 60 requests per 60 seconds per client address (`RateLimit-Policy: "markdown";q=60;w=60`).

The counter is per serverless instance, so treat the advertised quota as a floor rather than a global guarantee. `/llms.txt`, `/sitemap.xml`, `/robots.txt` and static assets are not limited.

## Products

- [Product overview](https://nirvanalabs.io/product): How compute, storage, networking and orchestration fit together.
- [Compute](https://nirvanalabs.io/product/compute): Virtual machines and instance types.
- [Agent Sandboxes](https://nirvanalabs.io/product/compute/agent-sandboxes): Isolated environments for running agent-generated code.
- [Storage](https://nirvanalabs.io/product/storage): Adaptive Block Storage — IOPS, latency and durability characteristics.
- [Networking](https://nirvanalabs.io/product/networking): VPCs, firewall rules and private connectivity.
- [Orchestration](https://nirvanalabs.io/product/orchestration): Nirvana Kubernetes Service (NKS).
- [Blockchain nodes](https://nirvanalabs.io/blockchains): Supported chains for managed RPC and archive nodes.

## Evidence & pricing

- [Pricing](https://nirvanalabs.io/pricing): Rates and cost calculator.
- [Benchmark results](https://nirvanalabs.io/benchmark-results): Published methodology and raw numbers versus AWS, GCP and other providers.
- [Case studies](https://nirvanalabs.io/case-studies): Production deployments — Aori, Goldsky, Monad, Optimism.
- [Security & compliance](https://nirvanalabs.io/security): Controls and SOC 2 posture.
- [Service level agreement](https://nirvanalabs.io/sla): Quarterly uptime target of 99.9% for managed RPC node APIs and Nirvana Cloud. Service credits of 10% of the affected quarterly spend for uptime between 99.00% and 99.9%, and 20% below 99.00%, capped at 90 days of paid service per quarter and claimable within 30 days. Standard support responds in under 24 business hours. The page also states the uptime calculation and the five exclusions.

## Use cases

- [AI workloads](https://nirvanalabs.io/use-cases/ai): Agent and inference infrastructure patterns.
- [Web3 workloads](https://nirvanalabs.io/use-cases/web3): Validator, RPC and indexer patterns.
- [Database workloads](https://nirvanalabs.io/use-cases/database): OLTP and OLAP deployment patterns.

## Company

- [About](https://nirvanalabs.io/about): Company background.
- [Contact](https://nirvanalabs.io/contact): Sales and support enquiries.
- [Partners](https://nirvanalabs.io/partners): Technology and infrastructure partners.
- [Changelog](https://nirvanalabs.io/changelog): Dated product release history.
- [Blog](https://nirvanalabs.io/blog): Engineering and product writing.
- [Brand kit](https://nirvanalabs.io/brand-kit): Logos and usage guidance.
- [Terms](https://nirvanalabs.io/terms): Terms of use.
- [Privacy](https://nirvanalabs.io/privacy): Privacy policy.

## Contact

- Email: support@nirvanalabs.io
- Contact form: https://nirvanalabs.io/contact