Bun
Bun servers and static builds
homeport installs with your bun.lock and runs bun run build. Compile your server to a binary with bun build --compile, or build a static site, and it is served either way.
What homeport reads
- bun.lock
- Installs exactly what the lockfile says. The Bun version comes from packageManager or .bun-version.
- package.json build script
- Run as your build. A compiled binary named server runs as your app; otherwise a site folder (build, dist or out) is served as files.
- Vite, Astro, SvelteKit (static)
- Recognised as static builds, served from their output folder with long caching on fingerprinted assets.
What you get
- A compiled Bun binary: no node_modules on the server
- Static sites served as files, with nothing running behind them
- Apps sleep when idle and wake on the next request
- HTTPS on a homeport.run address, and your own domain on paid plans
Start from bun-api
A Bun HTTP API compiled to a single binary, ready to deploy.