Skip to content

Latest commit

 

History

History
91 lines (54 loc) · 2.57 KB

resource-limits.md

File metadata and controls

91 lines (54 loc) · 2.57 KB

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 Free 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 Free plan and reaching limits {% #switching-to-free-plan-reaching-resource-limits %}

When an orgnization switches from Pro or Scale plan to Free 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 Free 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 Free 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 %}