Deployment providers reference
The deployment trigger methods Acrosite supports — Vercel deploy hook triggers and Manual / No Automatic Deployment — plus the providers that appear as Coming Soon and cannot be configured yet.
After Acrosite commits your content to GitHub, it can trigger your host to rebuild. This reference lists the deployment trigger methods Acrosite supports today and what is coming. To set one up, see Configure a deployment trigger.
Available methods
You choose one of these in Deployment Setup:
- Vercel Deploy Hook — triggers a Vercel deploy hook after Acrosite finishes the GitHub commit.
- Manual / No Automatic Deployment — Acrosite does not trigger a deploy; use this if your host already rebuilds from Git pushes or you prefer to deploy yourself. See Use manual deployment.
Planned providers
These providers appear in Deployment Setup as not yet available and cannot be configured yet: Netlify, Cloudflare Pages, GitHub Actions, Custom Webhook, Render, DigitalOcean App Platform, AWS Amplify, GitHub Pages, and Firebase Hosting. Until they ship, use a Vercel deploy hook or manual deployment.
Triggered, not completed
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.