What Shipped in MetaKarta 12.0, and What's Still Planned?
This page is for administrators planning an upgrade and evaluators checking what MetaKarta ships today. It links the features and roadmap notes and the current patch lists for MetaKarta 12.0 and MetaKarta 11.1, for both the Meta Integration Metadata Management (MIMM) platform and the Meta Integration Model Bridge (MIMB)connectors for metadata harvesting, plus Metadata Query Language (MQL) and REST API changes. After reading it, you can tell which capabilities are generally available, which are planned, and whether your installation has the latest cumulative patch.
Note
Some of the features detailed in this document may not apply and/or be available for the particular edition/version you are using.
Get started
MetaKarta 12.0
MetaKarta 11.1
Frequently asked questions
What shipped in MetaKarta 12.0?
MetaKarta 12.0 became generally available on September 22, 2026. It shipped a redesigned interface, Ask MetaKarta for natural-language questions through your own LLM provider, and MetaKarta MCP, one server with two toolsets for AI agents: Metadata Management Tools and Semantic Hub Tools. It also shipped Context Sandbox for validating AI grounding context, and Semantic Hub, with semantic model import, modeling, native compilation, and Ontology Modeling.
What's planned for Semantic Hub after 12.0?
Planned for Semantic Hub: import and export for Apache Ossie (formerly OSI) and Microsoft DAX, and import and export for third-party semantic modeling tools. These are roadmap items and aren't available in 12.0. [NEEDS ANSWER: confirmed delivery timing for these items; the live 12.0 notes say Spring 27 (03/15/2027) and the vault says Q4 2026.]
Which 12.0 features are in each edition?
Semantic Hub, Ontology Modeling, and Context Sandbox ship in MetaKarta only. Ask MetaKarta, the redesigned interface, and MetaKarta MCP's Metadata Management Tools ship in MetaKarta and in OEM partner products. [NEEDS ANSWER: whether MetaKarta MCP's Semantic Hub Tools ship to OEM partners.] Each release page repeats that some features may not apply to your edition or version.
How do cumulative patches work?
Every patch is cumulative: each one is a fully integrated build that includes every earlier fix. MIMB patches come out weekly and platform (MIMM) patches monthly.
A patch applies within a version, such as 11.1, and doesn't cover Apache Tomcat or PostgreSQL updates. Some fixes in the patch lists note that they need the full installer.
See the Support page's patch policy and the 12.0 current patches.
How do I upgrade to MetaKarta 12.0?
Use the full upgrade procedure, since patches only update an installation within its current version. Back up the installation and database, clean up old model versions, test your model imports, and follow the Deployment Guide's step-by-step upgrade. Check the 12.0 notes for version-specific issues first.
Where are the MIMB bridge release notes?
MIMB keeps its own release notes, with a features and roadmap page and a current patches list for 12.0 and 11.1, plus notes for earlier versions back to 9.0.1. Check them when a harvest behaves differently after a patch, since newer bridges can extract more metadata and report more warnings.
See MIMB Release Changes.
Where are the MQL and REST API release notes?
Both keep release change pages, currently covering MIMM 11.1 and 11.0. One change that affects existing scripts: the REST API authentication header was renamed from api_key to api-key in 11.1.0.
Related documentation
Return to the MetaKarta documentation home. For the full upgrade procedure, see the Deployment Guide; for bridge coverage and limits, see the MIMB bridge documentation.