git push. flowbit builds it.
Install the flowbit GitHub App, link a repository and branch, and every push turns into a Docker image and a running deployment.
1
App install
Per GitHub account or organization
6
Build states
queued → succeeded
Auto
Deploy on push
Toggle per linked repository
Dockerfile
Build input
Custom path supported
What Builds is
Builds connects flowbit to GitHub so your workflow stays git push. Instead of a personal token, you install the flowbit GitHub App on an account or organization and grant it the repositories you choose. Signing in with GitHub is a separate identity flow — deploy access always comes from the App install.
Connecting takes four steps from the project's GitHub settings: open the install page, let GitHub redirect back so the installation registers automatically, link a repository with its branch and Dockerfile path, then click Deploy now or simply push. If the redirect ever fails, you can paste the installation ID manually.
Each push to the linked branch triggers a webhook and a build that moves through queued, cloning, building and pushing to succeeded or failed. A successful build creates or updates a deployment carrying the repository and commit, so you always know which code is running.
Build history lives at the organization level and per project, with status, short commit SHA, branch, repository, duration and start time, plus full clone, build and push logs on every build page and in Observability.
Connected in four steps
Connect GitHub
Open the install URL from project settings and pick the account and repositories to grant.
Setup callback
GitHub redirects back to flowbit and the installation registers automatically — no IDs to copy.
Link a repository
Choose the repo, branch, Dockerfile path, and whether pushes auto-deploy.
acme/web · main · ./DockerfileDeploy
Click Deploy now, or push to the branch — the webhook starts a build.
git push origin mainWatch every build move through the pipeline
queued
Push received from the webhook
cloning
Fetching the commit
building
docker build with your Dockerfile
pushing
Publishing the image tag
succeeded
Deployment created or updated
failed
Build logs show the cause
Your workflow stays the same
GitHub App, not a token
Scoped repository access through an App install. Sign-in with GitHub is a separate, unrelated OAuth flow.
Auto-deploy on push
Webhooks trigger a build on the linked branch; turn it off to deploy only on demand.
Full build logs
Every clone, build, and push line is kept on the build detail page and in Observability.
Commit metadata
Deployments created from a build carry the repo and commit, so you always know what is running.
Org-wide history
See builds across every project, or filter to one project.
Recovery built in
If the redirect fails, paste the installation ID under Settings → GitHub → “Having trouble?”.
If it has a Dockerfile, it builds
flowbit builds exactly what your Dockerfile describes — no buildpack guessing. Point the link at any path in the repo.
- Root or monorepo sub-path Dockerfiles
- The first exposed port is published for the deployment
- Environment comes from vault refs, not the image
FROM node:22-alpine AS build
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:22-alpine
WORKDIR /app
COPY --from=build /app ./
EXPOSE 3000
CMD ["npm", "start"]What every build records
| Field | Example | Shown in |
|---|---|---|
| Status | succeeded | Builds list, build detail |
| Commit | a1b2c3d | Builds list, deployment |
| Branch | main | Builds list |
| Repository | acme/web | Builds list, deployment |
| Duration | 1m 42s | Builds list |
| Logs | clone · build · push | Build detail, Observability |
Example values are illustrative.
Common questions
Is “Sign in with GitHub” the same connection?
No. Signing in uses OAuth for your identity; deploys use a separately installed GitHub App with repository-scoped access.
Do you support GitLab?
Not yet. GitLab appears as Coming soon in the deployment wizard.
Are there preview environments per pull request?
PR previews are not part of this release; builds run for the linked branch.
What if the build fails?
The build is marked failed with its logs, and the currently running deployment is left untouched.
Link your repository
Install the GitHub App and your next push deploys itself.
Security & compliance
flowbit runs on independently audited security, privacy and cloud controls — so your apps and data meet the standards your customers expect.
