Deployment providers reference
The deployment methods Acrosite supports: Git-connected, Vercel, Netlify and Cloudflare Pages deploy hooks, and Manual.
After Acrosite commits your content to GitHub, your host rebuilds the site. This reference lists the deployment methods Acrosite supports. To set one up, see Configure a deployment trigger.
Available methods
You choose one of these in Deployment Setup:
- Git-connected (recommended) — your host is connected to the repository and builds from each commit Acrosite makes. Acrosite sends no trigger and stores no URL. This works with Vercel, Netlify, Cloudflare Pages and most other Git-based hosts.
- Vercel — a Vercel deploy hook URL (
https://api.vercel.com/v1/integrations/deploy/...). - Netlify — a Netlify build hook URL (
https://api.netlify.com/build_hooks/...). - Cloudflare Pages — a Cloudflare Pages deploy hook URL (
https://api.cloudflare.com/client/v4/pages/webhooks/deploy_hooks/...). - Manual — Acrosite does not trigger anything; you deploy yourself. See Use manual deployment.
Each hook provider accepts only its own hook address, and Acrosite checks the saved address again before every trigger.
Important
If your host is also connected to the repository, a deploy hook makes every publish build twice — once from the commit and once from the hook. Choose Git-connected, or turn off the host's automatic Git builds for that branch.
Triggered, not completed
Important
Acrosite records deployment trigger requests; a trigger does not mean the build finished. A successful trigger means your provider accepted the request. Owners and Admins see the build status your host reports to GitHub with each publish — see Build status and Understand Deployment Logs.
Keeping hook URLs safe
Your deployment hook URL is stored server-side and shown masked in the interface. Configure a provider once, test it, and Acrosite uses it only after a successful commit. See How Acrosite handles secrets.