Aiolum Browse stories
All stories
Graph database on object storage for AI agent memory and knowledge graphs · United States

HydraDB: Product, team and how it was built

Small teamFundedB2BDeveloper tools

HydraDB (Graph database on object storage for AI agent memory and knowledge graphs, United States): 13.1K GitHub stars, November 2026. Evidence grade E: no revenue figure was checked. Team: headcount and founding team not published; no founder is named on the pages that were read; 15 accounts wrote the 82 commits of the public repository. Launched March 2026; still running.Added

Outcome
13.1K GitHub stars, November 2026
Evidence
E no revenue figure was checked
Launch
March 2026
Status
Still running
Team
headcount and founding team not published; no founder is named on the pages that were read; 15 accounts wrote the 82 commits of the public repository
Outside funding
Sky9 Capital and angel investors, as the company says; no amount found in a downloaded source
Main channel
Not stated
No revenue figure

What is not verified

No dated revenue figure was found. The company's manifesto says US$400K ARR but has no date. A payment-processor profile, a press interview or a founder post could confirm it. The company says paying customers exist and lists a price list. No independent source confirms that the named customers pay. The funding amount is not stated in any downloaded source. The start date, the founders and the team size are not published. No company register was read: one answered with a bot check and the Delaware search needs a form. The earlier name Cortex may have an earlier history that the read pages do not show. This story is grade E: the business is real and its product, price and customers are described from public pages, but no revenue figure was checked. Aiolum shows it as an idea worth studying, not as proof that it makes money.

HydraDB is a graph database for AI agents. A graph database stores things as nodes and the links between them, such as a function and the service that calls it. The company says HydraDB is built on object storage, the cheap bulk file storage of cloud providers such as S3. It says this gives up to 10-100x lower costs.

The company sells three plans: a free self-hosted version with public code, a managed cloud plan and an enterprise plan. The cloud plan has a minimum usage of US$25 a month. An archived page of 12 March 2026 on the same domain is titled "Cortex: Context & memory infrastructure for AI". No page that was read gives a founding date or a founder name; the earliest dated trace is a GitHub organisation of 17 November 2025.

No revenue figure with a date was found, so this story is grade E. The company's manifesto says it reached US$400K ARR, which is annual recurring revenue, with 2,000 developers. That page has no date, and no payment processor, journalist or filing confirms it. The headline is a status fact: the public code repository has 13.1K stars on GitHub.

HydraDB: 13.1K GitHub stars, November 2026. Graph database on object storage for AI agent memory and knowledge graphs, United States, team of 2 to 10, evidence grade E.
The story in one card. Share it with the address of this page.
01

Why did HydraDB work?

Four causes, in the order they mattered. Each one is a reusable lesson.

01

It stores graphs on object storage to lower the cost

The company says its graph lives mostly in object storage, with hot data in memory and warm data on fast disks. Its home page claims up to 10-100x lower costs. The manifesto says it is 10x cheaper than FalkorDB and Neo4j. No outside source checked this.

02

It enters through agent memory and publishes its benchmark results

The manifesto names three first uses: agent memory, company knowledge and ontologies. The company publishes benchmark pages for each, with scores such as 90.79% on LongMemEval-S. They are the company's own runs.

03

It gives the code away and charges for the managed service

The self-hosted version is free, and its code is public. The managed plans start at US$25 a month in minimum usage. The manifesto says the open-source launch was meant to let anyone check the company's efficiency claims.

How it was built

These details come from the company's repository, home page and documentation. They are grade C. [9, 1, 12]

  • The repository page says HydraDB is an object-store-native distributed graph database written in Rust.
  • The home page diagram shows writer, indexer and reader nodes, a write-ahead log and an index built with GraphBLAS, on S3-style storage.
  • The managed service has SDKs for Python and TypeScript, an MCP server and plugins for coding agents, the documentation says.
  • The documentation lists 70 connectors, such as Slack, Gmail and Notion. The pricing page says 100+ connectors.

Tools named in the sources

Each one opens its page in the Tools tab, with every story that uses it.

02

Who tried this before HydraDB, and why did they fail?

Three companies in a database of failed startups sold database infrastructure to developers. The values below are from that database, read on 12 November 2026, and are not independently verified.

Died 2009 to 2016Burned US$12.0M

RethinkDB

The promise

A database that pushes live updates to apps, so developers need no polling.

Why it died

The record says developers liked the idea but did not pay for it. It also says the database was costly to run.

Business model
Died 2013 to 2018Burned US$100.0M

Primary Data

The promise

A layer that makes enterprise data independent of where it is stored.

Why it died

The record says the product was too complex and that the market timing did not match. It says adoption needed enterprises to change how they store data.

Technical overreach
Died 2011 to 2017Burned US$7.0M

Parse

The promise

A ready-made backend for mobile apps, so a developer ships without servers.

Why it died

Facebook bought it in 2013 and shut it down in 2017, the record says. It calls the usage-based freemium costs a fatal weakness.

Unit economics

The failed startups come from our database of 1,749 dead startups, retold here in our own words. Its entries are AI-assisted summaries of public sources, so these cards carry no evidence grade.

