-
Notifications
You must be signed in to change notification settings - Fork 297
Feat plans docs #311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat plans docs #311
Changes from all commits
8821084
cd95f2e
b56ce76
172ebe1
f226eeb
9a4ac1e
0002940
d62bb21
32c9bab
e2648ae
d61b2fd
037abae
bb1ba63
3cbeac7
486c0a5
57dd1f9
ffa43ce
01d9b34
ead6fb4
8b1d168
bf10560
f4957bf
6e96311
1f46bb9
e000faf
44c54b9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,61 @@ | ||
| ## Check resource usage {% #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-resource-limits %} | ||
| Reaching your organization's resource limits will have the following effects until the current billing period ends. | ||
| {% table %} | ||
| * Component | ||
| * Consequence | ||
| --- | ||
| * **Bandwidth** {% rowspan=3 %} | ||
| * 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. | ||
| {% /table %} | ||
|
|
||
| ## Switching to Starter plan and reaching limits {% #switching-to-starter-plan-reaching-resource-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. | ||
|
|
||
| {% table %} | ||
| * 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). | ||
| {% /table %} | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| --- | ||
| layout: article | ||
| title: Billing | ||
| description: Understand Appwrite's billing features, like budget caps, billing periods, taxes, and more. | ||
| --- | ||
|
|
||
| Appwrite allows you to configure billing per organization. | ||
| You can access your organizations billing information under the **Billing** tab of your organization. | ||
|
|
||
| # Plans {% #plans %} | ||
| You can view or change your organization's plan under the **Billing** section. | ||
| You'll also find the expected cost, as well as the start and end date of the current billing period. | ||
|
|
||
| ## Billing period {% #billing-period %} | ||
| Billing periods begin the day you change your plan, and lasts 30 days. | ||
| You resource limits are reset at the beginning of each billing period and you will be billed for your plan and usage on the last day of each billing period. | ||
|
|
||
| # Payment history {% #payment-history %} | ||
| You can view and download you past invoices under **Payment history**. | ||
| You can click the three-dots menu to view and download your invoices. | ||
|
|
||
| # Payment methods {% #payment-methods %} | ||
| Appwrite Cloud accepts credit and debit cards as payment methods and will bill the card at the end of each billing cycle. | ||
| Appwrite accepts Visa, Mastercard, American Express, Discover & Diners Club, China UnionPay, Japan Credit Bureau (JCB), Cartes Bancairies, and eftpos Australia. | ||
|
|
||
| # Billing addresss {% #billing-addresss %} | ||
| Your billing address will be displayed on your invoices and used when Appwrite Cloud bills your payment method at the end of a billing cycle. | ||
|
|
||
| # Tax ID {% #tax-id %} | ||
| If you'd like you or your company's tax ID displayed on your generated invoice, you can provide it under **Tax ID**. | ||
|
|
||
| # Budget cap {% #budget-cap %} | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should also talk about billing alerts here in a separate section
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When do we send alerts and can they be configured? I'll add a whole new section about all the alerts. |
||
| Appwrite allows you to set budget caps when on your organizations. | ||
| Appwrite will automatically scale your projects by purchasing add-ons as they require more resources. | ||
| Budget caps limit the amount of automatic scaling and prevent unexpected bills. | ||
|
|
||
| You can enable budget caps under **Budget cap**, toggle the option **Enable budget cap**. | ||
| You will be able to set a budget cap in USD. | ||
|
|
||
| ## Budget alerts {% #budget-alerts %} | ||
| When you enable budget cap, you'll be able to configure alerts under **Budget alerts** to warn you when you organization is near the budget cap. | ||
| By default, an email alert will be sent at 75% of the budget cap. You can add up to three check points that send budget alerts when reached. | ||
|
|
||
| # Redeem credit {% #redeem-credit %} | ||
| If you received a redeemable code for Appwrite Cloud credits, you can redeem them in the **Available credit** section. | ||
| When you redeem credit, the credit balance will be automatically applied to the next billing cycle. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| --- | ||
| layout: article | ||
| title: Enterprise | ||
| description: How Appwrite can accelerate enterprise development teams and provide custom support and hosting options. | ||
| --- | ||
|
|
||
| Enterprise development teams face unique challenges and have unique needs. | ||
| Appwrite can provide tailored solutions for enterprise customers with custom hosting, training, and support needs. | ||
|
|
||
| If you're interested to learn about what Appwrite can do for your enterprise development teams, [contact us](https://appwrite.io/contact-us) for more details. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| --- | ||
| layout: article | ||
| title: Open source | ||
| description: Learn how Appwrite supports open source projects by providing free credits and other benefits. | ||
| --- | ||
|
|
||
| Appwrite remains open source and continues to offer support to open source maintainers that build fundemental software that modern developers depend upon. If you've got a growing open source project that can use our help, we're here for you. | ||
|
|
||
| If your open source project has out-grown our free Starter plan, [contact us](https://appwrite.io/contact-us) to apply for a free Pro plan. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| --- | ||
| layout: article | ||
| title: Pro | ||
| description: Understand Appwrite's different pricing plans, behaviors, billing cycles, and limitations. | ||
| --- | ||
|
|
||
| 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](https://appwrite.io/pricing). | ||
|
|
||
| # Create a Pro plan organization {% #create-a-pro-plan-organizations %} | ||
| Appwrite's plans are applied to an entire organization. | ||
| Get started with a Pro plan organization by visiting the [pricing page](https://appwrite.io/pricing) and click **Start building** | ||
| or create a new organization from the Appwrite Console and select **Pro plan**. | ||
|
|
||
| ## Trial {% #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 {% #switch-to-pro-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 {% #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](https://appwrite.io/pricing). | ||
|
|
||
| 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 {% #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. | ||
|
|
||
| {% partial file="resource-limits.md" /%} |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| layout: article | ||
| title: Scale | ||
| description: Appwrite's scale plan helps you grow your app to any sized audience. | ||
| --- | ||
|
|
||
| Appwrite's Scale plan is designed for growing development teams and agencies with many organization members and large projects. | ||
| Appwrite's Scale plan is priced per organization instead of priced per member. | ||
| Scale plan organizations will receive substancially greater resource limits and dedicated support. | ||
|
|
||
| Appwrite's Scale plan is coming soon, stay tuned for future announcements or [contact us](https://appwrite.io/contact-us) for more details. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| --- | ||
| layout: article | ||
| title: Starter | ||
| description: Appwrite's Starter plan provides a generous free tier. Perfect for budding projects, hobbiests, and side-projects. | ||
| --- | ||
|
|
||
| Appwrite Cloud provides a free **Starter** plan to all developers to start building with Appwrite. | ||
| Appwrite Starter plan is a perfect for personal hobbby projects for students and professional developers alike. | ||
| Learn more about Starter plan's generous resource limits on the [pricing page](https://appwrite.io/pricing). | ||
|
|
||
| # Create a Starter plan organization {% #create-a-starter-plan-organizations %} | ||
| Appwrite Cloud's different plans are applied at an organization level with its resources shared by the organization's projects. | ||
| When you create your Appwrite Cloud account, a **Personal Projects** organization using the Starter plan is automatically created. | ||
|
|
||
| Each Appwrite Cloud account can only have one organization on the **Starter** plan, but you can create unlimited projects in the organization. | ||
|
|
||
| # Resource limits {% #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](https://appwrite.io/pricing). | ||
|
|
||
| Each resource limit is applied per billing period and resets at the beginning of each billing period. You cannot purchase additional resources under the Starter plan. | ||
|
|
||
| {% partial file="resource-limits.md" /%} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we disable the oldest ones or we disable the newest ones? for me it makes sense to disable the latest ones not the oldest ones
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lohanidamodar Depends on the behavior you implement. Let me know, I don't mind either way.