Zero-config builds
Detect the project, choose the provider, and generate the complete build plan automatically.
Build anything.
Deploy anywhere. Automagically.
Anybuild detects your app, builds it, and deploys it to multiple environments with a simple CLI and zero-config defaults.
Providers
Deployments
Static Sites
Node.js
Python
PHP
AnybuildDetect · Build · Adapt
Local preview
Cloudflare
Wasmer
Vercel
Fly.io
Static sites, Node.js, Python, and PHP projects flow through Anybuild. Frameworks including Hugo, Docusaurus, MkDocs, Gatsby, Next.js, Astro, Vite, Django, FastAPI, Flask, WordPress, Laravel, and Symfony become local previews, Wrangler deployments, Wasmer packages, or Docker containers for Cloudflare, Wasmer, Vercel, and Fly.io.
Install Anybuild
Choose your preferred installation method
$
curl -fsSL https://anybuild.run/install | shUse anybuild
Feature Highlights
Every framework, every runtime, everywhere, built and deployed wherever you need.
One command workflow
Build, package, and prepare every project through one predictable command.
Framework-aware
First-class detection across static sites, Node.js, Python, PHP, and more.
Optimal deployments
Anybuild only includes the files and dependencies that are strictly required to run your app. This results in up to 50× smaller deployed containers.
How it compares
A direct capability comparison across today’s application build tools.
| Capability | Anybuild | Railpack / Nixpacks | Devbox | Heroku Buildpacks |
|---|---|---|---|---|
| Adapt the build to different artifactsBuilds can target different artifact formats and runtimes without changing the application. | ||||
| Can deploy to Edge providersDeploys non-Docker artifacts directly to Edge providers without requiring a container image. | ||||
| Can build with your local toolsRuns builds directly with the toolchains already available on the developer's machine, without requiring a container. | ||||
| Programmable buildBuild behavior can be expressed as code instead of being limited to fixed configuration. | Via Starlark | |||
| Optimal deployment sizeDeployment artifacts contain only the files and dependencies required to run the application. | ||||
| Supports migrations and jobsSupports one-off commands such as database migrations, release tasks, and background jobs. | ||||
| Supports build cacheReuses unchanged dependencies and build outputs to make subsequent builds faster. | ||||
| Frameworks supportedThe number of frameworks, providers, templates, or official buildpacks supported by each tool. | 64 | 12 / 24 | 38+ | 13+ |
Frequently Asked Questions
Short answers about Anybuild’s detection, environments, compatibility, and scope.
Does Anybuild require Docker?
No. Local building and local preview are the defaults. Docker is optional and only selected with --docker or --docker-client.
Does --docker run the application in a container?
No. Docker is a build backend: it executes build steps in an isolated container and exports artifacts into .anybuild. Runtime selection is separate; use the local runner or add --wasmer.
What if detection chooses the wrong provider?
Force a registered provider, inspect the plan, and regenerate the project definition.
anybuild plan . --provider node
anybuild . --provider node --regenerate --startWhich platforms can Anybuild deploy to directly?
The current Rust implementation publishes directly to Wasmer or writes Wasmer deployment configuration. Other platforms can integrate the CLI or SDK and consume the generated plan and artifacts, but Anybuild does not currently expose generic Cloudflare, Fly.io, or OCI-image deployment commands.
Can Anybuild be used without the CLI?
Yes. The anybuild Rust crate exposes the same synchronous generate, plan, build, run, deploy, and auto operations with structured options, outcomes, errors, and events.