LioranDB V2 is currently in pre-alpha, and we're now opening managed LioranDB deployments for selected early-stage startups and developers.
Until now, the focus has primarily been on building and testing the database itself: the Rust storage engine, B+Tree primary storage, MVCC, WAL and crash recovery, secondary indexes, full-text search, and the developer APIs around them.
Now I want to start working directly with real applications.
So instead of simply giving developers a Docker image and saying good luck, we're introducing a small managed offering with direct founder support.
Two Pricing Options
1. Fixed Plan: ₹5,000/month
This is designed primarily for early-stage products that don't need huge infrastructure yet.
The plan includes:
- Up to 1 million documents
- Daily database backups
- Managed LioranDB deployment
- Infrastructure monitoring and maintenance
- Direct founder support
- Basic feature requests based on your application's requirements
- Help with database integration and deployment
LioranDB's current development testing has demonstrated workloads around 10K writes/sec + 35K reads/sec, or roughly 45K operations/sec under tested configurations.
These numbers should be treated as development benchmark figures, not guaranteed production throughput or an SLA. Actual performance depends heavily on hardware, indexes, query patterns, document sizes, concurrency, and workload.
LioranDB V2 itself is also currently pre-alpha, so this offering is aimed at teams comfortable adopting early infrastructure and working directly with its developer.
2. Custom Plan
Need more than 1 million documents?
Need different CPU, memory, storage, backup policies, or workload requirements?
That's where the custom plan comes in.
Instead of forcing every application into the same infrastructure configuration, we'll review your application's expected workload and determine an appropriate deployment and monthly price.
This is particularly useful for SaaS platforms, CRM systems, backend services, AI applications, and other products with unusual or rapidly growing database workloads.
How Do You Get a Managed LioranDB Database?
We're not making managed deployments instantly purchasable yet.
There is an application process.
Visit:
app.liorandb.com
Create an account and submit an application describing your product, expected workload, and database requirements.
We'll review the application.
If it's approved, we'll provision your LioranDB database and provide the information you need to connect your application.
Billing is monthly.
The process looks roughly like this:
Create Account
↓
Submit Application
↓
Application Review
↓
Approved
↓
Database Provisioned
↓
Connect Your Application
↓
Monthly Billing
Why an Application Process?
Because LioranDB V2 is still pre-alpha.
I'd rather onboard a smaller number of applications and understand exactly how they're using the database than throw open a giant "Buy Now" button and pretend the product has already reached cloud-database maturity.
Working with early users also gives us something benchmarks can't provide: real workloads.
Different applications create very different database pressure.
A CRM might perform huge numbers of indexed lookups.
A SaaS product might have strongly tenant-oriented access patterns.
An API might perform thousands of tiny reads.
Another application might continuously ingest data.
Those workloads expose problems synthetic benchmarks simply won't.
And because managed customers have direct founder support, if something strange happens, you're talking directly to the person building the database rather than bouncing through three support tiers.
What Is LioranDB?
LioranDB V2 is a document database developed in Rust with a MongoDB-style developer experience.
Its current architecture includes:
Application
↓
LioranDB Query Layer
↓
Transactions + MVCC
↓
B+Tree Primary Storage
↓
WAL + Checkpoints
↓
Page Cache
↓
Persistent Storage
+ Secondary LSM Indexes
+ Inverted Text Index
V2 pre-alpha launched on August 16, 2026, and development is currently moving toward the Alpha release planned for October 23, 2026.
The database is still under active development and is not currently presented as production-ready.
That's also why I'm particularly interested in working with developers who are willing to test it, push it, report weird behavior, and tell me where the developer experience sucks.
Interested?
You can learn about LioranDB on liorandb.com, or apply for a managed deployment through app.liorandb.com.
If you're building an early-stage SaaS, CRM, API, internal tool, or another backend-heavy product and want to experiment with LioranDB, I'd particularly like to hear about your workload.
And yes, trying to break the database is still encouraged.
