Five hosts
Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify, each on your own account.
Deploy to your own host
Deploy to your own Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify
Connect your GitHub, GitLab or Bitbucket account and your own hosting account, and publish to Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify from the dashboard. The hosting account and its bill are yours.
What it is
A connection to the static and front-end hosts you already use. Connect the repository provider your code lives in — GitHub, GitLab or Bitbucket — and the host account you want to publish to.
Some of these hosts are available only on your own account, and we say why. Vercel's Hobby plan is for non-commercial, personal use, so connect a paid Vercel team for a commercial site. AWS Amplify bills per gigabyte and per build minute, so it runs only on your own AWS account.
What you get
Five hosts and three repository providers.
From your repository
Connect GitHub, GitLab or Bitbucket so the host builds from the repository your code already lives in.
Vercel, the commercial way
Vercel's Hobby plan is restricted to non-commercial, personal use. For a commercial site, connect a paid Vercel team.
AWS Amplify on your own account
Amplify bills per gigabyte and per build minute, so it is offered only on your own AWS account, where those charges are yours to see and control.
Checked before it is saved
Each credential is validated with the provider before anything is stored.
Stored encrypted, deleted on disconnect
A credential that passes is kept encrypted in our secrets vault, and disconnecting deletes it.
Step-by-step guides
Each guide shows where to create the key on the provider's side, what it needs, and how to connect it in the dashboard.
Bring your own accounts: the overview
Read the guide →Netlify
Read the guide →Vercel
Read the guide →Render
Read the guide →Azure Static Web Apps
Read the guide →AWS Amplify
Read the guide →GitHub
Read the guide →GitLab
Read the guide →Bitbucket
Read the guide →How it works
Connect the two accounts, then publish.
Connect your repository provider
Connect your GitHub, GitLab or Bitbucket account.
Connect your host
Connect your Netlify, Vercel, Render, Azure Static Web Apps or AWS Amplify account. It is validated before it is saved.
Deploy
Publish your site to the host you connected, on your own account.
Pricing
Deploying to your own host is not an add-on.
We charge nothing for the connection. Your host bills you directly, on your own account and plan, for what it builds and serves. Your Zinn Digital® hosting plan is billed as normal.
Build minutes, bandwidth and plan limits are your host's. Check its terms for commercial use — Vercel's Hobby plan does not allow it.
Why it is built this way
Front-end teams often have a host they already know. Deploying to it from the same dashboard as the rest of your estate means you keep that host and still manage everything in one place.
We name the terms that bite, because a site taken down for breaching a free plan's terms costs more than a paragraph of small print now. That is why Vercel needs a paid team for commercial work and Amplify runs only on your own AWS account.
Questions people ask before they buy
Which hosts can I deploy to?
Netlify, Vercel, Render, Azure Static Web Apps and AWS Amplify, each on your own account.
Which repository providers work?
GitHub, GitLab and Bitbucket.
Can I use Vercel's Hobby plan?
Only for a non-commercial, personal site. Vercel's Hobby plan is restricted to non-commercial, personal use, so connect a paid Vercel team for anything commercial.
Why is AWS Amplify only on my own account?
Amplify bills per gigabyte and per build minute. Those charges belong on the account of whoever runs the site, so Amplify is offered only on your own AWS account.
Who bills me for hosting on these platforms?
The platform does, directly, on your own account. We charge nothing for the connection, and your Zinn Digital® hosting plan is billed as normal.
How are my credentials stored?
They are validated with the provider before saving, stored encrypted in our secrets vault, and deleted when you disconnect.
Help with this
Step-by-step guides from our knowledge base, written for exactly this.
Deploy a static site to your own Vercel team
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.
Read the guide →Deploy a static site to your own Netlify account
Create a Netlify personal access token and connect it, so you can publish static sites to your own Netlify account from your dashboard.
Read the guide →Deploy a site to your own CDN account
Connect your own Cloudflare account, put a site on it, and move a site between accounts without taking it down.
Read the guide →Connect your repository and host
Create an account, open Integrations, connect GitHub, GitLab or Bitbucket and the host you publish to, and deploy from the dashboard.
Get started