Appwrite Cloud's Pro plan is designed for professional developers or development teams that need to build applications at scale. When applications outgrows Appwrite's Starter plan organizations can switch to Pro plan to continue growing its apps. You can learn more about Pro plan on the pricing page.
Create a Pro plan organization
Appwrite's plans are applied to an entire organization. Get started with a Pro plan organization by visiting the pricing page and click Start building or create a new organization from the Appwrite Console and select Pro plan.
<!-- ## Trial Every Appwrite Pro plan organization starts with a 14 day free trial. The first billing period will start after the trial ends. -->
Switch to Starter plan
Head to the overview of your organization through the profile menu on the top right of your Appwrite Console. Under the Billing tab, you can click Change plan to update your organization's plan.
Resource limits
Each plan in Appwrite Cloud has a set of resource limits. You can find the details of these resource limits in the in the pricing page.
Additional resources are automatically purchased when your orgnization goes over the resource limits to continue scaling until the budget cap is reached. Each resource limit is applied per billing period and resets at the beginning of each billing period.
Budget cap
Appwrite allows organizations to set budget caps when using a Pro plan. Appwrite will automatically scale Pro plan projects as they require more resources. Budget caps limit the amount of automatic scaling and prevent unexpected bills.
Organization budget caps can be set by navigating to the organization's Billing tab, under Budget cap, toggle and set a budget cap. Appwrite will send emails to warn organization memebers when near the budget cap.
Check resource usage
You can check your organization's resource usage for the current billing cycle by navigating to your organization, under the Usage tab.
Reaching resource limits
Reaching your organization's resource limits will have the following effects until the current billing period ends.
| Component | Consequence |
| Bandwidth | More bandwidth will be purchased automatically until your organization reaches a budget cap. If the organization uses a Starter plan or a budget cap is reached, API access will be denied until your organization's plan is upgraded or your budget cap is increased. |
| Importing projects via migrations disabled, but you can still export your projects. | |
| Platform creation disabled. | |
| Users | Creating new accounts and team invitations disabled. |
| Compute | Function executions are disabled. |
| Realtime | Realtime subscriptions disabled. |
| Storage | File uploads are disabled. Persists across billing periods until the amount of storage used is below the plan limit. |
Switching to Starter plan and reaching limits
When an orgnization switches from Pro or Scale plan to Starter plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period. After the billing period ends, the Starter plan limits and consequences will apply.
If an organisation has multiple members after the billing period ends, all admins besides the original creator of the organization will be removed. The following consequences should also apply at the project level if the Starter plan per-project resource limits have been exceeded.
| Component | Action |
| Platforms | If more than 3 platforms have been created, disable them in order of date created (oldest ones first). |
| Webhooks | If more than 2 webhooks have been created, disable them in order of date created (oldest ones first). |
| Teams | If more than 100 teams have been created, disable them in order of date created (oldest ones first). |
| Databases | If more than 1 database has been created, disable them in order of date created (oldest ones first). |
| Buckets | If more than 3 buckets have been created, disable them in order of date created (oldest ones first). |
| Functions | If more than 5 functions have been created, disable them in order of date created (oldest ones first). |