Knowledge base
Create a Vercel token scoped to a paid team and connect it — Vercel sites are only published to your own account, never to one of ours.
Connecting your own Vercel account lets you publish a static site to your Vercel account from your Zinn® dashboard. You own the project and the bill; we handle the deploy, the custom domain and the DNS records.
A Vercel account, and for any business or revenue-earning site, a paid team. Vercel's free Hobby plan is restricted by Vercel to non-commercial, personal use, which is why we never place a customer's site on a Vercel account of ours: Vercel is available only on your own account. We cannot read your plan from Vercel, so connecting a Hobby account works — but using it for a business site would breach Vercel's terms on your account.
In Vercel, open Account Settings → Tokens from your personal account and choose Create. Name the token, and in the scope dropdown choose the team that owns your projects — a token scoped to the wrong team cannot see them. Choose an expiration and press Create Token. Copy it — Vercel shows it once.
Open Integrations in your dashboard and choose Connect an account. Pick Static hosting (Netlify, Vercel) as the group and Vercel as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
target. Choose it and we publish the site's build to a project on your account.
needs so the domain resolves to the new host.
your own vendor dashboard.
than guessing it, and show you the exact record on the domain's page.
Your projects do not appear. The token was scoped to a different team, or to your personal account. Create a token scoped to the team that owns them.
Deploys stop for the day. The Hobby plan caps deployments per day. Moving to a paid team removes that and the non-commercial restriction.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →