Push to deploy · GitHub & GitLab
GitDeploy straight to Kepler.
Now in beta — connect your repo, push to main, and watch it build and go live on Swedish infrastructure. No YAML maze, no mystery pipeline — just git push and you’re live.
GitHub & GitLabBuild logs & rollbacksEU/Sweden
$ git push origin main
# Kepler GitDeploy picks it up
→ detected: Node 20 · npm build
→ building… ████████████ done (38s)
→ deploying to swe1…
✓ live at https://app.yourdomain.eu
# Kepler GitDeploy picks it up
→ detected: Node 20 · npm build
→ building… ████████████ done (38s)
→ deploying to swe1…
✓ live at https://app.yourdomain.eu
Connects with
GitHub
GitLab
+ any Git remote
How GitDeploy works
Push to main. We do the rest.
1
Connect repo
Authorize GitHub or GitLab. Pick a branch — usually main.
2
Auto-detect build
We sniff your stack (Node, static, Docker) and set sensible defaults.
3
Build & deploy
Every push builds on a Planet in Sweden, with live logs you can read.
4
Rollback anytime
Bad deploy? One click back to the previous build. Snapshots included.
Why GitDeploy on Kepler
The convenience of a PaaS, the control of your own Planet.
No pipeline maze
No 200-line YAML. Sensible auto-config you can override when you need to.
EU build & run
Your code builds and runs in Sweden. Source never leaves EU soil.
It’s still your Planet
Drop into SSH, add a database, scale the flavor. No black box underneath.
Straight talk: GitDeploy is in active build toward our App Engine on the roadmap. Early-access slots are opening now — join the list and we’ll onboard you as the push-to-deploy flow rolls out.
Get early access to GitDeploy.
Connect a repo and we’ll set you up as push-to-deploy opens — GitHub or GitLab, your choice.