Start
Free, Starter, Pro and Enterprise
What changes between the four plans: capacity, backups, support, Enterprise on your MongoDB or ours, and the paths of system collections that scripts must know about.
A service runs on one of four plans, all with the same API. The plan sets how much the service carries, whether it shares the machine with other services, and, on Enterprise, whether the MongoDB is ours or yours. You can move up at any time: see the last section of this page.
At a glance
| Free | Starter | Pro | Enterprise | |
|---|---|---|---|---|
Price |
€0 |
€9 a month, €90 a year |
€25 a month, €250 a year |
Tailor made |
Users at once, in a typical app |
About 5 |
About 25 |
About 100 |
Not capped: your nodes' |
Requests |
150 a minute |
750 a minute |
3,000 a minute |
Not capped |
Collections and storage |
20 collections, 500 MB |
50 collections, 2 GB |
100 collections, 8 GB |
Not capped by us |
Team members |
1 |
2 |
5 |
Not capped |
Semantic search |
|
|
|
Not capped, with vector indexes |
Document size |
512 KB |
1 MB |
1 MB |
16 MB, MongoDB’s own limit |
File size |
2 MB |
10 MB |
10 MB |
Not capped |
Emails a day |
200 |
500, or your own SMTP with no cap of ours |
2,000, or your own SMTP with no cap of ours |
Your own SMTP, not capped |
Infrastructure |
Shared |
Shared |
Shared |
A dedicated node, or several, in one region or many |
MongoDB |
Included, managed by us |
Included, managed by us |
Included, managed by us |
Yours or ours: Atlas, with shards where you need them, or any MongoDB 6 or later |
Backups |
None. A service idle for 40 days is deactivated. Its data is kept for 30 days, and support reactivates it on request. |
Daily, kept 7 days, restored on request |
Daily, kept 7 days, restored on request |
As designed with you |
Databases |
One |
One |
One |
As many as you like, with a selector in the console |
Features |
The ones in the console |
The ones in the console |
The ones in the console |
Also your own RESTHeart plugins |
Support |
Basic, by email, without a guaranteed time |
Standard, by email within 48 hours |
Standard, by email within 24 hours |
Production support, included |
Support tickets open at a time |
1 |
2 |
5 |
10 |
The full comparison and current prices are on the pricing page. The users figures assume 30 requests a minute for each active user: what a typical app makes with lists, details, writes and token renewals.
Over the requests limit, a request gets a 429 and the API stays online. Usage is never charged: the invoice is always the price of the plan.
Production support is an option for Free, Starter and Pro, at €99 a month or €990 a year per service; Enterprise includes it. An engineer of our team follows the service and answers questions on its use and problems in production within set times, one working day at most. With this option you can also pay by invoice and bank transfer.
Enterprise: built with you
Enterprise starts with a dedicated node in the region you choose. From there it grows with your app: several nodes, in one region or many, Atlas with shards where your users are, your own plugins on the nodes. We design it with you, and the price follows the design. To start, choose Enterprise when you create a service: the console opens a form to our team.
An Enterprise service runs on the MongoDB you choose. It can be one of yours, for example an Atlas cluster on AWS, GCP or Azure, whose connection string you give us when we set the service up. Or it can be one we run for you, sized for your data. On yours, Ulabase connects to it and never stores your data anywhere else. See Connecting your MongoDB for the steps and the network settings.
Paths that change on Enterprise
The console shows the same menu on every plan and uses the right paths for you. Scripts and app code that call the service directly must use these paths:
| Collection | Free, Starter and Pro | Enterprise |
|---|---|---|
Users |
|
|
Permissions |
|
|
GraphQL apps |
|
|
Schemas |
|
|
Aggregations and change streams |
In the collection’s metadata, |
The same, in the selected database: |
On Enterprise, every console page that works on collections shows a database selector at the top. The choice lasts for the session.
Moving up
From Starter to Pro the service keeps its address and its data: only the plan changes.
From Free to a paid plan the service moves to another node and gets a new address. Create the paid service from the console. In its Settings, under Bring data into this service, click Contact support: we copy the data, the configuration and, if you want, the users.
After a move to Enterprise, update any script that uses the paths above.