Zeotap on Snowflake Native App

Zeotap is available as a Snowflake Native App. Install it from the Snowflake Marketplace and the entire Zeotap CDP runs inside your own Snowflake account on Snowpark Container Services (SPCS) — control plane, event ingest, sync orchestrator, identity engine, and forwarder. You operate it through the same composable.zeotap.com UI as cloud customers, but the data stays put.

Why install the Native App

The Native App is built for teams whose compliance posture, billing preference, or data-residency rules push back against shipping customer data through a vendor cloud.

• Customer data never leaves your Snowflake account. Profiles, events, audience computations, identity graphs, and warehouse writes all happen inside SPCS in the region your Snowflake account runs in. Egress is limited to the External Access Integrations (EAIs) you explicitly approve for each destination family.
• Marketplace billing. Pay for Zeotap through Snowflake credits and the Marketplace billing channel rather than receiving a separate vendor invoice. SPCS compute and warehouse usage are charged on the credits you already buy from Snowflake.
• Zero infrastructure to operate. Zeotap ships the application package; Snowflake provisions the compute pool, mounts the block volumes, schedules the services, and exposes the public ingress endpoint. There is no Kubernetes to manage, no VPC to peer, no IAM roles to author beyond the consumer-side bootstrap.
• Data-residency follows your Snowflake region. The app runs wherever your account runs — AWS us-east-1, Azure West Europe, GCP asia-southeast1 — so residency is a property of your existing Snowflake contract, not a separate data-processing addendum.
• Same UI as the cloud product. Your team uses composable.zeotap.com and signs in with email or Google. The browser only ever talks to the Zeotap cloud origin; the cloud forwards your requests to your in-account control plane through a reverse-proxy that authenticates with a keypair minted at install time.

How it fits together

The cloud control plane on the left handles authentication, account/workspace provisioning, the events ingest endpoint, and a reverse-proxy that swaps short-lived UI tokens for the encrypted keypair credential bound to your install. Everything on the right — the long-running CDP services and the ephemeral job services that run sync, loader, identity, and journey work — lives inside your Snowflake account on SPCS.

The proxy chain is one-way: the browser talks to composable.zeotap.com, the cloud forwards through Snowflake’s SPCS public ingress, and the in-account control plane handles the request locally. Zeotap runs its SQL through the warehouse you bind at install; the databases it reads from and writes to are configured per source and destination, and you grant access to each one explicitly.

What you’ll do to get started

Installing the Native App takes about ten minutes of operator time and a couple of minutes of SPCS warm-up.

1. Install from Marketplace in Snowsight — Snowflake creates an Application object in your account from the Zeotap Application Package.
2. Bind the warehouse reference and approve EAIs for the warehouse SPCS jobs should run against, plus each destination family you intend to use.
3. Run two post-install SQL scripts as ACCOUNTADMIN: post-install-eais.sql to bind the per-destination EAIs, and post-install-auth.sql to mint the proxy keypair and register the install with the Zeotap cloud.
4. Open the claim URL the registration step writes into APP_DATA.CLOUD_REGISTRATION and sign in. Zeotap ties the install to your account and creates a default workspace.

The full walkthrough — including the SQL templates with explanatory comments, common pitfalls, and the EAI catalog — is in Installation.

Where to go next

• Architecture — the SPCS service inventory, the event hot path, and the proxy chain in detail.
• Installation — stage-by-stage walkthrough from Marketplace to active workspace.
• Auth Setup — why the proxy user/role exists, what GENERATE_PROXY_KEYPAIR does, and how to rotate or harden the credential.
• Sources — adding additional Snowflake databases as native-app sources, the GRANT script the UI generates, and why SELECT-only is enough.
• Destinations — the per-destination EAI mapping, the pre-bound catalog, and BYO-EAI for destinations outside the catalog.
• Troubleshooting — the errors operators hit most often during install and how to clear each one.
• FAQ — data-residency, pricing, upgrades, and uninstall questions.

If none of the Native App reasons apply to your team, the cloud-hosted Zeotap on composable.zeotap.com is the simpler default — see Getting Started for that path.