Ship a container or a git push
Deploy a Docker image or a GitHub-connected repository into any project. flowbit runs it, publishes the port, and streams its logs — Kubernetes stays out of your way.
2
Sources live
Docker image and GitHub build
4
Wizard steps
Source → Image → Environment → Review
3
Environments
development · preview · production
0
Plaintext secrets
Only vault key references leave the API
What Deployments is
Deployments is the Deployment Center of every flowbit project. You give it a Docker image — or connect a GitHub repository and let Builds produce one — and flowbit runs it as a container, publishes its port, and keeps a record of everything that happens to it.
Every deployment belongs to a project. You create it through a four-step wizard — source, image or repository, environment, review — and then manage it from its own page: an Overview with status and port, live Logs, Settings for rename, start, stop, restart and delete, and an Activity timeline of control-plane events.
Configuration comes from the project vault. In the environment step you pick variable and secret keys; their values are resolved only when the container starts, and no list or detail response ever returns them in plaintext. Status moves through queued, provisioning, running, stopped, failed and deleting, so you always know where a release stands.
An organization-wide list mirrors every deployment across projects, while creation always happens inside a project. Owners and admins make changes; every member can read deployments, logs and events. The runtime underneath is a replaceable provider, so Kubernetes and host details never leak into the product.
Everything you need to run a service, nothing you have to operate
A developer-first control surface: every deployment belongs to a project, and every action is recorded.
Docker image source
Point at any image and tag, choose the ports to expose, and optionally set CPU, memory, and a restart policy.
GitHub builds
Connect the flowbit GitHub App — each push builds an image and rolls it into a deployment.
Vault environment refs
Select variable and secret keys from the project vault. Values resolve at provision time and are never shown back.
Live logs
Tail container stdout and stderr from the deployment page or the unified Observability viewer.
Start, stop, restart
Lifecycle controls on every list row and in Settings. Delete lives only in the Settings danger zone.
Activity timeline
Create, deploy, fail, and delete events for every deployment — an audit trail, separate from runtime logs.
From image to running in four steps
Source
Docker Image or GitHub. GitLab, Marketplace, and Helm are coming soon.
Image or repository
Docker: image, tag, ports. GitHub: installation, repo, branch, Dockerfile path.
nginx:1.27-alpineEnvironment
Pick vault variable and secret keys — references only, never plaintext.
DATABASE_URLReview & deploy
Confirm the summary and deploy. A GitHub source creates a build first, then the deployment.
The dashboard is just a client
Every action in the Deployment Center maps to a stable, project-scoped REST endpoint documented in OpenAPI.
- Project-scoped writes; an org-wide list for reads
- Owners and admins mutate; any member can read logs and events
- Responses carry only ref keys and non-secret metadata
curl -X POST \
"$FLOWBIT_API/v1/organizations/$ORG_ID/projects/$PROJECT_ID/deployments" \
-H "Content-Type: application/json" \
--cookie "$FLOWBIT_SESSION" \
-d '{
"source": "docker_image",
"name": "web",
"image": "nginx",
"tag": "1.27-alpine",
"ports": [80],
"environment": "production",
"envRefs": [
{ "kind": "secret", "key": "DATABASE_URL" },
{ "kind": "variable", "key": "LOG_LEVEL" }
]
}'Every state is visible
queued
Accepted by the control plane
provisioning
Pulling the image and resolving env refs
running
Container up, port published
stopped
Stopped by you; start again any time
failed
Provisioning error, with an event message
deleting
Tearing down the container
What ships today
| Capability | Status | Notes |
|---|---|---|
| Docker image deploys | Live | Image, tag, ports, CPU/memory, restart policy |
| GitHub builds | Live | GitHub App install, webhook on push |
| Logs | Live | Tail 100 to 5,000 lines |
| Settings & activity | Live | Rename, lifecycle, delete, event timeline |
| Custom domains | Live | Attach from the project Domains tab |
| Metrics & terminal | Coming soon | Per-deployment tabs |
| GitLab, Helm, Marketplace | Coming soon | Listed in the source step |
Common questions
Do I need to know Kubernetes?
No. You give flowbit an image or a repository; the runtime behind it is a replaceable provider and never appears in the UI.
How do secrets reach my container?
You pick vault keys in the wizard. They are resolved when the container is provisioned; list and detail responses never include plaintext.
Who can create or delete a deployment?
Organization owners and admins. Every member can view deployments, logs, and events.
Can I roll back?
Rollback is not a first-class action yet — redeploy a previous image tag. One-click rollback is on the roadmap.
Deploy your first app
Pick a project, choose Docker or GitHub, and ship.

