I built Shiprr, a Git-based platform for deploying web apps without having to wire up your own deployment pipeline, runtime fleet, or control plane.
It is aimed at long-running web apps, where you want the convenience of a PaaS but still need control over region, resources, domains, and access.
What Shiprr does
Shiprr supports:
- GitHub and GitLab repositories
- Source builds
- Automatic framework detection
- Regional runtime placement
- Custom domains
- Managed TLS
- Access controls
- App sizing from the dashboard
The goal is to make the path from Git push to a live app as direct as possible, while still keeping deployment behavior understandable.
Why I built it
A lot of deployment tools fall into one of two extremes:
- very simple, but limited
- very flexible, but operationally heavy
I wanted something in between: a platform that feels lightweight, but still supports real production workflows.
What it is not
Shiprr is not trying to be:
- a serverless platform
- a general infrastructure control plane
- a replacement for all cloud services
It is focused on deploying web apps cleanly, with sane defaults and enough control for production use.
Current direction
The main focus is:
- Git-based deployments
- regional runtime placement
- predictable app sizing
- basic operational visibility
- a workflow that stays simple for smaller teams
Feedback welcome
I would especially appreciate feedback on:
- whether the positioning makes sense
- what would make it easier to adopt
- what you would expect from a PaaS before trusting it for a real app
Site: https://shiprr.app
Top comments (0)