Skip to Navigation
NoSQL Document Database
Easy, Fast, Reliable with Multi-Document ACID Transactions
Incremental
Time Series
Concurrent Data
Subscriptions
ETL for
Elasticsearch
Power BI
Support
-
Getting Started
All you need to know about RavenDBGetting Started
All you need to know about RavenDB -
Multi-document ACID Transactions
RavenDB is fully transactionalMulti-document ACID Transactions
RavenDB is fully transactional -
Management Studio
Our GUI makes the user experience enjoyableManagement Studio
Our GUI makes the user experience enjoyable -
Powerful Querying
Full-text search out of the boxPowerful Querying
Full-text search out of the box -
RavenDB Webinars
High-level tutorials on using RavenDBRavenDB Webinars
Customer Success Story: Rakuten Kobo
High-level tutorials on using RavenDB -
Upcoming Workshops
Deep dive into practical use of document data modelingUpcoming Workshops
RavenDB Online Workshops
Deep dive into practical use of document data modeling
What they say about us
As a document database it remains true to the core principles of these type of storage mechanisms. Somehow it managed to combine the best of relational databases with that of document databases.
RavenDB is so smooth, I don’t notice it.
Considering how huge the amount of data sent back and forth in a single quote document is, the fact that RavenDB can store the entire document and continue to perform well is really impressive.
Easy implementation, nice UI, cloud options
Easy implementation even for people with little experience with NoSQL
RavenDB is a convenient, no hassle, noSql implementation that is blazing fast.
Very quick phase for get up and running in prod (setup, learning, working).
A Multi Model Database Ripe for Building Microservices.
Customer focused with very minimum response time support.
A performant data storage solution that scales as we need it
Best in class NO SQL database for embedded IOT
Install On-Premise
Database as a Service
Supported clients
- C#
- Java
- Node.js
- Python
- C++
- Go
Fully Transactional NoSQL Database
Get the benefits of NoSQL while keeping the most essential parts of a relational database.
RavenDB is perfect for OLTP tasks like processing sales, purchases and more.
Multi-Model Architecture
RavenDB supports automatic ETL (Extract, Transform and Load) processes to replicate data to SQL solutions.
As an ACID database, you can use RavenDB in conjunction with your existing SQL databases and enjoy the best of both worlds.
All-in-One Database
Our in-house storage engine is designed to serve all your needs in one place.
You have at your fingertips features you would usually have to plug in from someplace else, saving you time and money. We automate a lot of tasks to reduce your overhead so there is less need for costly support.
Easy to Use
RavenDB is easy to install, implement, and use.
There is a small ramp up to learn. Our high-quality GUI with heavy built-in monitoring and SQL-based query language makes RavenDB user friendly for developers and non-developers alike.
Scale Up Fast
Setting up a cluster is as simple as point and click in the RavenDB Management Studio.
Keep up with the ever-increasing amounts of data and web traffic effectively and efficiently by creating new database nodes within minutes.
High Availability
Real time replication between nodes keeps your database online and available across multiple points at all times.
Your cluster keeps working amidst network partition. Balance load, reduce latency, and optimize performance within multiple locations to serve your users.
Faster than ever
Manage over 1 million reads per second and 150,000 writes on simple commodity hardware.
Try our Studio
FREE with every license
Stunning & intuitive UI
Live monitoring
Effortless configuration
Comprehensive performance statistics
Deep insight into database internal
Extensive logging & incident reporting
Download with Free License
See also
Customer Success Story | RavenDB with Rakuten Kobo on May 11
You can register for the webinar here.
Production postmortem: Deduplicating replication speed
A customer called us with an interesting issue. They have a decently large database (around 750GB or so) that they want to replicate to another node. They did all the usual things that you need to do and the process started running as expected. However… that wouldn’t make for an interesting postmortem post if everything […]
