You commit. We ship.

Install the Infrly GitHub App and choose whether it can see all of your repositories or only the ones you select. When you create a service, you pick a repository and a branch, usually main. From then on, every push to that branch reaches Infrly through a GitHub webhook within seconds and starts a fresh build. Pushes to other branches are ignored, and you can redeploy manually at any time without a new commit.

Web services and cron jobs build from source on seven runtimes: Node.js, Python, Go, Java, Ruby, PHP, and Rust. You don't write a Dockerfile. Infrly detects the runtime and prefills install, build, and start commands you can override. Common frameworks like Express, NestJS, FastAPI, Django, Spring Boot, Rails, Laravel, Gin, and Axum work with the defaults or a one-line change to the start command.

No. The new version starts alongside the one that's already running, and traffic only switches over once it passes its health check. If the new version never becomes healthy, the previous one keeps serving and nothing is torn down. For static sites, a failed build leaves the last published version live.

Every service is billed on its own, based on the plan you pick, and prorated to the days it actually existed that month. There's no platform or per-seat fee on top. Web services have a free plan, and static sites have limited free access. Cron jobs have no monthly price at all: you pay per execution, for exactly as long as each run takes, so a job that doesn't run costs nothing.

Not for the free web service plan or for static sites on limited free access. Paid plans, databases, Key Value instances, and cron jobs need a validated payment method, because they cost real resources from the moment they exist or first run. Your Billing page shows a running usage estimate, so you always know what the month is trending toward.

Yes. Every web service and static site gets an automatic *.infrlyapp.com URL with HTTPS, and you can add your own domain alongside it. Add a CNAME record at your DNS provider and click Verify. Infrly then issues and renews a TLS certificate for it automatically, usually in under a minute once DNS resolves.

Every PostgreSQL database is backed up automatically once a day, with 7 days of retention by default, and you can change that window at any time. You can restore to the most recent backup or to any point in time within the window. A restore always creates a new database next to the original, so trying one never puts your live data at risk.