---
title: "Capacity and billing"
description: "How Fabric capacity billing works for a deployed Rayfin app, and which operations consume Capacity Units and which do not."
url: https://rayfin.ai/docs/deploy/pricing
markdown_url: https://rayfin.ai/docs/deploy/pricing.md
section: deploy
product: Rayfin
sdk_version: 1.34.0
cli_version: 1.33.2
last_updated: 2026-08-22T22:02:07-07:00
source: deploy/pricing.mdx
---

# Capacity and billing

> How Fabric capacity billing works for a deployed Rayfin app, and which operations consume Capacity Units and which do not.

A Fabric app runs on Microsoft Fabric capacity. There are no additional Rayfin-specific
charges — you pay only for the Fabric capacity units (CUs) consumed by the services your
app uses.

## How billing works [#how-billing-works]

Fabric uses a universal billing model based on **Capacity Units (CUs)**. Every operation
performed by a Fabric app's child services consumes CUs from the Fabric capacity assigned
to your workspace.

Your workspace must have a Fabric capacity associated with it. CU consumption is tracked
in the
[Microsoft Fabric Capacity Metrics app](https://learn.microsoft.com/fabric/enterprise/metrics-app),
where you can monitor usage per item and per operation.

## What consumes capacity [#what-consumes-capacity]

A Fabric app uses three Fabric services that consume CUs.

### SQL Database [#sql-database]

| Operation                 | What it covers                                                                                                                                                             | Billing meter                                      | Type        |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ----------- |
| **SQL Usage**             | Compute for all SQL queries, modifications, and data processing — including queries from your app's GraphQL API and any queries you run in the Fabric portal query editor. | SQL database in Microsoft Fabric Capacity Usage CU | Interactive |
| **Allocated SQL Storage** | Dynamically allocated storage for tables, indexes, transaction logs, and metadata. Fully integrated with OneLake.                                                          | SQL Storage Data Stored                            | Background  |

One Fabric CU equals 0.383 SQL database vCores.

### GraphQL API [#graphql-api]

Every GraphQL query (read) and mutation (write) your app's `RayfinClient` makes consumes
CUs, at a rate of ten CUs per hour of request and response processing time.

| Operation | What it covers                                                                    | Billing meter                           | Type        |
| --------- | --------------------------------------------------------------------------------- | --------------------------------------- | ----------- |
| **Query** | Compute for all GraphQL queries and mutations performed against your data models. | API for GraphQL Query Capacity Usage CU | Interactive |

See
[Fabric API for GraphQL](https://learn.microsoft.com/en-us/fabric/enterprise/fabric-operations#fabric-api-for-graphql)
in the Fabric operations documentation for more detail.

### OneLake storage (static content) [#onelake-storage-static-content]

When static hosting is enabled, your built frontend assets (HTML, CSS, JS) are stored in
OneLake and served from a public URL. OneLake storage and the read/write operations that
serve that content consume CUs.

| Operation           | What it covers                                                              | Billing meter                              | Type       |
| ------------------- | --------------------------------------------------------------------------- | ------------------------------------------ | ---------- |
| **OneLake Read**    | Read operations when serving static content to end users.                   | OneLake Read Operations Capacity Usage CU  | Background |
| **OneLake Write**   | Write operations when deploying or updating static content via `rayfin up`. | OneLake Write Operations Capacity Usage CU | Background |
| **OneLake Storage** | Storage of static content files in OneLake.                                 | OneLake Storage                            | Background |

## What does not consume additional capacity [#what-does-not-consume-additional-capacity]

These Fabric app capabilities do not incur separate CU charges today:

* **Rayfin WebService** — the application backend service that handles API routing and
  authentication.
* **Authentication** — Fabric brokered auth (Entra SSO) sign-in and session management.
* **Deployment operations** — running `rayfin up` has no CU charge of its own, beyond the
  SQL and OneLake operations it triggers.

## Further reading [#further-reading]

* [Fabric operations](https://learn.microsoft.com/en-us/fabric/enterprise/fabric-operations)
  — the full list of Fabric operations and their capacity consumption rates.
* [Microsoft Fabric Capacity Metrics app](https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app)
  — monitor and understand your capacity usage.
* [Fabric apps](/docs/deploy/fabric-apps) — what a Fabric app is and the services that make
  it up.