Public beta · Free while in beta

Deploy web apps, static sites, cron jobs and databases from GitHub.You commit. We ship.

Infrly is a deployment platform for web apps, static sites, cron jobs and managed PostgreSQL and Key Value databases. Connect a GitHub repository, and every push is built, deployed and kept running, with HTTPS, backups and monitoring built in. Plain code and standard databases, so you're never locked into one cloud.

Free during the betaNo credit cardAutomatic HTTPS
acme / api-server Deploying

Fix rounding in checkout totals

main 4f2c9a1 pushed via GitHub · just now
  1. Build21.8s

    Node.js detected · npm run build

  2. Package6.2s

    Release packaged and ready to ship

  3. Deploy…

    Health check on /health → 200

    Previous version a91e07d keeps serving until then

  4. Live—

    https://api-server-ab12cd.infrlyapp.com

HTTPS certificate Zero-downtime rollout total 0:28
Five service types. One git push.

What can you deploy from GitHub?

Connect a repository and Infrly figures out the rest — a running app, a published site, a scheduled job, a managed database, or a cache, each provisioned the way it actually needs to be.

WEB

Web Service

Node, Python, Go, Java, Ruby, PHP, or Rust apps, built and run for you, isolated, with the CPU and memory you choose.

No Dockerfile neededZero-downtime deploysAuto-restart
STATIC

Static Site

Built once and served straight to your visitors over HTTPS, with no server of your own to pay for.

No server to runAny SSG
CRON

Cron Jobs

Scheduled tasks that spin up on your own timezone-aware cron expression, billed only for the seconds they run.

No run, no charge: there's no monthly fee, and you pay only for the time each run actually takes.

Pay per runPer-job timezone
POSTGRES

PostgreSQL

Fully managed Postgres with automatic daily backups, point-in-time restore, and configurable retention.

Auto backupsPoint-in-time restore
KEY VALUE

Key Value

Managed, Redis-compatible Valkey for caching, sessions, and rate limiting. Every Redis client works unmodified, and it's private to your project by default.

Redis-compatiblePassword-protected
Web services build from source: Node.js, Python, Go, Java, Ruby, PHP, Rust.Supported languages & frameworks →
Build and deploy

Push code. Watch it travel.

One push triggers the whole pipeline — Infrly builds, packages, and deploys it, live in under a minute.

git

Push

webhook received

src

Build

runtime detected

pkg

Package

release prepared

run

Deploy

zero-downtime rollout

200

Live

HTTPS issued

Also deploys: Managed DatabasesCron JobsKey Value
How it works

How do you go from a GitHub repo to a running service?

1

Connect GitHub

Sign in and authorize the repositories Infrly should be able to see. Nothing more.

2

Pick a service type

Web service, static site, cron job, or database — configure defaults or accept them as-is.

3

Push to deploy

Every push to your connected branch builds and ships automatically — no separate deploy step.

4

Live, with a domain

HTTPS is issued automatically. Your service is reachable the moment the build finishes.

Included, not upsold

What comes with every service, so you don't build it yourself?

TLS

Automatic HTTPS

Every service and subdomain gets a valid certificate the moment it goes live — issued and renewed without a manual step.

Backups

Backups & point-in-time restore

Every managed database is backed up automatically on a retention schedule you set, restorable to any recoverable point.

Metrics

Live metrics, per service

CPU, memory, and disk usage in real time, viewable by the hour, week, or month — right on the service you're looking at.

Alerts

Alerting that reaches you

Resource pressure and downtime raise an alert before it becomes an incident, not after.

Isolation

Real isolation between projects

Every project is walled off from every other customer, with its own private network and enforced resource limits, so a noisy neighbor can't slow you down.

Portability

No cloud lock-in

Plain code from your git repo, standard PostgreSQL and Redis-compatible databases you can connect to and export from, and no SDK or config format that only works here.

Pricing

How much does it cost? Nothing during the beta.

Run up to 2 services at a time on Infrly at no cost while we're in beta, each on its smallest size, with no credit card. When the beta ends, each service is billed by its plan, prorated to the day, with no platform or seat fee. Beta users get 50% off for their first 12 months.

