Works with the host you already use
Eddy deploys previews and merged changes through your hosting provider’s own API. No migration. No rebuild.
Firebase Hosting
Connect a project and Eddy deploys previews and merges through the Firebase Hosting API.
Vercel
An API token and your project/team ID are enough for Eddy to publish through Vercel.
Cloudflare Pages
Publish through the Cloudflare Pages API with a scoped token and your account/project IDs.
Netlify
A personal access token and your site ID connect Eddy to the Netlify API.
Railway
Publish through the Railway API using an account or team token.
Anything else
No API integration? Drop an eddy.json in your repo root with your build and deploy
commands. No credentials needed. Eddy just runs them.
Nothing to install on the client site
Eddy works from the outside. There is no SDK to add and no rebuild required to start. A snapshot of your live site is enough for the client to point and click. An optional one-line bridge script makes element targeting more precise, but you can skip it.
Repository access is the only thing Eddy asks for, and only for the repo you connect. Hosting credentials stay server-side and never show up in the browser.