Knowledge base
Create a Render API key and connect it, so your static sites build from your repository on your own Render account.
Connecting your own Render account lets you publish a static site to your Render account from your Zinn® dashboard. You own the project and the bill; we handle the deploy, the custom domain and the DNS records.
A Render account, and a connected GitHub, GitLab or Bitbucket account holding the site's code — Render builds sites from a repository and cannot accept an uploaded build. Render's free static sites allow commercial use.
In the Render Dashboard, open Account Settings, find API Keys and create a new key. Render shows the full key once, when it is created; copy it then.
Open Integrations in your dashboard and choose Connect an account. Pick Static hosting (Netlify, Vercel) as the group and Render 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. Render builds from a repository — it has no way to accept an uploaded build — so the site's code must come from a connected GitHub, GitLab or Bitbucket repository. Connect one first if you have not.
and trigger deploys. The domain's page shows any DNS record Render needs.
The site cannot be created. Check that a repository account is connected and that Render itself can reach the repository — Render may ask you to authorise its own access to your Git provider in its dashboard.
The key was revoked. Render keys stay valid until revoked; if yours was, create a new one.
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 →