Neutral by design, not by how many we have written
The Semcore Platform binds at the data catalog layer: the place your data estate already keeps the identity of a table. Everything below that layer is reachable through it, which is why this page is a consequence of the architecture rather than a list of work.
It matters because the alternative is renting your semantics from whichever vendor holds your data. Meaning that sits above the storage layer can move; meaning that sits inside one cannot.
Built to bind to the data catalogs, warehouses and stores you already run
What that binding reaches
Grouped by where each system sits rather than by how far along it is. Nothing here carries a state, because the claim is about where the Platform binds, and that does not change as each one is written.
Data catalogs
Where a table's identity and its metadata already live. This is the layer the Platform binds at.
- Apache Polaris
- Project Nessie
- Unity Catalog
- Snowflake Open Catalog
Warehouses
Engines with a data catalog of their own, addressed through it rather than around it.
- Snowflake
- Databricks
- Google BigQuery
- Amazon Redshift
- Dremio
Object stores
Where the files actually sit, underneath whatever data catalog describes them.
- Amazon S3
- Azure Data Lake Storage
- Google Cloud Storage
Repositories
Where definitions are versioned and reviewed, the same way code is.
- Git
These names identify the systems the Platform is built to bind to. They are their owners’ trademarks, used to say what the Platform targets, and none of these companies has any affiliation with Semcore or has endorsed, sponsored or partnered with it.
An AI Readiness Review
A scoping conversation, and a look at your data estate as it stands: what your AI plans will need from it, where the gaps are, and which of them to close first. The findings are yours either way.