Skip to content
rushdb
FeaturesUse casesPricingBlogDocsGitHub
Sign InStart free

Agent memory

Agents that remember, and can show where a memory came from.

Company brain & RAG

Answers that span your docs, CRM, support, billing and code, with the record behind every fact.

AI search & assistants

Search and assistants on the records your app already writes.

Analytics

Questions about your data, answered by a read-only query you can inspect.

All use cases →
rushdb

The open-source database for AI. Store any data; your agents always know what’s in it.

GitHubDiscord

Product

FeaturesQuery languagesPricing and CloudSecurity

Use cases

Agent memoryCompany brain & RAGAI search & assistantsAnalytics

Developers

DocsQuick tutorialSelf-hostingTutorialsEngine manualSDKsMCP serverAgent skills

Resources

BlogGuidesComparisonsChangelogllms.txtGitHubContact
PrivacyTermsCookies

Databases are closing up. RushDB is going the other way

MongoDB, Elastic, Redis, CockroachDB, ArangoDB: eight years of database licences moving toward closed and cloud-first. Why RushDB 3 went the other way, from ELv2 to Apache-2.0.

Author
Artemiy Vereshchinskiy
Category
Engineering
Published
Nov 19, 2026
Reading time
8 min
Contents
  1. └How the pattern usually goes
  2. └The economics are real
  3. └Why it still looks like defence to me
  4. └What closing costs the people building on top
  5. └Why RushDB went the other way
  6. └Is that naive?
  7. └Sources

Contents

  1. └How the pattern usually goes
  2. └The economics are real
  3. └Why it still looks like defence to me
  4. └What closing costs the people building on top
  5. └Why RushDB went the other way
  6. └Is that naive?
  7. └Sources
░░░░░░░░░░░░░░░░░░░░░░░░00%

8 min read

Topics

  • essay
  • rushdb
  • open-source
  • licensing

Share

  • X.com
  • LinkedIn

RushDB

Precision your agents can query.

RushDB is a self-describing, graph-native database that helps AI agents reason over data with confidence: progressively introspect what's queryable—without guesswork.

Start free →

Related reading

  1. Nov 19, 2026Single writer by design: why RushDB batches8 min
  2. Nov 11, 2026Time to move on: why RushDB took the hard path off Neo4j13 min
  3. Nov 19, 2026You probably don't need a graph database8 min

In the last eight years a long list of database companies moved away from open source. MongoDB, Elastic, Redis, CockroachDB and ArangoDB changed their licences or retired their free self-hosted editions, and some products became cloud-only. I understand every one of these decisions. From where I sit, it still looks like playing defence. With RushDB 3 we went the other way: the engine moved from Elastic License 2.0 to Apache-2.0.

Most of these companies built databases I learned on, and some of them carried RushDB for years. It's an observation from someone who builds a database too, and who had to make the same decision recently.

How the pattern usually goes

If you watch long enough, the story repeats almost step by step:

Diagram

The licence is open, the project wins developers, then a cloud provider (or a fast competitor) sells it as a service and keeps most of the money. The company answers with a licence that blocks this. The community forks the last open version. And sometimes, years later, the company adds an open-source licence back.

Here are the dated events I mean, as of November 2026:

WhenProjectWhat changed
Oct 2018MongoDBCommunity Server moved from AGPLv3 to the SSPL, written to cover offering MongoDB as a service (MongoDB)
Jan 2021Elasticsearch, KibanaApache-2.0 → dual licence, SSPL or the Elastic License, announced in January (Elastic); AWS forked the last Apache version as OpenSearch (AWS)
Mar 2024RedisBSD-3 → RSALv2 or SSPL from 7.4 (Redis); the Linux Foundation started the Valkey fork (Linux Foundation)
2024ArangoDB 3.12Source under BSL 1.1; prebuilt binaries under the ArangoDB Community License, which caps production data at 100 GiB and says "you cannot use it for any commercial purposes, only internal business purposes" (ArangoDB docs)
Aug 2024Elasticsearch, KibanaAGPL added as a third licence option (Elastic)
Aug 2024 (effective Nov 2024)CockroachDBFree Core edition retired with 24.3 (announced in August, effective in November); one Enterprise licence, free for companies under $10M annual revenue (Cockroach Labs)
May 2025Redis 8AGPLv3 added next to RSALv2 and SSPL (Redis)
Oct 2026PineconePinecone Local, the Docker emulator, reached end of life; the product is managed-only (Pinecone docs)

Graph databases have their own version of this. Memgraph, SurrealDB and ArangoDB are under the BSL, FalkorDB is SSPL, and Neo4j keeps closed-source components in a commercial Enterprise edition.

The economics are real

I want to be fair here, because the pressure behind these moves is not imaginary.