WEB$0free planPaid plans from $6 / month after the beta
STATIC$0limited freePaid plans from $5 / month after the beta
POSTGRES$9/ monthFrom, after the beta. Backups included
KEY VALUE$5/ monthFrom, after the beta
CRON$0monthly feeAfter the beta, pay per second each run takes

$0 during the beta. The prices above start after the beta ends, and we'll announce that at least 30 days ahead.

See pricing and estimate your bill
Why Infrly

Your app shouldn't belong to your cloud.

Whether you're coming from AWS, Google Cloud or Heroku, moving in takes one push. And because Infrly runs plain code on standard databases, moving out never takes a rewrite.

Infrly in short

  • One platform for the whole app. Web services, static sites, cron jobs, PostgreSQL and Key Value deploy from the same GitHub repo and dashboard.
  • No Dockerfile needed. Infrly detects Node.js, Python, Go, Java, Ruby, PHP or Rust and fills in the build and start commands.
  • Deploys without downtime. A new version only gets traffic after it passes its health check.
  • Databases you don't babysit. Daily backups and point-in-time restore come with every PostgreSQL database.
  • Free during the beta. Run up to 2 services with no credit card, and get 50% off for 12 months after the beta.
Compare

How does Infrly compare to Render, Railway and Heroku?

All four deploy your app when you push to GitHub. The differences are in which service types are built in, who looks after the database, and what's free. Here is the short version, taken from each provider's own documentation on October 7, 2026.

InfrlyRenderRailwayHeroku
Static sitesYesYesRun as a serviceRun as an app
Cron jobsYes, billed per second of each runYesYes, at least 5 minutes apartScheduler add-on: every 10 min, hourly or daily
PostgreSQLManaged, daily backups and point-in-time restoreManagedTemplate; you set up backupsManaged, from $5/month
Free starting pointFree during the beta, 2 services, no cardFree web services sleep after 15 idle minutes; free Postgres expires after 30 daysSee Railway's pricingNo free plan; Eco dynos $5/month

Comparing more options, like Fly.io, DigitalOcean, Vercel or Netlify? Read our full comparison of GitHub deployment platforms, with sources.

FAQ

Questions people ask before signing up

Infrly is in beta. What does that mean for me?

Infrly is in public beta: it's open to everyone, runs real projects today, and is free while the beta lasts. You don't need a credit card. During the beta, you can run up to 2 services at the same time, in any mix: for example a web service and a PostgreSQL database. Each one runs on its smallest size; the larger sizes open after the beta. Builds, deploys, HTTPS, custom domains and database backups work as this page describes. When the beta ends, the prices on our pricing page start, and beta users get 50% off for their first 12 months. We'll announce the end of the beta at least 30 days ahead, and nothing is charged until you add a payment method and choose a plan. We post what's new on X (@infrly).

How does deploying from GitHub work?

Sign in with GitHub; at sign-in Infrly only asks for your profile and email. The first time you pick a repository to deploy, GitHub asks you to give Infrly access to your repositories: Infrly reads the code to build it and adds a webhook. GitHub grants this access to all your repositories, but Infrly only uses the ones you deploy, and you can revoke it any time in your GitHub settings. 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.

Which languages and frameworks are supported?

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.

Will my app go down while a new version deploys?

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.

What does it cost, and how is billing calculated?

Infrly is free during the beta. After it, 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.

Do I need a credit card to start?

Not during the beta. After it, the free web service plan and static sites on limited free access still need no card. Paid plans, databases, Key Value instances, and cron jobs need a validated payment method, and nothing is charged until you add one and choose a plan.

Can I use my own domain?

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.

How does Infrly compare to Render, Railway and Heroku?

Infrly, Render and DigitalOcean App Platform give web services, static sites, cron jobs and managed databases their own service type. Railway runs databases from templates that it describes as unmanaged, so you set up backups yourself. Heroku runs cron jobs through its Scheduler add-on and has no free plan. Render's free web services spin down after 15 idle minutes, and its free Postgres expires after 30 days. Infrly is free during its beta for up to 2 services, with managed PostgreSQL backups and point-in-time restore. Our full comparison links each claim to its source.

How do database backups and restores work?

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.

How do I contact Infrly?

Email info@getinfrly.com or message @infrly on X. Sign-in and account questions go to the same address.

Deploy your first service in the time it takes to read this.

Connect a repository and see the whole pipeline — build, deploy, HTTPS — run end to end.