What changed

RethinkDB, Primary Data and Parse each sold infrastructure that developers had to adopt in place of something they already used. The records name cost, complexity and adoption as the problems. HydraDB faces the same risk, and its pages state that the Postgres graph route "is a practical starting point".

HydraDB differs in what it targets. The company aims at agent memory, where a database must hold links and history, and it offers a self-hosted version. Whether customers pay enough is not shown by any source with a date.

03

Can one person copy HydraDB now?

The pricing pattern, yes. The product, no.

A small team can copy the commercial pattern: public code, a low monthly minimum for the managed version and a higher tier for dedicated infrastructure. Building a distributed graph database is hard work. The company's own claims about cost and accuracy have no outside check.

Where it is still open: Memory and context stores for one kind of agent: voice agents, coding agents or clinical assistants.

  1. 1Publish the code and a benchmark that others can run.
  2. 2Sell the managed version with a low monthly minimum.
  3. 3Add a higher tier with one database per customer.
  4. 4Keep a public blog that answers what buyers search for.
04

How much revenue does HydraDB make?

Each row shows the evidence grade and the source numbers from the list at the end of this page. The grades are explained in How Aiolum verifies.

A funded graph-database company with a price list, a public code repository and company-stated traction. No dated revenue, founder name or headcount
FactValueGradeHow we knowSources
Public code repository, November 202613.1K stars and 5.4K forksCGitHub page of hydra-db/hydradb, read 12 November 2026. The same page shows 82 commits. The organisation page shows 63 followers and no public members.[9, 10]
Paid plans, November 2026Ship from US$25 a month, Scale from US$300 a month, Enterprise on requestCPricing page, read 12 November 2026: "managed cloud $25/mo min usage" and "$300/mo min usage". The terms add that a subscription can be cancelled in the account settings.[2, 7]
Earlier name on the same domainCortex, in an archived page of 12 March 2026CThe Internet Archive copy of the home page has the title "Cortex: Context & memory infrastructure for AI" and the text "HydraDB stores context". The archived manifesto of the same day calls the company Cortex.[4, 5]
Start of the companynot stated; the earliest dated trace is 17 November 2025CNo downloaded page gives a founding or incorporation date, and no company register was read. GitHub's record of the organisation hydra-db shows that it was created on 17 November 2025. Archived copies of hydradb.com from August 2024 and January 2025 redirect to domain-sale pages. The first copy of the present site is dated 12 March 2026. A Cortex site exists, but its robots.txt disallows Claude agents, so it was not read.[13, 4]
Accounts that wrote the public code15 accounts in 82 commits, August to November 2026calcCalculated: distinct author accounts in GitHub's commit list of hydra-db/hydradb, read 12 November 2026, without the dependency bot. Five account names contain the word hydra. The list does not say who is an employee.[14]
Legal entityAGI Context, IncCThe privacy policy and the terms name AGI Context, Inc as the company behind HydraDB. The pages show a registered office in Delaware.[6, 7]
Traction the company states, undatedUS$400K ARR, 2,000 developers, more than 12,000 agents in productionDThe manifesto says: "We launched two months ago and are already at $400K ARR with 2,000 developers on the platform." The company wrote it. The page has no date. The archived manifesto of 12 March 2026 does not contain it.[3, 5]
Customers the company namessmallest.ai, clinsight.ai, calsoft.ai and ComposioCThe manifesto says it serves these companies for agent workloads. The home page logo row has the logo names clinsight, composio and smallest.ai among others.[3, 1]
Backers the company namesSky9 Capital and angel investorsCThe manifesto says: "We are backed by" a list of angels, "Sky9 Capital" and "other operators". It gives no amount and no date of a round.[3]
Benchmark results the company reports90.79% on LongMemEval-S; 82% on BEAM 1MCThe company's benchmark site lists results dated August to October 2026. They are the company's own runs, and no outside party checked them.[11]
Blog135 posts, 58 of them labelled Deep DiveCThe blog index shows the counts. The latest posts are dated 4 October to 29 October 2026 and many are titled "... Reviews in 2026" or "... Alternatives".[8]
Time from the earliest dated page of the present site to November 20268 monthscalcCalculated: 12 March 2026 to 12 November 2026.[4]

How to read this table: a grade C value is what the company says on its own pages or what a platform page shows. A grade D value is a company claim with no date or no check. A "calc" value (grade X) was computed on this page. No value comes from a payment processor, a filing or a journalist's check of documents.

HydraDB plans as shown on its pricing page, read 12 November 2026 (grade C)
PlanPer month, billed yearly (US$)Per month, billed monthly (US$)Limit
Open Source0self-hosted on your own object storage; community support
Ship (managed cloud)25 minimum usageone database, unlimited collections; 100+ app connectors; usage charges apply
Scale300 minimum usagededicated infrastructure; one database per customer; private Slack channel; response SLAs
Enterprisecustomcustomyour cloud or a dedicated cloud; 99.5% uptime SLA; HIPAA BAA; forward-deployed engineer

