Connect your own accounts — CDN, DNS, code hosting, SEO data and more

You can run parts of your hosting on accounts you own — your own CDN, your own DNS, your own code hosting — and still manage everything from your Zinn® dashboard. The account, the contract and the bill stay yours, so moving away from us later costs you nothing on that front. Each kind of account has its own guide with the exact steps for creating the key.

What you can connect

• Cloudflare account (Pages, CDN & DNS) — publish to Cloudflare Pages and serve DNS and

cache from your Cloudflare account.

• Code hosting — GitHub (a token, or the Zinn® GitHub app), GitLab and Bitbucket, so a push

deploys a site and every branch can have a preview.

• Static hosting — Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify. Vercel and

AWS Amplify are available only on your own account.

• Your own DNS — Cloudflare, deSEC, Hetzner, ClouDNS, Bunny, Azure DNS, Amazon Route 53,

DigitalOcean and Gcore.

• Your own CDN — Cloudflare, Bunny, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and

Akamai.

• Your own SEO data — Majestic, Ahrefs, Moz and DataForSEO keys, so metrics for your sites run

on your subscription instead of ours.

• Video & streaming, Web app firewall, AI inference — Gcore Video Streaming, Gcore WAAP and

Gcore Everywhere Inference, on your own Gcore account only.

Two related things live elsewhere. The account your domains are registered with has its own guide, Connect your registrar and we keep your nameservers pointed at your site. And your own AI provider keys (Anthropic, Google Gemini, OpenAI, xAI) are added under Zinn® AI → Your keys, not here.

Connect one

1. Create the key at the vendor, using the guide for that vendor.
2. Open Integrations in your dashboard and choose Connect an account.
3. Pick the group, then the account, fill in what the form asks for, and press **Connect

account**.

You can connect more than one account of the same kind — an agency might keep client work on one Cloudflare account and its own sites on another — and choose per site or per domain.

How your keys are kept

We test a key before saving it; a key that does not work is never stored. A key that works is kept encrypted in our secrets vault, never in our database, and is never shown again. For CDN, DNS and Cloudflare connections, a checklist beside the connection shows which permissions we could confirm, so a missing one is visible before you rely on it.

We use a key only for what its connection is for. We ask for the narrowest permissions that work, and each guide lists them.

Disconnecting

Integrations → the account → Disconnect deletes the stored key at once. Anything using it stops at its next action and says so. Disconnecting does not undo what was already done, and it removes our copy of the key — revoke it at the vendor as well if it may have leaked.