Create a Silva UI app
create-silva-ui starts a new project with Silva UI, TypeScript, and the runtime configuration for the kind of app you choose. Use it to start a new app instead of wiring Silva UI into an existing Hono JSX project.
Choose a starter
The static SPA does not include a production Hono server. The two SSR starters share the same Hono JSX application structure; full-stack adds the API example, while SSR-only leaves it out.
Choose an SSR runtime
When you select Full-stack SSR or SSR-only, choose the runtime that matches where you intend to run the app.
Every listed adapter is fully supported for both the Full-stack SSR and SSR-only starters. Choose the runtime that matches your deployment target.
A generated project contains configuration and local scripts only. It does not create a cloud project, store credentials, or deploy anything during generation. Complete the provider-specific setup before deploying.
Install and validate
Enter the generated directory, then use the package tool for its runtime. The generatedpackage.json is the source of truth for the available scripts.
Some provider starters are build-only by design. Review their generated configuration and provider documentation before using a build or deployment command.
Automate generator choices
For CI or scripted setup, provide the same choices through environment variables.static, full-stack, and ssr-only are valid template values. SSR templates also accept an adapter ID.
cloudflare, node, bun, fastly, and deno.
Start from an existing app
The generator is optional. To add Silva UI to an existing Hono JSX project, follow Installation instead.A starter is a foundation, not a deployment policy. Keep provider credentials outside the project, review runtime-specific configuration, and use the support tier as a guide when selecting a production target.