You select the repository
Connect GitHub, choose the repo, and RepoShip starts from the source of truth instead of asking you to write deployment config first.
Select a repo. RepoShip handles the rest.
RepoShip
Give us the GitHub repository. RepoShip finds the app, builds it, wires the deployment shape, and gets it hosted without making you become the infrastructure team.
Select repoRepoShip configuresHosted for you
Repository selected
RepoShip handles the deployment
1
Select repo
handled by RepoShip
2
Detect app
handled by RepoShip
3
Wire config
handled by RepoShip
4
Build
handled by RepoShip
5
Deploy
rolling out
Input
GitHub repo
Output
Hosted app
Baseline
€6 / month
One repo in, a deployment plan out.
No YAML tour before you know if it can ship.
€6 baseline per small host when one host is enough.
Deployment model
You bring code. RepoShip handles the deployment.
The product is built around the job you actually want done: choose a repository, confirm what RepoShip detected, and let the platform own the build and hosting path.
RepoShip builds the deployment plan
It finds the app, reads scripts and Dockerfiles, maps environment variables, chooses the runtime, and prepares the hosting shape.
We host it in the smallest shape that works
The first target is a deployed app, not a cloud architecture project. More machines and services get added only when the app needs them.
Resource ladder
Handled does not have to mean expensive.
RepoShip hides the deployment work from you, but it still keeps the hosting shape small until the app needs more room.
Prototype
1 machine
One small host, one reverse proxy, one place to run the app.
Growing app
2-3 machines
Split the app when frontend, backend, or data needs separate room.
Production
3-5 machines
More isolation, replicas, storage, and health checks where needed.
Enterprise
Use your platform team
When procurement, compliance, and global scale dominate cost.
Early access