A repo goes in. A running app comes out.

homeport reads the files your repo already has. A go.mod means a Go binary. A composer.json means a PHP app on FrankenPHP. A Bun lockfile means bun install and bun run build. A folder of HTML is a static site.

You see the plan before anything builds: the toolchain, the build command and what gets deployed. When the guess is wrong, change it in the app settings, or commit a short homeport.yaml.

When an app has had no requests for a while, it goes to sleep. The next request wakes it in under a second, and that request is answered, not dropped.

Compute is billed per GB-hour while an app is awake, so a sleeping app costs nothing. On paid plans you choose, per app, whether it sleeps when idle or stays always on.

Apps run under gVisor, a sandbox that gives each app its own kernel boundary instead of sharing the host kernel directly. Your app sees an ordinary Linux machine; it cannot see its neighbours.

Static sites run nothing at all. They are files, served directly.

Every app gets an HTTPS address on homeport.run as soon as it deploys. On paid plans, add your own domain, point a DNS record at it, and a certificate is issued and renewed for you.

Static sites get a sensible cache policy out of the box: fingerprinted assets are cached for a year, HTML is always revalidated so a deploy shows up at once, and any headers you set win.

Deploys build on homeport’s own builders, billed per build minute. You can follow the log live and cancel a build that has gone wrong.

On Growth and above, deploy a compiled Linux binary from your own CI instead: build it however you like and the GitHub Action ships it. Static sites deploy by push-to-build or by uploading the folder.