What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Apple appears to have acquired Canadian graph-database startup Kuzu in October 2025 for an undisclosed amount. The transaction became public on February 11, 2026, after Apple-focused publications identified it in European Union Digital Markets Act (DMA) acquisition disclosures. Apple has not announced a product using Kuzu, and the available evidence does not establish whether the deal covered the whole company, selected assets, employees, or a combination.
What the reported acquisition establishes
The MacObserver reported that an EU disclosure identified Apple’s acquisition of Kuzu, while MacRumors described the deal as completed in October 2025. Neither report gives a purchase price. The public accounts call it an acquisition of Kuzu, but they do not provide enough detail to classify it confidently as a conventional corporate takeover, an asset purchase, an acqui-hire, or a transaction combining company ownership with employee hiring.
The exact day sometimes appears as October 10 in published lists of Apple’s 2025 transactions. The broader reporting supports October 2025; the specific day should therefore be treated as reported rather than independently confirmed.
A qualification matters here: the European Commission’s acquisitions page, as currently retrieved, does not display a Kuzu entry and can return “No acquisitions.” The acquisition is supported by multiple secondary reports and by Kuzu’s repository being archived around the same time, but the historical, non-confidential Commission notice is not presently available through that live page.
Recommended Free Tools
#1 Best Overall
Why an EU disclosure revealed the deal months later
The disclosure route is the DMA’s concentration-notification system. Under Article 14, designated gatekeepers must inform the European Commission about qualifying mergers, acquisitions, or other concentrations involving companies that provide core platform services, other digital services, or services enabling data collection. The Commission publishes non-confidential summaries on a rolling basis, generally no earlier than four months after receiving a notification.
That process explains how a transaction reported as completed in 2025 could surface publicly on February 11, 2026. It does not mean every Apple acquisition must appear in the database, nor does the existence of a notice establish a particular valuation threshold.
Other 2025 transactions reported alongside Kuzu
MacObserver’s account transcribed the following transactions from the same disclosure context. The list should not be read as proof that every item was a full-company acquisition; EU notices can concern assets, employees, or other structures.
Rank #2
| Reported date | Company or technology | Reported focus |
|---|---|---|
| January 3 | Pointable | Enterprise natural-language retrieval |
| January 24 | TrueMeeting | Digital-avatar technology |
| January 24 | WhyLabs | Machine-learning monitoring |
| February 11 | Pixelmator | Image-editing software |
| May 28 | IC Mask Design | Analog-chip layout |
| August 19 | Styra | Cloud-native authorization software |
| October 10 | Kuzu | Embedded graph-database technology |
What Kuzu actually built
Kuzu was not a hosted database service that customers operated as a cloud cluster. Its project described an embedded, serverless property-graph database: an engine integrated into an application or process rather than run as a separately managed database server. The upstream project was released under the MIT license.
- Graph model: entities are represented as nodes and their connections as edges.
- Cypher: a graph query language for expressing relationship traversals.
- Search: full-text search and vector indexes.
- Storage and execution: columnar disk-based storage, vectorized and factorized query processing, and multi-core parallelism.
- Transactions: serializable ACID transactions.
- Deployment: WebAssembly bindings that could support browser-based execution.
A relational database generally stores records in tables and joins them when a query runs. A graph database makes relationships a first-class part of the data model, which can simplify traversals such as “find all dependencies two or three links away” or “identify entities connected through several relationship types.” That can help with recommendation systems, dependency analysis, fraud investigation, and knowledge graphs. It does not make graph databases universally faster: results depend on data shape, indexes, query patterns, storage design, and workload size.
Why Kuzu could interest Apple
The most credible strategic interpretation is that Apple acquired technology and/or people useful for local, relationship-aware data processing. That is an inference, not an announced roadmap.
Rank #3
On-device and in-process execution
An embedded engine can run inside an application without a separate database service. For software that must work offline, minimize operational overhead, or keep data on a device, that architecture is materially different from a cloud-only graph platform.
Private relationship modeling
A local graph could model connections among contacts, calendars, files, apps, media, locations, or communications while keeping those relationships on the device. Kuzu’s embedded design is compatible with that kind of privacy-sensitive processing, although there is no evidence Apple is using it for any particular data set.
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 →AI retrieval beyond vectors
Vector search finds semantically similar material; graph edges preserve explicit relationships and provenance. Combining the two can help an AI system retrieve information that is both similar and connected. The possibility is relevant to Apple’s broader AI work, but no source confirms Kuzu in Apple Intelligence, Siri, or any other named product.
Rank #4
Internal infrastructure or developer tooling
Apple could use graph capabilities internally or expose selected functionality through future developer frameworks. Kuzu’s acquisition does not, by itself, imply a standalone Apple database product.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What happened to the public Kuzu project
The upstream GitHub repository was archived on October 10, 2025 and is read-only. It lists version 0.11.3 as the latest release. The project’s documentation says existing releases remain usable, while also noting changes around extension distribution: the official extension server was no longer provided, so users were directed to bundled extensions or to host an extension server themselves. Version 0.11.3 included commonly used extensions such as algo, fts, json, and vector.
MacRumors and MacObserver also reported that Kuzu’s website was taken down and that its public presence changed after the transaction. Repository archival is strong evidence that upstream public development stopped or changed direction on that date. It is not proof that the code is unusable, that all future development ended, or that Apple has assumed public maintenance.
Practical implications for existing users
- Existing applications can continue using released code under the MIT license.
- No future official release, security fix, compiler update, or operating-system compatibility update is established.
- Extension availability and self-hosting requirements deserve review before new deployments.
- Teams should preserve source, build instructions, dependency pins, and test coverage rather than assume an archived project will receive support.
- Whether Apple will publish changes, offer migration guidance, or retain the technology privately is unknown.
How Kuzu differs from Apple’s existing database products
Apple owns FileMaker through Claris. FileMaker is a user-facing relational and workgroup database product; Kuzu was an embedded analytical graph engine. They address different technical problems and should not be treated as interchangeable products.
The acquisition therefore does not imply that Apple is preparing a new database application for iWork or replacing FileMaker. MacObserver raised those product possibilities while noting that Apple has not explained Kuzu’s intended use. Internal infrastructure, developer tools, or future data features are equally plausible interpretations, and none has been announced.
What remains unknown
- The purchase price.
- Whether Apple acquired Kùzu Inc., selected assets, employees, intellectual property, or some combination.
- Whether Kuzu engineers joined Apple.
- Which Apple organization, if any, received the technology.
- Whether Kuzu-derived code is already present in an Apple framework.
- Whether Apple will keep the project open source, commercialize it, or discontinue public development.
The timing is notable: the reported October 2025 completion and October 10 repository archive are close together. That correlation is circumstantial, not proof of the transaction’s structure or of why the repository was archived.
Bottom line
Apple’s purchase of Kuzu is credible based on secondary reporting tied to DMA disclosures and the project’s contemporaneous archival. What Apple acquired and what it plans to do with the technology remain undisclosed. The confirmed technical story is an embedded, open-source graph engine with Cypher, vector and full-text search, parallel execution, transactions, and WebAssembly support—not the launch of an Apple graph-database product or evidence of a specific new Siri or Apple Intelligence architecture.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsQuick 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.
