How it works

Give RepoShip a repository. We turn it into a deployment.

The flow is intentionally simple: select the repo, confirm what RepoShip detected, and let the platform handle the build, configuration, hosting shape, and rollout path.

Select the repository

Install the GitHub App, pick the repo, and give RepoShip permission to inspect only the code you chose.

RepoShip finds what can be deployed

It checks package manifests, lockfiles, framework conventions, Dockerfiles, build scripts, output folders, and environment examples.

RepoShip wires the deployment shape

The plan turns the repo into concrete decisions: app path, build command, runtime adapter, required variables, host count, and routing.

We build it and handle hosting

The current loop reaches RepoShip-owned builds and artifacts. Live publishing, DNS, and resource provisioning are rolling out in early access.

Early-access boundary

The promise is handled deployment. The rollout is staged.

RepoShip is being built toward the repo-in, app-hosted loop while keeping the current early-access boundary clear.

Repository selection, scanning, and deployment-plan generation are the center of the current product.

Build jobs run in RepoShip-owned infrastructure so the app moves from source code toward a hosted artifact.

Live URLs, DNS wiring, and resource-tier provisioning are the early-access rollout path.