Move your repo to Anvil. We handle the rest.
Paste your GitHub or GitLab URL. Anvil fetches your stack, provisions a managed Anvil App, and deploys it on its own subdomain — without you scaffolding a fresh project or wiring CI.
Three steps to a live site
Paste your repo URL
Drop in a GitHub or GitLab repo URL. We auto-detect the provider and authorise via OAuth — your code stays where it lives, Anvil only gets clone access.
We detect your stack
Anvil reads your composer.json, package.json, Gemfile, requirements.txt, or pom.xml and picks the right runtime. You confirm or override.
Deploy on Anvil Hosting
A managed Anvil App spins up on your own *.anvilhosted.app subdomain with TLS, SQLite, scale-to-zero, and PR-on-merge auto-deploy. Custom domain optional.
What we auto-detect
Eleven stacks, hand-rolled rules. No LLM call, instant.
| File checked | Signal | Stack |
|---|---|---|
| composer.json | laravel/framework | Laravel |
| package.json | next | Next.js |
| package.json | astro | Astro |
| package.json | nuxt | Nuxt.js |
| package.json | @angular/core | Angular |
| package.json | express | Express |
| Gemfile | gem 'rails' | Ruby on Rails |
| requirements.txt or pyproject.toml | django | Django |
| requirements.txt or pyproject.toml | fastapi | FastAPI |
| pom.xml or build.gradle | spring-boot-starter | Spring Boot |
No marker matches? Pick the stack manually — every supported runtime is on every plan.
What you keep
Your source repo
Code stays on GitHub or GitLab. Anvil never owns or mirrors your repo. Disconnect any time and your code is unaffected.
Your git history
No force-pushes, no rewriting. Branch protection rules you set on GitHub / GitLab are respected.
Your workflow
Open PRs the way you always did. Anvil deploys on merge to the branches you configure (main → production, staging → staging).
Your secrets
Set env vars on the project. They live in Anvil's encrypted store — never in the repo, never in the deploy logs.
Frequently asked
Does Anvil work with private repos?
Yes. The OAuth flow grants Anvil clone access scoped to the specific repo. Tokens are stored encrypted; only the deploy machine sees them when cloning.
I have a monorepo — can I deploy a subfolder?
Not yet. v1 deploys the repo root. A subpath flag is on the roadmap; in the meantime, point Anvil at a deploy-only branch that contains just the app you want hosted.
How do I configure environment variables?
After import, the project's Infrastructure settings page has an env var editor. Values are encrypted at rest and injected into the site machine on every deploy.
Can I use my own domain?
Yes. Add it on the Infrastructure page; Anvil issues a TLS cert via Let's Encrypt and routes traffic. CNAME to your *.fly.dev hostname or use the on-screen instructions.
How do I roll back a bad deploy?
Each deploy is tied to a commit SHA — push a revert commit (or the PR's revert button) and the next deploy lands automatically. There's no destructive cutover.
Ready to bring your repo over?
Free tier covers one site, scale-to-zero, 3GB bandwidth. No credit card required.