Software · subscription
CoreModels
The platform that holds the mappings and governed meaning between your schemas — data and content platforms, warehouse, APIs, ontologies and the public standards they connect to — so pipelines, integrations, agents and apps all read from one Core Model.
Published Revised
Licensed on coremodels.io Included in Implementation and Managed Operations engagements
- Developed by
- ARAMAI
- What it holds
- The mappings and governed meaning between your data and content platforms, warehouse, API and ontology schemas
- How schemas get in
- Bring the file your tools already produce — no passwords, no warehouse credentials
- Connectors
- 26 listed on coremodels.io: 10 formats, 16 platforms, each labelled for what you can do today
- Generally available today
- JSON Schema, JSON-LD and ShEx import; export to the same three
- Agent access
- MCP endpoint on every plan; read and write under the caller's permissions, every write versioned
- Access control
- Builder and view-only seats on every plan; RBAC, SSO/SAML, IP allowlisting and audit logs on Enterprise
- Supply chain fit
- Core to Structure and Semantics; authors the Validation contract
Deliverables
- A modeling workspace of projects — each one governed model and everything in it: types, elements, taxonomies, mappings, versions, and the connectors that feed it
- Import from the artifacts your tools already produce — a dbt manifest, a registry dump, a warehouse extract, a schema file — with no credentials
- Export to JSON Schema, JSON-LD and ShEx
- A schema validation suite and transformation profiles on every plan
- Schema versioning with branching, a changelog and version history on Team and Enterprise
- Unlimited view-only collaborators on every plan; agents are not seats
- The MCP agent endpoint on every plan — agents read and write under the permissions of the account they run under, and every write is versioned
- API access on every plan; Git integration with CI/CD triggers, schema lineage and cross-system mapping on Enterprise
What it is
Where your structure and meaning get written down
What it is
CoreModels holds the mappings and governed meaning between your data and content platforms, warehouse, API and ontology schemas, and the public standards they connect to. Whatever you build or transform with AI works from the connected picture: no manual stitching, no guessed structure, no hallucinated mappings. Pipelines, integrations, agents and apps all read from one Core Model.
It is not a database, not a search engine, not an API platform, and not a data pipeline. It sits alongside those and gives them something to agree with. Most estates already hold this knowledge; it is just spread across three schemas, a wiki page, and one senior engineer's memory. CoreModels gives it one home, with a shape, a history, and an export button.
CoreModels is developed by ARAMAI. Ariesnet configures, deploys and operates it as the authoring layer of the Context Supply Chain — the same product our Implementation and Managed Operations engagements install and run.
How schemas get in
Bring the file your tools already produce — a dbt manifest, a registry dump, a warehouse extract, a schema file. No passwords: CoreModels does not need your warehouse, database or API credentials to build a model. It imports the artifacts your tools already produce; it does not crawl your estate.
The connector catalogue on coremodels.io lists 26 connectors — 10 formats and 16 platforms — and every card is labelled for what you can do today. Generally available now: JSON Schema, JSON-LD and ShEx import. The platform connectors (dbt, Snowflake, Databricks, BigQuery, Salesforce, Confluent and the rest) are early access, and dbt is early access run with you. The catalogue is the source of truth: if it and this page ever disagree, the catalogue wins.
| Format | Import |
|---|---|
| JSON Schema | Generally available |
| JSON-LD | Generally available |
| ShEx | Generally available |
| ODCS | Early access |
| Apache Avro | Listed; no status badge published |
| LinkML | Listed; no status badge published |
| MACH ODM | Listed; no status badge published |
| OWL | Listed; no status badge published |
| Protocol Buffers | Listed; no status badge published |
| SQL | Listed; no status badge published |
Export is to JSON Schema, JSON-LD and ShEx. Nothing else is claimed here that the catalogue does not claim.
The full connector catalogue
Every connector coremodels.io lists, row by row. The catalogue is the source of truth; this table is a mirror of it, not a superset.
| System or platform | Artifact / format | Direction | Status | Auth | Who remediates disconnects |
|---|---|---|---|---|---|
| Airbyte | Catalog sync | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Apache Airflow | Scheduler metadata | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Confluent | Kafka Schema Registry | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Databricks | Unity Catalog | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| dbt | dbt manifest | Import | Early access (guided) | File in, no credentials | Ariesnet, in the engagement |
| Google BigQuery | INFORMATION_SCHEMA | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| JSON Schema | JSON Schema file | Both | Generally available | File in, no credentials | Ariesnet, in the engagement |
| Salesforce | Org schema | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Snowflake | Snowflake schema | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Apache Avro | Avro schema file | Import | Listed; no status badge published | File in, no credentials | Ariesnet, in the engagement |
| AWS Glue | Crawler snapshot | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Azure Synapse | Registered schema | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| cBioPortal | Study schema (codebook) | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| JSON-LD | JSON-LD file | Both | Generally available | File in, no credentials | Ariesnet, in the engagement |
| LinkML | LinkML file | Import | Listed; no status badge published | File in, no credentials | Ariesnet, in the engagement |
| MACH ODM | MACH ODM file | Import | Listed; no status badge published | File in, no credentials | Ariesnet, in the engagement |
| Microsoft Fabric | Warehouse schema | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Neo4j | Graph schema | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| ODCS | ODCS file (data contract) | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Open Semantic Interchange | Semantic definitions | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| OWL | OWL file (ontology) | Import | Listed; no status badge published | File in, no credentials | Ariesnet, in the engagement |
| Protocol Buffers | .proto file | Import | Listed; no status badge published | File in, no credentials | Ariesnet, in the engagement |
| REDCap | Codebook | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| Schema Converter | Multiple schema formats | Import | Early access | File in, no credentials | Ariesnet, in the engagement |
| ShEx | ShEx file (shape) | Both | Generally available | File in, no credentials | Ariesnet, in the engagement |
| SQL | SQL DDL / schema | Import | Listed; no status badge published | File in, no credentials | Ariesnet, in the engagement |
Disconnects fail closed at the boundary. When two feeding systems disagree on a definition the conformance contract decides whether the agent refuses or warns; every refusal is logged and attributed in Managed Operations. Ariesnet remediates the connector; the model does not drift silently.
The conformance contract has a home: it is the model's ShEx export, versioned in your repository beside the JSON Schema render. Your CI reads it, the boundary check in front of your agents reads it, and every refuse or warn decision cites the shape and the mapping it failed. That is how Ariesnet runs the boundary in an engagement; the export itself is CoreModels'.
What you get
A project is one governed model and everything in it: types, elements, taxonomies, mappings, versions, and the connectors that feed it. Most teams run one project per domain or per source system. Any type, element, taxonomy term or value in a model is a node.
Meaning is edited in a grid — definitions, owners, permitted values, and the columns agents get wrong — rather than in a YAML file, so the person who knows what a column means can fix it without opening a pull request.
Schema versioning with branching, a changelog and version history on Team and Enterprise; a schema validation suite and transformation profiles on every plan; unlimited view-only collaborators on every plan, and agents are not seats.
Agents and the MCP endpoint
Agents read the governed model through the MCP endpoint on every plan, using the same permissions as the person whose credentials they run under. They can write as well as read, within those permissions, and every write is versioned, so an agent's changes are reviewable and reversible like anyone else's. Each agent gets up to 15 concurrent in-flight requests; Enterprise sets throughput in contract.
Access control
Builder and view-only seats on every plan. Enterprise adds role-based access control, SSO/SAML, IP allowlisting and audit logs, with dedicated infrastructure, private-cloud or on-premise deployment, and an SLA in contract.
Where it sits in the context supply chain
CoreModels is core to Stage 2, Structure, and Stage 3, Semantics, and it is strong at Stage 4, Validation, because it authors and exports the conformance contract that other stages enforce. It is not the retrieval engine and it is not the agent runtime — Stages 5, 6 and 7 are served by other things.
We would rather you knew that on day one than discovered it in month three. If your problem is that retrieval keeps returning plausible but wrong material, or that your agents have nowhere governed to write back what they learn, CoreModels is a good part of that answer and not the whole of it. Ask us and we will tell you which part is missing.
What it does not do
- It is not the runtime gateway. It authors and exports the conformance contract; enforcing that contract at every boundary is a separate job.
- Governed write-back into your own systems of record, and the telemetry of your agents in production, are Stages 6 and 7 of the chain and live elsewhere. Writes into the model itself are supported: versioned, and governed by the caller's permissions.
- It does not crawl your estate and it does not hold your credentials. Schemas arrive as the files your tools already produce.
How it is licensed
CoreModels is licensed on coremodels.io — per builder, per team, or for the whole enterprise — and the contracting entity is Ariesnet, Inc. Ariesnet's Implementation and Managed Operations engagements include the licence for the engagement term: licensed to your team and readable by your MCP tools on your own agent API key; Managed Operations keeps it current.
You own your models and can export everything at any time. If billing pauses, projects remain in read-only mode and nothing is deleted; a downgrade past a plan's limits makes the extra items read-only rather than deleted.
Licensing
Priced on coremodels.io, not here
One price list per thing: engagements are priced on this site, the platform is priced on its own.
The context that matters most is the structure your organization already authored: its schemas, data models and canonical definitions. CoreModels holds the mappings and governed meaning between them. Ariesnet builds and operates the supply chain around it.
You own the Core Model. Export it any time to JSON Schema, JSON-LD and ShEx, with your mappings; the change log is yours on exit.
The model is the source of truth; GitHub carries its JSON Schema render. CoreModels pushes that render to a file in your repository with a file compare and a changes grid before every push, and if someone edits the file there, the changes are listed for review and enter the model only if you choose them. When an element’s version changes, an Ariesnet engagement’s CI fails the pull request whose render is behind, and your named control owner accepts the regenerated diff — our engagement practice, not a platform setting. Renders are outputs; the model is what you own from day one.
We author a Core Model three systems at a time, validate mappings at the boundary, and you leave owning the model in open formats — SQL, Cypher and vector indexes are render targets, not the product.
See one governed definition end to end — the model entry, its change, the JSON Schema and SQL renders, and the gate that refuses a wrong grain.
CoreModels is licensed on coremodels.io — per builder, per team, or for the whole enterprise. Ariesnet’s Implementation and Managed Operations engagements include the licence for the engagement term — licensed to your team and readable by your MCP tools on your own agent API key; Managed Operations keeps it current.
Honest placement
Where it sits in the chain, and where it does not
CoreModels does the authoring work in the middle of the context supply chain. It is where structure gets typed and where meaning gets agreed across systems, and it exports the conformance contract that later stages enforce at their boundaries.
It is not the retrieval engine, and it is not the agent runtime. Getting the right context to an agent at the right moment, governing what agents write back, and closing the learning loop are handled elsewhere in the chain. We would rather you knew that now than found it out in week three.