We are finishing up a big performance cycle, and hopefully we will have a new stable next week with all of those goodies for you.
If all goes well, this will be the last (or one before last) stable release in the current version of RavenDB.
As you probably know, we have been thinking about our licensing strategy, and I thought that I'll share with you some of our early thoughts ,to get your feedback.
Probably in March or April, we want to release a new version of RavenDB. Probably called 1.2.
We are trying to run as much as possible in the open, and solicit your feedback whenever we can. Both on coding and business issues.
Your feedback is important, and I am not saying this just because it sounds good.
That said, the last time we had a pricing discussion things got somewhat ugly. I ask you all to have a polite conversation about this.
Thanks in advance, Oren.
Implications for anyone who bought a subscription: None, except that they might want to update to the new version.
Implications for people who made a one time payment:
If they bought in the last 6 months, they get 1.2 automatically. If they bought earlier than that, they need to pay an upgrade fee (249$) per instance.
There are some cases where people expected to be able to get the new versions indefinately. If you are one of those, and you bought a one time payment more than
six months ago, contact us, we will make an arrangement that will make both of us happy.
Along with the new version, we intend to change our pricing structure. This has several reasons behind that. If you remember the pricing discussion in May 2010, one
of the repeated issues that was brought up was that RavenDB is a NoSQL database, and as such its pricing needs to be match the scaling needs.
Another issue, from our side, is that introducing a new product is always a touch period of time, especially one that require the level of trust expected from a database.
The pricing reflected both those issues.
Now, with over a year and a half in production using multiple customers, we have much better data both about common usage patterns and about RavenDB itself. The level of
trust expected from a database is much higher than when we introduced RavenDB and I can tell you that so far, no one is running a 25 nodes cluster of RavenDB (maybe I
shouldn't have worked so hard on perf, people would need more servers :-) ).
All of this leads me to the following changes:
we are going to introduce RavenDB Standard, RavenDB Enterprise and RavenDB Scaleout.
RavenDB Standard is the RavenDB that you all know and (hoepfully) love. However, it also would be limited in the following ways:
Max of 12 GB RAM
Max of 6 Cores
Max of 25 databases
Note: If you are have an existing license, either subscription or one time payment that got grandfathered in, you don't have to worry about those limitations.
Pricing would still be based on per instance model, which is effectively per server.
Cost per instance would be: 999$ - which include 18 months of support (4 incidents) and auto upgrades.
After the time is up, you _can continue to use your RavenDB instance with no issues_.
But, you won't be eligible for any additional updates or support.
Exception for that is security / critical bugs that would still get fixed in a period of 36 months from the date you purchase the software.
Subscriptions would be:
399$ per year
39$ per month
In either case, you get 2 support incidents per year. And auto upgrades for as long as you have a current subscription.
If the subscription lapses, you can continue to use RavenDB, but you are not eligible for support or updates.
We will still offer the OEM model for embedded instances, which would be 1,599$ per developer per year.
Now we get to the RavenDB Enterprise. First, let us talk about the goodies.
* No limits on RAM / cores / databases
* Indexing scheduler
** Index priorities
** Offline index builds (new index won't stop existing indexes updates)
* Windows Clustering support
* Builtin compression
* Builtin encryption
* Management interface for the server (not just on a single database)
* Integration for managing all of the builtin bundle
* Replication monitoring
* HTTP Support when running in service mode
* S3 backup support
And probably a bunch of other stuff as well, but we want to have a _few_ surprises.
RavenDB Enterprise will be licensed per core. Number of cores is defined as whatever Environment.ProcessCount returns, for simplicity sake.
I don't have final pricing for that yet, so I would like to get your opinions on the matter.
I am looking at having a similar range betwen RavenDB Enterprise and SQL Enterprise as between RavenDB Standard and SQL Standard, but I haven't made up my mind.
Finaly, we have RavneDB Scaleout.
This is meant to answer the need of people who need large number of RavenDB servers (the 20 nodes RavenDB cluster).
Pricing for that is based on a 25 instances bundle, at a cost of 750$ per instance. So a 25 bundle would cost 18,500$.
If you need more than 25 - 50 nodes, you probably need to call us and we can talk about prices anyway.