Deploy a static site to your own Render account

What connecting it does for you

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.

Before you start

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.

1. Create the key at Render

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.

2. Connect it here

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.

What happens next

• When you create or move a static site, this account appears as a deploy

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.

• We create the service on your account, point it at the repository, attach your custom domain

and trigger deploys. The domain's page shows any DNS record Render needs.

• Usage and billing are on your account, visible in your own vendor dashboard.

If it does not connect

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.

Disconnecting

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.