Introduction
Hiraiship deploys your app to the edge, on its own subdomain, in a few seconds. You send the source; Hiraiship detects the framework, builds it in an isolated machine, and serves it from Cloudflare's network.
It does that and nothing more, on purpose. There's no database, no authentication for your users and no storage to adopt: your app keeps its own.
What you can deploy
| Framework | Kind | Runs as |
|---|---|---|
| Vite | Frontend | Static files |
| Rasengan.js | Frontend | Static files, or server-rendered |
| Hono | Backend | A Worker |
| Futon | Backend | A Worker |
A folder without package.json | Static site | The files as they are |
The framework is detected from your project, so there's nothing to configure for the common case. The install command, build command and output directory can be changed per project or per deployment.
How it fits together
- A workspace holds your projects, your members and your plan.
- A project is one app. It starts with a
productionenvironment, reachable at<project>.hiraiship.app. - Each
hiraiship deploycreates a deployment: one build of your code. The latest successful one is live; older ones stay available for a rollback. - Domains point at an environment. Add your own on top of the default one.
Core concepts goes through each of them.