# Business package

The Business package is the premium package for production applications. It works in the same way as the Pro package, and adds features such as access to Ably's SOC 2 report, a HIPAA Business Associate Agreement, and faster support times.

## Features 

Business package users have access to the following:

* Access to all products: Pub/Sub, AI Transport, Chat, Spaces, LiveObjects and LiveSync
* WebSocket edge infrastructure in 11+ regions and 700+ PoPs
* SOC 2 compliant infrastructure, and access to Ably's SOC 2 report
* Analytics dashboards
* Email support with a Service Level Agreement (SLA) of less than 1 business day, and less than 4 business hours for impacted service
* A 99.999% uptime Service Level Agreement (SLA)
* A HIPAA Business Associate Agreement (BAA)
* [Datadog Lite](https://ably.com/docs/platform/integrations/streaming/datadog.md#lite) integration
* A branded Ably subdomain, for example `acme.realtime.ably.net`
* Regional routing constraints, for AUS, EU or US
* Guided onboarding with a Support Engineer

## Pricing and billing 

With the Business package you select the [MAU allowance](https://ably.com/docs/platform/pricing.md#allowance) you expect to need each month and pre-pay a single price that covers the package, support and your MAU allowance. You can choose [monthly or annual billing](https://ably.com/docs/platform/pricing.md#frequency).

| MAU allowance | Monthly billing | Annual billing |
| ------------- | --------------- | -------------- |
| 1,000 | $419 per month | $349 per month, $4,188 billed annually |
| 5,000 | $599 per month | $499 per month, $5,988 billed annually |
| 10,000 | $839 per month | $699 per month, $8,388 billed annually |
| 25,000 | $1,439 per month | $1,199 per month, $14,388 billed annually |
| 50,000 | $2,399 per month | $1,999 per month, $23,988 billed annually |

If you need more than 50,000 MAUs, [contact sales](https://ably.com/contact) to arrange a custom package.

Additional MAUs are charged at $0.05 per MAU and invoiced monthly in arrears.

## Limits 

[Compare the limits](https://ably.com/docs/platform/pricing/limits.md) associated with each package to see those available on the Business package.

## Support 

Business package support includes access to Ably support via email, with a Service Level Agreement (SLA) of less than 1 business day for general guidance and less than 4 business hours for service that is impaired or down. Guided onboarding is available through a Support Engineer.

## Change your package 

To change your package, MAU allowance or billing frequency:

1. Ensure you are the [account owner](https://ably.com/docs/platform/account/team.md).
2. Log in to your account and select [**Packages**](https://ably.com/accounts/any/package) from the account sidebar.
3. Select **Change your package**, then choose the package, MAU allowance and billing frequency you want.

Increases apply immediately. Decreases take effect at the end of your current month, or at the end of your 12-month term if you're on annual billing. Read about [how changes to your package are billed](https://ably.com/docs/platform/pricing/billing.md#change).

> **Note**
>
> To increase your MAU allowance beyond 50,000 per month, or if you require Enterprise-level features then [contact us](https://ably.com/contact?cta=enterprise_package) to discuss your options.

## Close your account 

You can [close your account](https://ably.com/docs/platform/account/team.md#close) at any time by first downgrading to the Free package.

> **Note**
>
> Be aware that this will permanently delete all information associated with your account.

## Related Topics

- [Free](https://ably.com/docs/platform/pricing/free.md): Explore the features of Ably's Free package.
- [Pro](https://ably.com/docs/platform/pricing/pro.md): Explore the features and cost of Ably's Pro package.
- [Enterprise](https://ably.com/docs/platform/pricing/enterprise.md): Explore the features of Ably's Enterprise package.

## Documentation Index

To discover additional Ably documentation:

1. Fetch [llms.txt](https://ably.com/llms.txt) for the canonical list of available pages.
2. Identify relevant URLs from that index.
3. Fetch target pages as needed.

Avoid using assumed or outdated documentation paths.