---
title: Plans
description: Compare the Hobby, Pro, and Team plans.
order: 0
---

Atlasflow has three plans. Every plan uses the same underlying [usage rates](/docs/billing/usage-and-credits.md); the differences are the included credits, region support, log retention, support, and reliability targets.

## Comparison

|                                                    | Hobby            | Pro                | Team                                     |
| -------------------------------------------------- | ---------------- | ------------------ | ---------------------------------------- |
| Monthly minimum                                    | $5               | $20                | $100                                     |
| Included usage credits                             | $5 / mo          | $20 / mo           | $100 / mo                                |
| Workspace seats                                    | Single developer | Unlimited          | Unlimited                                |
| Regions                                            | Single           | Single             | [Multi-region](/docs/networking/regions.md) |
| [Build machine tiers](/docs/guides/build-machines.md) | Standard         | Standard, Enhanced | Standard, Enhanced, Performance          |
| Deployment replicas                                | 1                | 1                  | 2                                        |
| [Log history](/docs/observability.md)                 | 7 days           | 30 days            | 90 days                                  |
| Availability target                                | —                | 99.9%              | 99.99%                                   |
| Support                                            | Community        | Atlasflow Support  | Support SLOs, Slack Connect              |

After your included credits are used in a billing period, you're only charged for resource usage beyond them. See [Usage and credits](/docs/billing/usage-and-credits.md).

## Which plan should I choose?

- **Hobby**: side projects and experiments by a single developer.
- **Pro**: production applications and small teams that want larger builds and a higher availability target.
- **Team**: teams shipping at scale that need multi-region, two replicas per deployment, the largest build machines, longer log retention, and support SLOs.

## Replicas and availability

The **Team** plan runs **two replicas** of each deployment, which improves resilience and is the basis for the higher availability target. Hobby and Pro run a single instance per deployment.

## Changing plans

Upgrade or downgrade from your workspace billing settings. Plan-gated features (build tiers, regions, replicas) take effect according to your active plan. See [Managing billing](/docs/billing/managing-billing.md).

## Next steps

- [Usage and credits](/docs/billing/usage-and-credits.md): the per-second rates and how credits work.
- [Managing billing](/docs/billing/managing-billing.md): subscribe and manage payment.
- [Pricing](https://atlasflow.com/pricing): plans and an interactive cost estimator.