Apple acquired Kùzu Inc., the company behind the open-source Kuzu embedded graph database, according to reports published on February 11, 2026. The deal appears to date to October 2025, but its price and Apple’s plans for the technology have not been disclosed. Apple has not announced a new database app.
What Apple acquired
The target was Kùzu Inc., a database company based in Waterloo, Ontario. Kùzu Inc. developed Kuzu, software for storing and querying connected data. Calling the acquisition a purchase of a “database app” is misleading: Kuzu was primarily database infrastructure for developers, not a new consumer product. Public reporting identifies the company as the acquisition target, but Apple has not published detailed terms identifying whether the transaction included particular assets, employees, or other components. The purchase price is undisclosed. MacRumors · 9to5Mac
When the deal happened—and how it became public
Reports published on February 11, 2026, said the acquisition had taken place around October 2025, with EU-related acquisition disclosures helping bring it to light. Kuzu’s core GitHub repository was archived on October 10, 2025, the same date listed for its final release, version 0.11.3. That is a strong public signal of when the project stopped active development, but it is not, by itself, proof of the transaction’s legal closing date. The disclosure does not establish that regulators endorsed the product or that Apple plans a consumer-facing service. MacRumors · 9to5Mac · Kuzu repository
What a graph database does
A relational database organizes information into tables, rows, and columns. When a query needs to connect records across tables, it typically uses joins. A property-graph database instead represents things as nodes and the connections between them as edges; both can carry properties. That model can make relationship-focused questions natural to express—for example, how people, accounts, transactions, and devices connect in a fraud investigation.
Recommended Free Tools
#1 Best Overall
Graph databases are often considered for recommendation systems, dependency maps, knowledge graphs, social networks, supply-chain analysis, and identity relationships. They are not automatically faster or better than relational databases: results depend on the data model, indexes, query, hardware, and implementation.
What Kuzu offered
Kuzu was an embedded property-graph database that used Cypher, a language for graph queries. “Embedded” means an application can use the database without requiring a separate database server to be installed and operated for that use case; it describes deployment, not a guarantee that data never leaves a device. Its project materials describe features including full-text search, vector search, columnar disk-based storage, multicore query parallelism, ACID transactions, an extension system, and WebAssembly support. Official Swift bindings and a browser-based exploration interface were also available. Kuzu repository · Kuzu Explorer · Kuzu Swift bindings
Rank #2
The core public repository identifies Kuzu as MIT-licensed. That describes the license stated for that project; it does not establish the terms for every related component or what Apple may do with technology it acquired.
Why Apple might want it
Kuzu’s combination of graph queries, vector search, and full-text search could be relevant to systems that need to find information by meaning while also tracking relationships between entities. That makes AI retrieval, semantic search, and knowledge-graph infrastructure plausible areas of interest. Kuzu’s embedded design could also suit local data processing or developer tools. These are technical possibilities, not disclosed Apple plans; no Apple product has been identified as using Kuzu.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #3
FileMaker and iWork are possibilities, not announcements
Apple owns Claris, which makes FileMaker, a commercial relational database and low-code application platform. Kuzu could theoretically contribute graph capabilities, search, or other technology to FileMaker. A future database-oriented iWork product is another speculation: Pages, Numbers, and Keynote do not amount to a direct Microsoft Access equivalent. Neither an iWork database app nor a FileMaker integration has been announced. AppleInsider
An acqui-hire—an acquisition driven partly by a team’s expertise—is also possible, but unconfirmed. The acquisition alone does not show whether Apple values Kuzu’s code, its people, or both.
Rank #4
What the acquisition does not tell us
Apple has not disclosed a product roadmap, a release date, a transaction price, or a named use for Kuzu. There is no evidence in the public reporting that Apple is launching a database app, adding Kuzu to iWork or FileMaker, replacing SQLite or FoundationDB, or using it for Apple Intelligence or a specific Siri feature. Until Apple makes an announcement, those claims remain speculation.
How Kuzu fits beside Apple’s other database technologies
These technologies address different data models and needs. The acquisition does not mean Apple is abandoning its existing frameworks or services.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match| Technology | What it is | How it differs from Kuzu |
|---|---|---|
| Kuzu | Embedded property-graph database using Cypher | Designed around connected entities and graph queries; its public repositories are archived. |
| FileMaker | Claris’s commercial relational database and low-code app platform | For business applications and relational workflows, not a direct graph-database equivalent. |
| FoundationDB | Distributed key-value database technology acquired by Apple in 2015 | Different architecture and role from Kuzu’s embedded property graph. |
| Core Data | Apple framework for object graph management and persistence | A developer framework, commonly used with SQLite-backed stores, rather than Kuzu’s graph database. |
| SQLite | Embedded relational database widely used in Apple-platform development | Relational rather than graph-native; SQLite is not an Apple-owned product. |
| CloudKit | Apple cloud service for app data and backend capabilities | A cloud service, not an embedded property-graph database. |
What Kuzu’s archive means for current users
The core Kuzu repository and multiple related repositories are archived and read-only. The project’s existing releases remain available, but an archived repository is not an actively maintained upstream: users should not assume Apple will provide updates, security fixes, compatibility work, or support. Kuzu’s Swift bindings and Explorer repository are archived as well. Kùzu GitHub organization · Kuzu repository
The core repository also notes changes to extension distribution: users may need preinstalled extensions or a local extension server. That can affect builds that depend on extensions, independently of whether the core database still runs.
Continuity steps for an existing deployment
- Pin the exact Kuzu version and dependency versions used by your application.
- Mirror the source, packages, documentation, and required extension artifacts so your build does not depend on their remaining available elsewhere.
- Test the pinned build on the operating systems and toolchains you actually support, including any Apple platforms in scope.
- Export representative data and preserve the queries and workloads needed to validate a replacement.
- Check whether any community fork you might adopt has active maintainers and a credible security process.
- Review license obligations for redistributed binaries and modified code; the core repository’s MIT license does not settle the terms of every related component.
Which alternatives fit which needs?
These options are not interchangeable. Choose based on whether you need relational storage, analytics, graph-native queries, business workflows, or a managed collaborative service.
| Option | Consider it when | Important difference |
|---|---|---|
| SQLite | You need portable, embedded relational storage. | It is mature and widely supported, but not graph-native. |
| DuckDB | You need embedded analytical SQL and local data analysis. | It targets analytical workloads, not property-graph data. |
| Neo4j | You need graph-native workloads with an established graph ecosystem. | Its operational and commercial model differs from a small embedded MIT-licensed project. |
| PostgreSQL | You need a general-purpose relational database and its broad extension ecosystem. | Graph modeling usually calls for a different schema or an extension. |
| FileMaker | You need Apple-adjacent low-code business apps, forms, and relational workflows. | It is not a direct replacement for an embedded graph database. |
| Cloud database services | You need hosted operations, collaboration, or managed scaling. | They introduce network dependence, recurring costs, and potential vendor lock-in. |
For an ordinary local app database, SQLite may be the closer fit; for embedded analytics, consider DuckDB; for a graph workload that needs an active commercial ecosystem, assess Neo4j. Those are starting points, not drop-in migration recommendations: test the data model, queries, performance, and operating requirements before switching.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
