Sitepins doesn’t host or deploy your site. It commits to your repository, and whatever you already have connected to that repository builds — exactly as it would for a commit you pushed from your laptop.
That means if your site is already deployed, deployment is already configured. There’s nothing to set up.
Already Deployed Somewhere
Vercel, Netlify, Cloudflare Pages, GitHub Actions, GitLab CI, a self-hosted runner — all of them watch your repository for commits. Sitepins commits are ordinary commits, so every one of them triggers a build with no extra configuration, no webhooks, and no build hooks.
Add your live URL under Project Settings → General → Website so Sitepins can show the site preview and use the correct domain in the SEO search preview.
Not Deployed Yet
The project’s Getting Started checklist includes a Deploy Site step with two options.
Deploy to Vercel
One click sends you to Vercel’s import flow with your repository pre-filled. Vercel detects your framework, builds it, and deploys. Once it’s live, every Sitepins commit rebuilds it automatically.
Already deployed elsewhere
If the site is already live, paste the URL and Sitepins records it. This is the same as the Website field in General settings.
Build Status
Pro plan. Available on Pro and above, during the free trial, and in every self-hosted install.
Once a build is reporting, Sitepins shows its status in two places: the Build Status row on the project overview, and a badge in the editor header after you publish.
| Status | Meaning |
|---|---|
| Building… | A build is running |
| Pending | Queued, not started |
| Success | Build passed |
| Failed | Build failed |
| Inactive | The check is registered but not running |
| No Status | Nothing is reporting a status for this repository |
Status is read from GitHub commit statuses or GitLab pipeline statuses. Anything that reports to those — Vercel, Netlify, GitHub Actions, your own CI — shows up here. Sitepins polls while a build is in progress and stops once the result is final.
No Status is not an error. It means nothing is reporting a build status for your repository — either nothing is deployed from it, or your host doesn’t post statuses back to Git.
When a build fails, Sitepins tells you it failed but not why. Follow through to your host’s logs for that. If the failure was caused by a content change, undo the commit.
Preview Deployments
Two different things people call “preview”:
- Live preview runs your site in a sandbox from uncommitted changes. Nothing is pushed. This is Sitepins’ own feature.
- Your host’s deploy previews build from a pushed branch or pull request. That’s your host’s feature, and it works with Sitepins commits like any other.
They complement each other: live preview while writing, deploy previews for review on a branch.
Deploying From a Branch
If you publish to a staging branch and merge to main when ready, configure your host to deploy main to production and staging to a preview URL. Sitepins doesn’t need to know about any of that — it just writes to whichever branch the project is on.
Common Issues
Commits land but nothing deploys. Check that your host watches the branch Sitepins is publishing to. Publishing to staging while your host builds main produces exactly this.
Images 404 on the live site but look fine in the editor. The Public Folder setting is wrong. See Configure Your Site.
The build fails after a config change. A config file value likely broke it. Check your host’s logs, then undo the commit from version history.