If the knowledge graph under your agents runs on GraphDB, the self-hosted fallback you are counting on does not exist. The database is proprietary, the free edition has needed a vendor-issued license file since April 2025, and as of this week the vendor is majority-owned by a private equity fund with a stated plan to buy its neighbours.
Oakley Capital Fund VI announced on August 19 that it had taken a majority stake in Graphwise. Most of the coverage treated this as a routine European software buyout. One widely-read trade report described GraphDB as "an open-source graph database". It is not, it has never been, and that sentence is the reason this deal matters more than its undisclosed price.
What Oakley Actually Bought
Oakley bought the company that issues your license key, not a stake in a community project. Oakley Capital Fund VI took the majority position from a consortium led by Integral Capital Group that also included PortfoLion Capital Partners, Carpathian Partners and the EBRD. Terms were not disclosed. Graphwise itself is only two years old as a corporate entity: it was formed in 2024 by merging Ontotext, founded in Sofia in 2000, with Vienna's Semantic Web Company, founded in 2004.
The numbers Oakley published are the vendor's own: more than 200 blue-chip customers in financial services, life sciences and the public sector, and historical organic ARR growth above 30% a year. Peter Dubens, Oakley's founder and managing partner, framed the thesis in one line — "AI is changing how every organization operates which makes trusted, well-governed data more important now than ever." Graphwise president and co-founder Atanas Kiryakov, who stays in place, called Oakley a firm with "an outstanding track record of transforming founder-led software businesses into unicorns."
The product you are buying is now five branded components: GraphDB, Graph Modeling, Graph Automation, Semantic Analytics and a GraphRAG "context-aware retrieval workflow engine". Ontotext, Semantic Web Company and PoolParty — the names on the contracts most existing customers actually signed — now appear on that page only as legacy logos. Brand consolidation of that kind usually precedes packaging and pricing consolidation.
GraphDB Is Not Open Source. RDF4J Is.
The open-source component in this stack is the framework GraphDB plugs into, not GraphDB. Eclipse RDF4J is a Java framework for RDF data governed by the Eclipse Foundation, and GraphDB's own architecture documentation is explicit about the relationship: GraphDB "is packaged as a SAIL (Storage And Inference Layer) for the RDF4J framework" and "implements The Sail API interface so that it can be integrated with the rest of the RDF4J framework." The open thing is the socket. The engine that plugs into it is a commercial product — the database catalogue at CMU lists GraphDB's license as "Proprietary" and its project type as commercial.
The confusion is understandable, because Ontotext genuinely did open-source parts of the product. In September 2019 it released the Plugin API and the GraphDB Workbench alongside the MongoDB, Autocomplete, GeoSPARQL and RDFRank plugins, and the Workbench repository carries the Apache License 2.0 with the copyright held by "Sirma AI" JSC, trading as Ontotext. So the admin UI is Apache 2.0 and the query engine underneath it is not. Both statements are true, and only one of them protects you.
This is the same shape as the Anyscale deal earlier this month, where Ray is Apache-licensed and the control plane above it is not. It is worth internalising as a pattern rather than a coincidence: vendors open-source the layer that drives adoption and keep the layer that drives revenue. Do not let a repository badge stand in for a license review — the same trap ran through the Anaconda acquisition of Enkrypt AI.
Version 11.0 Took the Free License Out of the Box
The escape hatch most architects assume they have was closed sixteen months ago. GraphDB's own licensing page states it plainly: "Starting from GraphDB 11.0, GraphDB Free is no longer automatically distributed with GraphDB. If you want to use GraphDB Free, you must first request a free license from the Graphwise website and manually install it before use." The page adds a detail that matters operationally — "This also applies when upgrading between minor versions of GraphDB."
GraphDB 11.0 shipped on 8 April 2025. Its release notes confirm the built-in Free license was removed, cap Free at five repositories, and remove something an enterprise cannot work around: "LDAP, OpenID/OAuth, Kerberos, and X.509 authentication and authorization methods are no longer available in GraphDB Free." Free also carries a hard ceiling of two concurrent queries. A tier with no SSO, five repositories and two concurrent queries is a laptop demo, not a production fallback.
Getting the license is a support ticket, not a download. The setup documentation tells you to "request your copy of GraphDB Free from the download page" and says "You will receive the Free License on your email address," after which you place it as graphdb.license in GraphDB's work directory or point at it with the graphdb.license.file property. In a container that means mounting a file your vendor emailed to a named human, into every environment, on every minor upgrade. Find out today which person's inbox that file came from, and whether they still work for you.
For the Enterprise Edition the shape of the bill is the part to underline: the licensing page says EE is "offered on a per-server-CPU-core basis," each license "is applicable to an individual machine only," and "each individual core supports only a single concurrent query." Agent traffic is concurrent by nature — a retrieval step fires per tool call, not per human. Under per-core licensing, agent concurrency converts directly into purchase orders, and Graphwise publishes no price for it. That is an uncapped variable in your 2027 budget, held by an owner you did not choose. It is the same failure mode as buying agentic capacity on credits that can be repriced at close.
Read Article 3.1 Before You Call Free a Fallback
The Free edition's license agreement forbids the exact use most teams imagine for it. The GraphDB Free license text states at Article 3.1 that "Licensee shall not use Licensed Software, Web Services or Documentation for a site or service and operate the site or the service for a profit or generate revenue through direct or indirect methods." If the agent grounded on that graph sits in a product you charge for, Free is not a contingency plan. It is a compliance finding waiting to be written up.
Three more clauses in the same document deserve a read by someone in legal rather than someone in platform engineering:
- Article 4 makes the grant a one-year term that "shall automatically renew for subsequent one-year terms." It is not perpetual.
- Article 18.2 lets either party terminate without cause on two months' written notice at the end of a term. That includes the licensor.
- Article 15.3 says "The Licensee is not allowed to publish evaluation results obtained through the use of the Licensed Software without the written permission of the Licensor." Your bake-off writeup is covered by that sentence.
The paid agreement is tighter in a way that cuts against you specifically. The GraphDB end-user license agreement grants a "nonexclusive, non-transferable and nonassignable limited right and license to use" the software "for Licensee's own internal use, and in accordance with the licensed number of CPU Cores," and states that "Licensee is not allowed to assign or transfer any contractual rights or duties to third parties, including any affiliates of Licensee, unless it has obtained the prior written consent of Licensor." Read that against this week's news. You cannot move your own license to your own subsidiary without asking permission. The company that issues it changed hands without asking yours.
That asymmetry is normal in enterprise software and it is exactly why change-of-control language belongs in the master agreement rather than the license file — the Stripe acquisition of OpenRouter made the same point about data policy, and Tricentis buying Tabnine made it about roadmaps and source-code escrow.
A Roll-Up Buyer Now Holds the License Key
Oakley told you what it intends to do, and its history says it will do it at volume. The announcement says the firm will develop Graphwise's commercial capabilities, strengthen its international footprint and "pursue selective strategic acquisitions" in a fragmented market. Oakley's own milestones page records more than 250 bolt-on acquisitions across the portfolio, over €12.7 billion raised across nine funds and more than 55 businesses backed, with the 100th bolt-on completed in 2021 and Fund VI closing in 2025 at €4.5 billion. That is roughly 150 add-ons in the last five years. "Selective" is doing gentle work in that sentence.
The steel-man is real and you should hold it. The sellers were a development-finance and growth-capital consortium, not a strategic acquirer with a competing product to protect. Kiryakov remains president. A €4.5 billion fund can pay for the enterprise features — clustering, identity, connectors — that a bootstrapped Sofia database company rationed for two decades. Buy-and-build in semantic technology could genuinely produce a better-integrated stack than the one 200 customers are running today, and plenty of Oakley portfolio companies grew rather than got squeezed.
But the mechanism that funds all of that is the same mechanism that sets your renewal. A per-core license with no published rate, an annual term, a two-month termination right and a Free tier gated behind a vendor-issued file is a pricing surface with very little friction on it. Nothing about that is unusual, and nothing about it is safe to leave unexamined for another two quarters.
What in Your Stack Is Actually Portable
More of it than you fear, and the parts that are not are the parts you built yourself. The query language is a W3C standard, the integration surface is RDF4J, and Apache Jena is Apache 2.0 with a SPARQL 1.1-compliant engine and built-in OWL and RDFS reasoners. Scale is not the objection people assume either: UniProt's public SPARQL endpoint reports 232,509,129,690 triples in its 2026_02 release and runs on QLever, an Apache-licensed engine from the University of Freiburg that reached full SPARQL 1.1 compliance including Update in June 2025. If 232 billion triples run on an open engine, your ten million are not the reason you are locked in.
What does not port is the inference layer. GraphDB's reasoning uses "a notation almost identical to R-Entailment defined by H.J.T. Horst" with GraphDB-specific extensions, and custom rulesets live in .pie files with GraphDB-only features like the Cut operator and context-based statement filtering. Every .pie file your team wrote is a migration project. So are the connector configurations, the GraphRAG retrieval workflows and any query that leans on a GraphDB-specific plugin. Inventory those before you inventory anything else — that is where the switching cost actually sits.
And do not assume the neighbours are cleaner. Neo4j Community Edition is GPLv3 while Enterprise "includes additional closed-source components not available in this repository" and requires a commercial license. Dual licensing is the norm in this category, not the exception. The lesson is not "GraphDB bad, alternative good." It is that the license file is the artefact you have to read, every time, for every store — the same discipline that separates a genuine self-hosting decision from a cost fantasy.
Three Things to Do Before Your Next Renewal
This Week: Establish what you actually run. Get the edition (Free, the discontinued SE, or EE), the licensed core count, the expiry date and the name of the person who received the license file by email. If you are on Free in anything that touches a revenue-generating service, escalate that to legal on the strength of Article 3.1 alone. Then check whether your build and disaster-recovery pipelines have a copy of the license file, or whether a clean rebuild would fail on startup.
This Month: Pull your master agreement and search it for change of control, assignment, price-increase caps and renewal notice periods. If there is no cap on the per-core rate at renewal, that is the single line to negotiate — the vendor's cost to serve did not change this week, but its ownership did. In parallel, count your .pie rulesets, GraphDB-specific plugins and connector configurations, and put a rough engineering estimate against porting them to Jena or QLever. You are not migrating; you are pricing the option so the renewal conversation has a number behind it.
Before Renewal: Model agent-driven concurrency against per-core licensing. Take your projected tool-call volume, work out peak concurrent SPARQL queries, and divide by one query per core. If that number is materially above your licensed cores, you have a budget event, not a technical one — and the same discipline applies to the retrieval spend sitting next to it. Ask Graphwise, in writing, for a multi-year rate card and confirmation that the Free license terms and issuance process will not change under the new ownership. The answer, or the refusal, tells you what you need to know.
The Bottom Line
Every few years the industry rediscovers that "we can always self-host it" was an assumption nobody tested. It was true of application servers, then of Hadoop distributions, then of the control planes above open-source runtimes, and it is true now of the semantic tier that a lot of enterprises have quietly made load-bearing for agent grounding — the layer where context, not model quality, turns out to be the ceiling. GraphDB is a good database. That is not in question here. What is in question is whether the people depending on it know that its free tier is a licensed product with a one-year term, a revenue-use prohibition and a new owner who buys companies for a living.
Your fallback plan is only a plan if someone has read it. Go read the license file.
Continue Reading
- Ray Is Open Source. The Control Plane Above It Isn't.
- Anaconda Bought Your AI Red Teamer. Read the License.
- Self-Host the Vector DB for Residency. Not for the Bill.
- Stripe Bought OpenRouter. A Toggle Is Not a Contract.
- Tricentis Bought Tabnine's Context Engine, Not Your IDE
- What RAG Actually Costs: $1,308 a Month at 10M Tokens/Day
- Grab Ran Analytics Agents 5 Months. Context Was the Ceiling.
- Bending Spoons Bought Airtable. Reprice Before It Closes.