The protocols Eisberg commits to.
Eisberg's portability promise is structural. Every customer-facing surface either is or builds on an open standard. The list below is what we publicly commit to.
What's in this set.
Apache Iceberg
Storage format
All customer data lives in Apache Iceberg in customer-owned object storage. Any engine that supports the standard can read it — including the warehouses you might be migrating from.
MCP
Agent protocol
The Model Context Protocol is how agents talk to Eisberg. Any MCP-compatible client becomes an Eisberg user with one config block.
Open lineage events
Lineage protocol
Lineage events emitted from every layer of the platform follow open-standard event shapes — replayable, queryable, and consumable by any compatible tool.
OpenAPI
API spec
Every public API has an OpenAPI 3.1 spec. Generate clients in any language. The spec is the contract, not the docs.
OAuth 2.0 / OIDC
Auth
Standard auth flows. SCIM for user provisioning. SAML for enterprise SSO. No proprietary auth rituals.
Request access
Documentation, OpenAPI specs, MCP server reference, and the migration-from-proprietary-formats guides — shipped on request.