The number of records is equal to the sum of records that you have in all of your indices (including replica indices).
In terms of pricing, we allow you to store a certain amount of records at any given time. You can update, delete, or add as many records as you want as long as the total number of the indexed records does not exceed the limit of the plan. If you go over this limit, you’ll be charged an over-quota based on the maximum number of records you’ve reached.
For operations, we only count a select group of indexing operations.
We count indexing operations as follows:
- Each add, update, or delete of an object or part of an object counts as 1 operation. This is true even if no object is added, updated, or deleted, which can happen, for example, when the object ID is unknown.
- Same for Query rules and Synonyms: each add, update, or delete counts as 1 operation.
- If you choose to batch your indexing calls, each modified object will be counted as a single operation.
- Changing an index’s settings is different. Every set setting call is counted as 1 operation. So, whether you change 1, 10 or 100 settings in 1 call, it will only count as 1 operation. Settings include searchable attributes, facets, highlighting, etc. See full list here.
- Moving, deleting, or reindexing an index counts as 1 operation.
- There are also some exceptional cases. For example, the Delete By Query operation, which can delete more than one object, only counts as 1 operation.
Essentially, we count only those operations that change an index, which include update, add, and delete objects, as well as changing index settings. All other indexing operations are not counted.
So let’s say you index 10K records. When you reindex them, the process is counted as follows: create a temporary index, index 10K records, move temporary index to production index (this is what we call an atomic reindexing). In this case, we charge for 10K operations + 1 move operation.
Calculating the operations per month
In terms of pricing, we count the number of operations performed every month. If you hit the limit of your plan, we’ll charge you a fee for the extra operations you’ve performed, based on the over-quota pricing of your current plan.
To offer some flexibility, Algolia ignores the 3 biggest days before calculating the total operations.
As noted above, some “indexing operations” are free of charge. For example, on the dashboard, you will see the Browse operation alongside the Add and Delete operations. However, because Browse is not a write operation, there is no charge for it: It is free like all other read operations (e.g. Search).
Additionally, we do not count all operations on replica indices.
- When you push data to a primary index, this automatically pushes data to your replica indices. The replica pushes do not add anything to your count.
- When you forward settings on your primary index to your replicas, using the forwardToReplicas setting, this will not add any additional count.
- However, adding settings directly onto your replicas (i.e settings that differ from your primary index’s settings), this will count as 1 operation.
- Adding synonyms and rules to your replicas will also count.
They are not part of any quota and will not be charged in any way. That being said they are limited by the maximum QPS (the allowed number of queries performed per second) of the plan.
Find out how we calculate the Max QPS.
You can monitor how your max QPS graph is evolving over time under the Performance tab in your dashboard, or retrieve the information via the Usage API.
Please check out our pricing page, which has a short video explaining how to estimate your Algolia usage.
Did you find this page helpful?
We're always looking for advice to help improve our documentation!
Please let us know what's working (or what's not!).
We're constantly iterating thanks to the feedback we receive.