The page shows no yearly price, so the first price column is empty. Ship and Scale are minimum monthly usage amounts. The Ship plan adds usage charges of US$0.70 per 1 million tokens for assisted graph creation and US$0.50 per GB-month of storage. The company says the open-source version will be free forever. The Enterprise plan is priced on request.

05

When did HydraDB launch, and how did it grow?

From a GitHub organisation in November 2025 to a public repository, benchmark pages and a three-tier price list in November 2026.

  1. 17 November 2025CThe GitHub organisation hydra-db is created, as GitHub's record of the organisation shows. [13]
  2. 12 March 2026CThe earliest archived copy of the present site at hydradb.com has the title "Cortex: Context & memory infrastructure for AI" and a demo button. It names no price. [4]
  3. August to October 2026CThe company's benchmark site lists nine dated write-ups, from "Long-Term Memory for AI Agents at Million-Token Scale" in August to retrieval tests in October. [11]
  4. October 2026CThe blog index shows posts dated up to 29 October 2026, many of them comparison articles about other memory and graph products. [8]
  5. 12 November 2026CThe home page shows a free open-source plan, a managed cloud plan and a Scale plan, with the GitHub repository at 13.1K stars. [1, 2, 9]

What could go wrong for HydraDB?

The risks are the mirror image of the causes above.

What is not verified

No dated revenue figure was found. The company's manifesto says US$400K ARR but has no date. A payment-processor profile, a press interview or a founder post could confirm it. The company says paying customers exist and lists a price list. No independent source confirms that the named customers pay. The funding amount is not stated in any downloaded source. The start date, the founders and the team size are not published. No company register was read: one answered with a bot check and the Delaware search needs a form. The earlier name Cortex may have an earlier history that the read pages do not show.

Logo wall, counters and testimonials

The home page says "Trusted by teams building world-class agents" above a row of logos with no link. The logo names include Genpact, Toptal and Distyl. No logo was verified. The "Built by the community" row shows posts from X with handles, which were not checked on X. The 13.1K stars sit next to 82 commits and 63 organisation followers on GitHub. The home page and the pricing page also show badges named AICPA SOC, ISO 27001 and HIPAA. They link to the trust center, which was not read, so no certificate or audit report was seen.

Open source and its license

The pricing page says "HydraDB will be free forever" for the open-source plan. The repository states the Elastic License 2.0. That license sets limits, so it may not meet some definitions of open source. The company uses the words open source.

Comparison articles on the company blog

Many blog posts compare HydraDB with named competitors, such as Mem0, Zep and Neo4j, under titles like "Reviews in 2026". The company wrote them. They are marketing pages. The trust center link on the home page returned HTTP 403 to the download and was not read.

Sources

The grade next to each source is the best grade that the source can support. "Read in full" means that the text of the page was downloaded and the numbers were checked in it.

  1. C HydraDB home page, downloaded 12 November 2026
    Read in full. Source for the product, the logo row, the testimonials, the counters and the cost claim.
  2. C HydraDB pricing page, downloaded 12 November 2026
    Read in full. Source for the four plans and the usage charges.
  3. C HydraDB manifesto, downloaded 12 November 2026
    Read in full. Source for the traction claim, the named customers, the backers and the strategy. The page has no date.
  4. C Internet Archive copy of hydradb.com, 12 March 2026
    Read in full. Source for the earlier name Cortex in the page title and for the earliest dated trace.
  5. C Internet Archive copy of the HydraDB manifesto, 12 March 2026
    Read in full. Source for the company name Cortex and for the absence of a traction section on that date.
  6. C HydraDB privacy policy, downloaded 12 November 2026
    Read in full. Source for the legal entity AGI Context, Inc and the founders mail address. No founder is named.
  7. C HydraDB terms of service, downloaded 12 November 2026
    Read the section on fees and cancellation. Source for the legal entity and the cancellation rule.
  8. C HydraDB blog index, downloaded 12 November 2026
    Read in full. Source for the post counts, the dates and the comparison titles.
  9. C GitHub: hydra-db/hydradb, downloaded 12 November 2026
    Read the page. Source for the stars, forks, commits, license and the Rust description.
  10. C GitHub: hydra-db organisation page, downloaded 12 November 2026
    Read the page. Source for the 63 followers and for the note that the organisation has no public members.
  11. C HydraDB benchmarks site, downloaded 12 November 2026
    Read in full. Source for the dated benchmark write-ups. The runs are the company's own.
  12. C HydraDB documentation: Introduction, downloaded 12 November 2026
    Read in full. Source for the description, the connectors, the SDKs and the MCP server.
  13. C GitHub API: record of the organisation hydra-db, downloaded 12 November 2026
    Read the record. Source for the creation date of the organisation, 17 November 2025.
  14. C GitHub API: commit list of hydra-db/hydradb, downloaded 12 November 2026
    Read the list of 82 commits. Source for the count of author accounts and the commit dates.
  15. C database of failed startups, record pages of the failed startups named above, read 12 November 2026
    Record pages read on the website on the day of writing. AI-written summaries, not independently verified. Source for the failed predecessors.

Run this company? Send corrections or a verified figure to aiolum@livyden.com

Back to all stories