BuildfyioBETA
Start deploying
Docs

Quickstart

From zero to a production URL in about two minutes.

1. Create a workspace

Sign up at buildfyio.com/sign-up. A workspace holds your projects, team members, and billing. The Hobby plan is free and needs no card. For its first 7 days a Hobby workspace without a payment method shares limited capacity with other new workspaces (see new-workspace limits); adding a card lifts that without a charge.

2. Connect GitHub

Go to Settings → Git providers and click Connect GitHub. You authorize Buildfyio once on GitHub; if it is not yet set up on your account or organization, GitHub asks which repositories to grant on the same trip. That grant is what powers push-to-deploy: every commit to your production branch triggers a build automatically. To add repositories or another organization later, use Manage GitHub access on the New project page (or Manage on GitHub in Settings).

3. Create a project

  1. Click New project and pick a repository.
  2. Discovery scans the repo and lists every deployable app — a single Next.js app, or all the apps of a monorepo. Pick the ones you want.
  3. Review the detected build settings (framework, build command, start command, port). They are editable, but detection is right for the overwhelming majority of repos.
  4. Paste your .env into the environment step if the app needs secrets at build time — variables land before the first build runs.
  5. Click Deploy.

The first build takes one to five minutes depending on the stack. When it finishes your app is live at <project>.buildfyio.com with TLS already issued.

4. Push to deploy

git commit -am "ship it"
git push origin main   # → builds and deploys automatically
Supported out of the box: Next.js, Nuxt, SvelteKit, Astro, Remix, Vite, CRA, Gatsby, NestJS, Express, Fastify, Django, FastAPI, Flask, Rails, Laravel, Go, Rust, Java, .NET, Bun, Deno, Elixir, PHP — plus any repository with its own Dockerfile.

What you get on every deploy

  • A unique preview URL per deployment and a stable production URL.
  • Automatic HTTPS on platform and custom domains.
  • Build and runtime logs, streamed live.
  • One-click rollback to any previous successful deployment.
  • Cookieless web analytics, injected automatically — no snippet needed.
Projects →How builds work →Environment variables →