SynOI

SynOI vs Natoma · MCP gateway, but for everyone

MCP is the open piece. The gateway around it doesn't have to belong to your data warehouse.

Natoma is a managed Model-Context-Protocol gateway with enterprise IAM bolted on. It is a real product with real customers, and Snowflake announced intent to acquire it on 2026-05-28. That is good news for Snowflake-standardised shops. It is a structural problem for every multi-cloud, non-Snowflake, regulated, or sovereignty-sensitive enterprise. SynOI is the open, multi-vendor, cross-cloud, self-hostable alternative, with signed receipts, a public verifier, and a memory layer Natoma does not have. The comparison below is factual. Where Natoma wins today, we say so.

The short version

If your stack is already Snowflake-standardised and you only need a managed MCP gateway with enterprise IAM: Natoma (now Snowflake) is a coherent choice.

If you run multi-cloud, must self-host, must publish independently verifiable audit, or need governance for actions that go beyond MCP tool calls: SynOI is the design that matches.

Axis-by-axis

No marketing adjectives. Facts cited to public sources.

Axis
SynOI
Natoma (Snowflake)
Category
Open agentic control plane: gateway + receipts + memory + identity + supply chain
Managed MCP gateway + enterprise IAM bolted on
Ownership
Independent Delaware C-corp (SynOI Inc., Jan 2026). Bootstrapped. The protocol stays open regardless of who funds us.
Acquisition announced 2026-05-28: becoming part of Snowflake. Roadmap and pricing now subject to a data-cloud vendor.
Cloud strategy
Cross-cloud and self-hostable. AWS, GCP, Azure, on-prem, air-gapped. Not bundled with a data warehouse.
Natoma is becoming a Snowflake feature. Multi-cloud and non-Snowflake shops inherit a Snowflake dependency.
Vendor lock-in
Open spec (SRAID-Core, GAP, OID Resolver). CC0. Any compliant library verifies offline. Move gateways without re-issuing identities.
Managed product; built on MCP (open) but the gateway is closed and now a Snowflake asset.
Audit trail
Hybrid-signed (Ed25519 + ML-DSA-65) Decision Receipts. Independently verifiable offline. Publicly anchorable to OpenTimestamps / sigstore Rekor.
Audit logs to SIEM. Verifier surface = the Natoma (Snowflake) product. No offline verifier.
Verifier surface
Public, no-auth verifier at verify.synoi.systems. An external auditor verifies a receipt without an account.
Verification is a feature of the product. No public verifier surface.
LLM provider strategy
BYO keys. Any LLM. Provider key forwarded once, never persisted.
Model-agnostic via MCP. Comparable.
Identity model
Operator-portable Persona signed by the operator. Identity travels across every AI surface and every gateway.
Standard enterprise IAM (OAuth 2.1, SSO, SAML, SCIM). Identity belongs to the IdP, not to the operator.
Self-hosting
Yes: Gateway, Edge, SynBox all self-deployable. DEP1 (cloud), DEP2 (your VPC), DEP3 (tenant-encrypted).
Managed cloud is the product. Self-host is limited to running MCP servers, not the gateway itself.
On-prem / air-gapped
Yes (Edge + SynBox). Designed for air-gap with offline-verifiable receipts.
Not in scope for the managed product.
HITL surface
Multi-surface: desktop overlay, Slack, SMS, mobile, email magic-link. Per-tenant policy picks the combo.
Identity-aware ABAC and role profiles; HITL is not a primary feature in their messaging.
Memory layer
SynOI Vault (memory tier + canonical tier). Resonance retrieval. Cross-vendor verifiable memory with signed receipts.
No memory layer: natoma is a gateway, not a substrate.
Supply-chain guard
SCG covers npm, PyPI, agent skills, and MCP servers themselves. State-divergence + signed releases.
Not addressed.
Standards alignment
CSA, OpenSSF, sigstore, in-toto, IPLD, IETF RFC 8949 / 8152 / 8032, NIST FIPS 204, NIST AI RMF, ISO 42001 (planned), Linux Foundation OIN.
SOC 2 certified; GDPR / CCPA compliant. OAuth 2.1 / SAML / SCIM. No public protocol contribution.
Pricing model
Free Gateway (self-host everything). Paid tiers add operated HITL, mobile push, hosted receipts. Paddle (merchant-of-record).
Free (5 servers / 5 users / 5,000 calls per month) → Pro → Enterprise. Post-acquisition pricing TBD.
MCP-server catalog
synoi-mcp-server bridges Persona, Skills, Recall, and GAP governance tools. Catalog of verified third-party servers is in active build.
100+ verified MCP servers shipped with managed auth. Today, this is their lead.
Brand recognition · enterprise
New brand · 2026. The thesis was on file with VCs 32 days before CSA named the category.
Founded 2024 by ex-Okta exec; $7M seed (Index + Greylock, May 2025); acquisition by Snowflake announced May 2026.

Claims about Natoma and the Snowflake acquisition are drawn from Natoma's public product / pricing pages (natoma.ai) and the Snowflake acquisition announcement of 2026-05-28. We will correct any inaccuracy on request: email via the contact form.

Why the shape matters

Your governance layer should not belong to your data warehouse.

A managed MCP gateway bundled with Snowflake will be excellent for Snowflake customers. For everyone else (Databricks shops, BigQuery shops, multi-cloud shops, on-prem regulated industries, sovereign-cloud customers) it is a cross-cutting dependency that nobody asked for.

The agentic control plane is a category orthogonal to where your data lives. We treat it that way. The Gateway works against AWS Bedrock, OpenAI direct, Anthropic direct, Groq, on-prem Llama, and anything else that speaks an LLM-API shape. Receipts verify against any Ed25519 library in any language.

The substrate underneath - SRAID-Core, GAP, the OID Resolver - is open specification under CC0. Anyone can reimplement, fork, audit. Nothing in the protocol layer requires SynOI infrastructure to operate.

Two closed shapes, one open shape

ServiceNow + NVIDIA

AI Control Tower bundled with an ITSM/GRC platform. Closed protocol. See comparison →

Natoma + Snowflake

MCP gateway about to be bundled with a data warehouse. Open MCP spec; closed gateway, closed audit log. You are reading this comparison.

SynOI

Open protocol layer (SRAID-Core, GAP, OID Resolver) under CC0; reference Gateway is free to self-host. Receipts verify offline. No bundled data plane.

The category is real. The question is who owns the substrate. Read the protocol page →

Run the comparison on your own traffic.

The Gateway is free to install. The receipt verifier is public. The protocol is open. You can prove every claim on this page on your own data, today, without ever talking to us.

Start freeOpen the verifier →