Introducing Hiraiship: deploy your apps to the edge in one command

Building an application is one thing. Getting it into production is another.

We spend hours on the code, then lose an evening on build configs, DNS records, environment variables and SSL. I think shipping should feel as good as building. So I've been working on Hiraiship, a deployment and hosting platform that takes your app from your machine to the edge.

Today I'm sharing it for the first time.

What it looks like

From your project directory:

npx hiraiship login
npx hiraiship deploy

login opens your browser to approve the device. There's no password, just a code sent by email. deploy packs your project, skipping node_modules, .git, .env* and anything in your .gitignore. Then it builds the project on Hiraiship's machines and streams the build logs to your terminal. When it finishes, your app is live on its own subdomain.

You can also connect a GitHub repository instead. Every push to a tracked branch deploys that branch's environment.

Frameworks

Hiraiship detects the framework and builds it with no config:

• Frontend: Vite, Astro, React Router, TanStack Start, Rasengan.js, and Next.js (static export, through vinext)
• Backend: Hono and Futon, bundled into a single edge Worker

Under the hood

Every app runs on Cloudflare's network, using Workers for Platforms. There's no single region to pick and no container to warm up: requests are served close to your users.

Each build runs in its own isolated container. Build outputs are content-addressed, so a redeploy only uploads the files that changed. A rollback points the routing back at a previous build, without rebuilding anything.

What you get

• Environments per project (production, staging, one per branch…)
• Custom domains with automatic SSL, plus redirects between domains
• Environment variables, with secrets encrypted per environment and build-time vs runtime targets
• Live build logs and one-click rollback
• Teams with roles, and API keys for CI
• A public REST API (docs.hiraiship.com)

Billing you can predict

Surprise invoices after a traffic spike are one of the most common complaints about hosting platforms. On Hiraiship:

• The Free plan never bills you. Every quota is a hard limit.
• Paid plans accept a spending cap, including a cap of zero, which turns every included amount into a hard limit.
• Projects are unlimited. You pay for the environments that are actually live, and idle ones can be paused.

What it doesn't do (yet)

I'd rather say it up front: server-side rendering isn't supported yet. A Next.js, Astro or React Router app that needs a server at request time is refused at build time. It isn't silently deployed half-working. Static sites, SPAs and Hono/Futon APIs are what work today. SSR is next.

Try it and tell me what breaks

🌐 hiraiship.com · 📚 docs.hiraiship.com

This is just the beginning, and early feedback shapes what I build next. So:

What matters most to you when choosing where to deploy your apps? Price, speed, framework support, something else? Tell me in the comments.