Your repo is the deploy button
No dashboard rituals. The branch you push is the version that ships, and history doubles as release history.
git-native hosting demo
Push a repo.
Push a repo.
Get a running site.
DockPool watches your Git repository and turns every push into a container. This page itself is the proof — built from a plain Dockerfile, served straight out of nginx.
The pipeline
Step 01
Push
Commit to any branch of a connected repository. No webhooks to wire by hand.
Step 02
Build
DockPool finds the Dockerfile at the repo root and builds it in an isolated pool worker.
Step 03
Serve
The fresh image replaces the old container behind the same URL. Rollback is just another checkout.
FeaturesEverything a demo needs, nothing it doesn't.
A deliberately small surface. The pool does three jobs and stays out of the way while doing them.
Pool workers
Every build runs in its own container, so a broken commit can't touch anyone else's.
Dockerfile detection
If there's a Dockerfile at the root, DockPool uses it. This demo ships exactly two lines of build instructions.
Metrics you can verify
Build time for this page: — metric pending first run. We show dashes until we can prove them.
How this page deployedThe whole story fits in one terminal.
This is the actual recipe behind the site you're reading — no hidden steps.
Write the page
One HTML file. Fonts from Google, styles inline, no framework to update later.
Add a Dockerfile
FROM nginx:alpine plus one COPY. That's the entire deployment artifact.
Let the pool build it
Push, wait for the green tick, refresh. The kitten at the bottom has shipped four times already.
Your next push is a deploy.
Connect a repo with a root Dockerfile and watch the pool pick it up.
Back to the top