Building a database is the hard path. It takes years of engineering before anybody pays, and the people who pay are usually large companies that want support, SLAs and features for scale. Meanwhile a hyperscaler can take your open-source engine, put it behind their console and their bill, and sell it to your future customers. You did the R&D. They own the distribution. That's a real problem, and a licence that says "you can't resell this as a service" is the cheapest tool in the drawer.

So when Mongo, Elastic or Redis changed licences, I don't think it was greed. They had investors, payroll and a competitor who didn't pay for the engine. That's fair anyway.

Why it still looks like defence to me

The licence became the business moat because the business moat wasn't anywhere else. If the only thing between you and a competitor reselling your database is a legal clause, then the product on top of the engine is not doing its job. The clause holds back the competitor, but it doesn't make your own service better.

And the market answered pretty clearly. AWS forked Elasticsearch into OpenSearch. The Linux Foundation forked Redis into Valkey within weeks, with cloud vendors behind it. Then both Elastic and Redis added the AGPL back. Relicensing didn't remove the competitor. It created a second project with the competitor's money behind it.

There's another cost that doesn't show up on a revenue chart, and it's trust. Every team that lived through a licence change now reads the LICENSE file before the README. They ask what happens in three years, not what the database does today. For a database, where migrating away is the most expensive thing a team can do, credibility and trust are the product. Once you spend them, they're hard to buy back.

What closing costs the people building on top

This part I feel directly. Right now I'm running a benchmark suite that compares fifteen databases on one machine, all pinned to exact image digests, all with the same CPU and memory limits. It's still cooking; when it's done I'll publish the suite and the results, so anybody can re-run every number. Cloud-only products can't be part of that. There's no version to pin, no hardware budget to match, and a network round-trip in every query. When Pinecone retired its local emulator, the question of how to include it on equal terms literally had no answer.

Developers hit the same wall in smaller ways. You can't run the database in CI without an account. You can't read the code when a query behaves strangely. You can't keep a copy that works if the vendor changes plans. And for AI agents it gets worse, IMO. An agent that works with your data should be able to run next to it, on your machine or in your VPC, not only through somebody's API with somebody's rate limits.

More closed boxes -> more plumbing around them -> more entropy for the team that has to glue it all together.

Why RushDB went the other way

To be honest, RushDB was part of this trend for a while. The 2.x platform core and dashboard were under the Elastic License 2.0: source available, but not open source. When we rebuilt RushDB as a standalone engine in Rust, I had to decide again. RushDB 3 is Apache-2.0, the whole workspace, one binary you can run anywhere. You can read the full story of the engine in the 3.0 release notes and why we left Neo4j in time to move on.

So where is the business? In the harness, not in the licence. RushDB Cloud runs the same engine and adds what is actually hard to operate yourself: managed embeddings, natural-language search, relationship suggestions, a hosted MCP server with OAuth, and team access. If somebody wants to self-host the engine and never pay us, that's fine. If somebody wants to host it for others, they'll have to build all of that too, or compete on something else.

And there's a product reason, not just a business one. RushDB is a database for AI, and its whole idea is agnosticism: any data becomes AI-ready, whatever shape it has and wherever it comes from. A database that wants to take any data can't be picky about where it runs. A closed, cloud-only engine would contradict the pitch.

Is that naive?

Maybe it is, because a hyperscaler could package RushDB tomorrow and the licence wouldn't stop them. I've thought about it, and my answer is kinda simple: if a cloud provider decides RushDB is worth reselling, the engine has already won, and our job is to make RushDB Cloud the better place to run it. I'd rather compete on the service than on a clause.

What I don't want is to build trust for five years and then spend it in one licence change. So the plan is boring on purpose:

  • The engine stays Apache-2.0.
  • The money comes from RushDB Cloud and support, see pricing.
  • Benchmarks get published with pinned versions, the method and re-run commands for every number.

Other companies will keep making the opposite call, and they'll have good reasons. I just think the databases people trust in ten years will be the ones they could always read, run and leave.

Sources

  • MongoDB issues new Server Side Public License for MongoDB Community Server (MongoDB, Oct 2018)
  • Doubling down on open, part II (Elastic, Jan 2021)
  • Introducing OpenSearch (AWS, 2021)
  • Redis adopts dual source-available licensing (Redis, Mar 2024)
  • Linux Foundation launches open source Valkey community (Mar 2024)
  • ArangoDB 3.12 incompatible changes: licence
  • Elasticsearch is open source. Again! (Elastic, Aug 2024)
  • CockroachDB enterprise license announcement (announced Aug 2024, effective Nov 2024)
  • Redis is now available under the AGPLv3 open source license (Redis, May 2025)
  • Pinecone Local development (end of life Oct 2026)