dexie
Dexie Cloud Pricing Production (SaaS)
Hi, have a view question about the pricing and the Storage management.
In the pricelist for Production (Saas) i see Production users: USD $3/mo per 25 seats. and then Storage: 100 GB / 100 users
Does that mean 25Gb per 25 seats for $3/mo or in other words 1Gb per 1 seat for $0.12/mo ??
Then we have Storage: Extendable for $0.05 / GB I assume that's $0.05/ per Month. Is that right? How does the billing for that extendable storage work ? Does id add automatically to my for example 25seats subscription if a user is exceeding his 1GB?
Do i get informed when that's happening?
I cant find any detailed information in the Dexie Cloud Manager.
Is there a way to see each users current storage? Can i limit the users storage? And is there a way the user can see how much storage he is using at the moment?
So if i want to give a user, let's say 20Gb of storage it would cost me maximum: 0.12 + 19 * 0.05
$1.07 / mo
Thanks for your Answers.
Hi, and thanks for your great questions!
We've recently reviewed our storage model and updated the pricing page to provide more details. Specifically, we've now separated object storage from blob storage:
- Object storage (for strings, objects, arrays, dates, etc.) is stored in a PostgreSQL database.
- Blob storage (for larger binary data) is stored separately, offering more space per user at a lower cost.
You can find the updated details here: Dexie Cloud Pricing – Storage Limits.
Storage Allocation & Pricing Updates
The included storage for 25 users is now 21 GB in total:
- 1 GB of object storage
- 20 GB of blob storage
Most applications use less than 5 MB per user, and so far, no customers have come close to the included storage limits—especially for blob storage. This means most customers won’t need to purchase additional storage beyond what's included in their subscription.
Extra Storage & Billing
Dexie Cloud follows a predictable pricing model, so no extra costs will be applied automatically unless explicitly enabled in the Dexie Cloud Manager. Currently, auto-scaling for seats and storage is not available, but we plan to introduce it soon, along with:
- The ability to set upper limits and notifications for automatic expansions.
- Warnings when approaching storage limits.
For now, if you exceed the included storage, we’ll reach out directly. In the future, we’ll automate notifications via email so you can take action as needed.
Monitoring & Managing Storage
Currently, Dexie Cloud Manager does not yet display detailed storage usage, but this feature will be available soon. In the meantime, you can estimate your usage by exporting your database:
npx dexie-cloud export
The size of the exported file can give you a rough idea, though it may not be an exact reflection of your actual storage usage. Once storage tracking is available in Dexie Cloud Manager, you’ll be able to see:
- How much storage is being used.
- What percentage of your included storage is consumed.
- Options to purchase more storage if needed.
I hope this answers your questions! Let me know if you need further clarification.
Best regards,
David
Thanks that sound great.
If i understand well, dexie cloud is now recognizing blob's and automatically adding them to the blob storage.
Where are you publishing updates and new features you are planning to introduce soon ?
No, we're still storing Blobs in base64 fields in postgres tables, but a bug was solved recently regarding syncing blobs. So now it's possible to use blobs but large blobs are not supported until we implement Optimized Blob storage
The ongoing project can be followed on https://github.com/orgs/dexie/projects/6
Hy. Just wondering, what to do, when a user cancels his subscription in my app and the subscription expires, so that his production seat is not any longer occupied and charched by dexieCloud.
Do i have to set deactivated to true? Do i have to set type to eval? Do i have to delete the user?
Thanks for your answer.
Do i have to set deactivated to true? Do i have to set type to eval? Do i have to delete the user?
You can set deactivated to true or type to eval and it will not occupy any seat. You can optionally delete the user. Unlike deactivation and setting to eval, deleting a user will delete data that the user has stored privately. It will also remove the user's access to common realms (remove member objects for the user).
A deactivated user can be reactivated later Likewise, an eval user can be set to prod at any time later.