How Billing Works
Your Algolia plan is billed monthly. At the beginning of each month, you pre-pay for the upcoming month’s of service and pay any overages you encountered in the month that just passed.
Our enterprise customers can pre-pay for a year to receive a lower cost and can pay by credit card, check or bank transfer. All of our customers can pay by credit card.
Switching Between Plans
You can switch between plans at any time. Simply go to the Current Plan section of your dashboard.
We provide all of our potential customers with a 14-day trial, with no credit card necessary. This allows you to test out Algolia and see if meets your need with no commitment.
The trial is based on our Pro plan and includes:
- Unlimited domains and indices
- Up to 50 million operations
- Up to 5 million records
- Access to the analytics module
- Full support and consultation
If you’re not happy, we’re not happy. At any point during your subscription, reach out to us and let us know how we can make it right.
However, if you decide to leave Algolia you can do so at any time. Our Pro, Growth, and Starter plans pay month by month and are not required to commit to a subscription. Our Enterprise plans have the option of pre-paying for a longer period of time.
To cancel your account, send an email to firstname.lastname@example.org.
Different Sites, Domains, and Environments
For all of our plans, there is no domain or app limitation. Use the same or different indices across all of your sites and apps.
We do not offer any discounts for development or staging environments. In order to provide the same performance on features on non-production environments, we need to use the same hardware setup and so a discount is not possible for this.
What we recommend is to use the same account and application for all environments and generate a new set of indices and API keys.
As an example, your app can have the indices
Then, you can generate API Keys for each environment by limiting their access to indices having the prefix ‘dev_’, ‘staging_’ and ‘prod_*’. If you want to minimize the impact on pricing, we recommend to only index a subset of your records in your non-production environments.
Counting Records and Operations
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 giving 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 reached.
For operations, we count search and indexing operations equally.
The Search operations:
- Each individual full-text search counts as an operation. If you implement a search-as-you-type experience, each keystroke represents one operation.
- If you decide to batch queries, say for instance you want to query 2 indices at a time, it will use 2 operations.
- For disjunctive faceting, the number of operations equals 1 + the number of refined disjunctive facets (because we’re performing additional queries to display the associated facet counts).
The Indexing operations:
- Each add, update or delete of an object or part of an object counts as 1 operation.
- If you chose to batch you indexing calls, each object modified will be counted as a single operation.
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.
Logo Requirement on the Hacker Plan
The Hacker plan is a plan we’ve announced to support small projects and give back to the community. All that we ask is a link back to Algolia via a logo next to the search bar letting the world know that your search is powered by Algolia. Have questions about this? Send us an email at email@example.com.
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.