Guide
Every pricing plan comes with a certain amount of monthly AI credits, automation runs, and integration syncs included in the subscription:
| Free | Standard | Pro | Enterprise |
AI | — | 250 credits
per paid seat | 500 credits
per paid seat | 1,000 credits
per paid seat |
Automations | 250 runs | 1,000 runs
+ 100 per paid seat | 10,000 runs
+ 1,000 per paid seat | Unlimited |
Integrations | 5,000 entity syncs | 25,000 entity syncs
+ 2,500 per paid seat | 250,000 entity syncs
+ 25,000 per paid seat | Unlimited |
If you need more, you can either upgrade to the next plan or (on Pro and Enterprise) enable extra usage.
Curious why the limits were introduced? Check out our blog post.
How are the limits calculated?
Fibery is a collaborative platform, so we scale your limits as you invite more people. For example, a 10-person workspace on the Pro plan will have 10,000 + 10 × 1,000 = 20,000 automation runs a month while a 50-person one will get 60,000 runs.
That being said, the pool of credits, runs, and syncs is workspace-wide. For example, a 25-person Enterprise workspace gets 25,000 AI credits, and they can all be consumed by a single tokenmaxxxer as there's no 1,000 per-user cap.
We only take paid seats (Admins and Members) into account when calculating limits, ignoring Observers and Guests.
During a Pro trial, each workspace gets:
500 AI credits
10,000 automation runs
250,000 entity syncs
The quotas are per calendar month and are not tied to your billing cycle. At the start of each month, the counters go back to zero (this applies to the annual plan as well).
What are the measuring units?
AI credit is consumed every time any user or automation asks Fibery AI to do something. A really basic query costs about 5 credits, while a typical one costs around 20.
Automation run happens every time a Rule is actually executed (filtered "runs" don't count) or a Button is clicked. In case an automation is triggered for multiple entities, it's processed in batches of 50 — each batch representing a single automation run.
Entity sync happens every time an integration creates, updates, or deletes an entity in Fibery based on the change in the source data.
Where do we check how many we have left?
For the % of AI credits, automation runs, and integration syncs left in the current calendar month, navigate to Help & Support → Workspace status at the bottom of the sidebar:
Other (rare) limits are either displayed in-place like for finding patterns:
Do we get notified if we are getting close to a limit?
For automations and integrations, we send two warning notifications to all workspace Admins:
75% of the limit reached before the 20th day of the month;
90% of the limit reached before the 25th day of the month.
We also display a sidebar banner to Admins suggesting an upgrade to the next plan:
What happens if we reach a limit?
When you use all of your monthly quota for a given service, it stops working:
AI stops taking queries.
Automation Rules stop running, and Buttons fail when users click them.
Integrations stop syncing data from external tools.
The rest of the workspace remains fully operational.
There are two ways to get the affected service up and running again:
upgrade to the next plan;
enable extra usage (on Pro and Enterprise).
Or you can always wait until the next calendar month starts and the limits are reset :zhdun:.
How do we go beyond plan limits?
Extra usage is available on Pro and Enterprise plans.
If you find yourself in the middle of a month no AI credits, automation runs, or integration syncs left, you can enable extra usage in Settings → Extra usage:
Here are the costs:
Service | Price per 1000 units, $ | Price per 1000 units, € |
AI credits | $15 | €15 |
Automation runs | $5 | €5 |
Integration syncs | $0.5 | €0.5 |
Set a monthly spending cap (e.g. €30 → 2000 AI credits per month) and continue your normal operations.
Once a calendar month is over, you'll be charged only for the amount used (e.g., €20.48), not the entire cap. There will be an extra invoice in your billing settings.
What can the monthly cap be?
The minimum cap is €5/$5 and the maximum is €1000/$1000. If you need more than that :muscle_right:, let us know.
Also, if you've already enabled extra usage and consumed, say, €25 worth of items a given month, you can't set your monthly cap to anything lower than that. If you want to make it €15 instead, do it at the start of the next month.
How do you decide when to tap into extra usage?
Whenever AI answers a query, an automation runs, or an integration syncs, we always try to tap into the pool of credits/runs/syncs that are included with the plan first. If the limit has been reached, then we tap into extra usage.
Note that the number of paid seats might fluctuate a lot during a month, and so can the credits/runs/syncs limit. We always decide if we should take items from the plan limit or tap into extra usage at the moment of consumption. Here's an example:
Event | When | Limit | Extra usage |
Month starts | May 1 | 0/5000 | 0/1000 |
Plan limit reached | May 17 | 5000/5000 | 0/1000 |
Extra usage consumed | May 17-20 | 5000/5000 | 250/1000 |
Paid seats: 10 → 15 | May 20 | 5000/7500 | 250/1000 |
Plan limit reached (again) | May 25 | 7500/7500 | 250/1000 |
Extra usage consumed (again) | May 25-27 | 7500/7500 | 600/1000 |
Paid seats: 15 → 2 | May 27 | 7500/1000 | 600/1000 |
Extra usage limit reached | May 31 | 7500/1000 | 1000/1000 |
What happens to extra usage if we downgrade or cancel?
The moment you stop having a Pro or Enterprise subscription (e.g., when their billing period comes to an end after a cancellation), the extra usage automatically resets to $0.
Note that if you're on annual plan, there can be months between the moment you cancel your subscription and the moment it actually expires. You can benefit from extra usage during this period.
How do we avoid reaching the limits?
Most workspaces (at least those on paid plans) shouldn't worry about the monthly limits since the caps only affect the heaviest of users. However, if you find yourself approaching a certain limit, there are things you can do to optimize your usage.
You always have a choice between optimizing your setup or enabling extra usage.
Automations
To lower the number of automation runs:
if you use the same Button to update many entities at a time, select them all (e.g. in a Table View) and click the Button once: for 100 entities, it's going to be 2 automation runs (50 entities per batch) instead of 100 runs when clicking the Button 100 times for each entity;
make sure your script actions work effectively with an array of incoming entities, as we can batch up to 50 entities together for a single automation run.
If none of the optimizations save you enough syncs/runs or you don't think they are worth your time, upgrade to the next plan for much higher or even unlimited quotas.
Integrations
A few caveats before we proceed to giving advice:
if the same entity is updated 3 times during one month, it counts as 3 entity syncs;
it doesn't matter if an entity changed a little (just one Field) or a lot (ten Fields) since the last update: in any case, it is still considered a single entity sync;
if an entity hasn't changed since the last update, it's not counted towards entity syncs;
imported (as opposed to synced) entities are not counted towards the limit.
To lower the number of entity syncs:
filter the data source by excluding old or irrelevant data;
sync less often;
if you use a custom connector via Create Custom Integrations, make sure you have a delta sync that avoids unnecessary data updates.
Adding a new field in the source system does not trigger a new full sync in Fibery by default.
If you want Fibery to capture and store data from that new field, you’ll need to:
Go to your integration configuration in Fibery.
Run a full sync so that all existing entities are updated with values for the new field.
Regular syncs will continue as usual for the fields you already selected.
FAQ
How are runs counted in chained or multi-step automations?
Each AI call inside your workflow counts as a separate run — even if triggered by one button or automation chain.
Button → AI Call 1 → AI Call 2 → AI Call 3
➡️ 3 runs (one for each AI step)
➡️ 5 runs total
Each step that invokes the AI counts individually toward your monthly quota.