> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/faq/billing.md).

# Billing

Tessell uses a simple, transparent consumption-based billing model. You are only charged for what you use, and services can be stopped or started at any time.

***

## How does billing work?

Services are **metered hourly** and **billed monthly**. There are only two meters:

| Meter                    | What it covers                           | How it's priced                                                                             |
| ------------------------ | ---------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Database Service**     | Any running database managed by Tessell  | Hourly rate based on the compute shape selected                                             |
| **Availability Machine** | Snapshots, backups, and transaction logs | No charge for up to **150%** of the storage provisioned for the associated database service |

> **Note:** The 150% free storage applies per database service. For example, if a database service has 100 GiB of provisioned storage, up to 150 GiB of Availability Machine storage (snapshots, backups, and transaction logs combined) is included at no charge.

***

## What counts as a running Database Service?

A database service is counted as a running service — and billed — whenever it is in an active (running) state. If you stop a service, billing for the Database Service meter pauses. Availability Machine billing continues as long as associated backups and snapshots are retained.

***

## How is the Availability Machine billed?

The Availability Machine covers all snapshots, backups, and transaction logs managed by Tessell for a given database service. Storage up to 150% of the provisioned database storage is included at no additional cost. Any storage above that threshold is charged based on the GiB-month consumed.

***

## Are there discounts available?

Yes. Tessell offers:

* **Volume discounts** — for organizations running a large number of database services.
* **Time-commitment discounts** — for committing to a usage period in advance.

To learn about bulk and reserved pricing, [contact Tessell Sales](https://tessell.com/contact-sales?query=Bulk/Reserved%20Discounts).

***

## Frequently asked questions

**Q: Is there a minimum commitment?** No. Tessell is pay-as-you-go with no minimum commitment. You can stop services at any time to stop incurring Database Service meter charges.

**Q: How is the compute shape linked to billing?** Each compute shape has an associated hourly rate. Larger shapes (more vCPUs and RAM) have higher hourly rates. You can scale your compute shape up or down and billing adjusts accordingly.

**Q: Where can I view my current usage?** Usage and billing details are visible in the Tessell portal. Contact your Tessell account team for detailed billing reports or invoice copies.

**Q: What happens to billing when I stop a database service?** Database Service metering stops when a service is stopped. Availability Machine metering continues if backups and snapshots are retained. Deleting a service and its associated Availability Machine stops all billing for that service.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tessell.com/tessell/faq/billing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.