create-hayate

Hayate ecosystem: Start here · Production golden app · Tested compatibility · Frontend matrix

Composable, production-oriented project scaffolding for hayate.

The golden path creates one application core with safe request correlation, compact JSON access events, API routes, OpenAPI/Scalar, stateless MCP 2026-07-28, checked SQL, Cloudflare Access identity, SQLite on ASGI, and D1 on Cloudflare Workers:

uvx create-hayate my-app --template workers --preset production
cd my-app
uv run pytest
uv run python manage_workers.py d1 migrations apply DB --local
uv run python manage_workers.py dev

The generated README keeps the scaffold-to-start path under ten documented minutes and includes a fail-closed production checklist.

Runtimes

mcp remains a compatibility shortcut. It is not a copied template.

Features

Compose features explicitly instead of choosing from a template matrix:

uvx create-hayate my-app \
  --template workers \
  --with admin,openapi,mcp,sql \
  --auth cloudflare-access

MCP projects keep Emscripten and CPython dependency resolutions separate in their uv universal lock. This preserves Pyodide's reviewed rpds-py build on Workers while installing a native Python 3.14 wheel on macOS and other CPython platforms.

admin implies sql and Cloudflare Access and is currently limited to the Workers template with --frontend none; that template still runs unchanged through ASGI for local and fallback verification. The generator creates no anonymous mode or default superuser. Operators are an explicit case-insensitive email allowlist, records are scoped to the Access subject, mutations require an exact configured Origin, and audit rows never contain submitted values.

All 52 supported backend compositions are generated, dependency resolved, and imported in CI. Invalid combinations fail before the destination directory is written; for example, admin rejects an explicit --auth none and every unreviewed frontend composition.

Frontends

Frontend choice is independent from runtime, authentication, and optional backend features:

uvx create-hayate my-app \
  --template workers \
  --frontend htmx \
  --with openapi,sql

The frontend layer is composed last and is forbidden from overwriting backend files. htmx generates identity-scoped CRUD, validation fragments, history restoration, SSE, CSP/CSRF/cache defaults, browser smoke tests, and a checksum-verified self-hosted htmx 2.0.10 asset. ASGI serves that asset through Hayate; Workers uses Cloudflare Static Assets with the same same-origin URLs. Jinja2 remains the byte-for-byte compatibility default:

uvx create-hayate my-app \
  --template api \
  --frontend htmx \
  --renderer htpy

--renderer htpy generates native typed-Python components for ASGI or Workers. jx generates Jinja-backed typed components on ASGI, while experimental tdom uses Python 3.14 t-string components on ASGI. All renderer profiles preserve the same routes, identity-scoped CRUD, htmx fragments, security headers, and browser behavior. Explicit renderer projects record their runtime and Python contract in frontend/renderer.toml and add strict mypy checks at the renderer boundary. Until hayate-htmx is published, ASGI profiles pin reviewed 0.2.0 candidate commit c133900, while htpy Workers bundle the same small typed boundary because Pywrangler cannot install VCS records from its portable lock.

react generates a pinned Node 24/Vite/React Router application in frontend/. It enables Hayate OpenAPI automatically, keeps JSON below /api, generates Hayate's zero-runtime Fetch client and its types from the checked-in contract, and fails CI when the document, types, or client drifts. Vite proxies /api locally; the Workers template serves the production build through Cloudflare Static Assets with API-first routing and SPA deep-link fallback. npm ci, typecheck, build, dependency audit, Chromium CRUD, and real-workerd routing are exercised in CI.

astro generates a pinned Node 24 static site in the same frontend/ boundary. Public content is imported at build time; authenticated TODO data is requested only after the visible Preact island hydrates in the browser. React and Astro share one generated OpenAPI contract component, so neither profile maintains handwritten API models. Local development proxies /api to Hayate, while Workers serves the static build and API from one origin. The generated static-output audit rejects private data markers, and CI covers npm ci, typecheck, static build, Chromium persistence/deep links, dependency audit, and real-workerd routing. Astro SSR remains an explicit, adapter-backed BFF extension rather than part of the initial runtime.

Non-none profiles are rejected with the production preset until each profile has a reviewed production contract. The data-backed frontend compatibility matrix is also the CLI allow-list: pull requests exercise ten boundary compositions from a built wheel, including all explicit htmx renderers, while weekly and manual runs retain all 112 unique supported runtime/frontend/auth/feature/entrypoint compositions in deterministic shards. Each run publishes phase-level commands, exact tool versions, and the wheel digest as JSON evidence.

Production preset

--preset production is the reviewed composition of:

• openapi,mcp,sql;
• Cloudflare Access identity;
• exact-origin CORS;
• secure response headers and a 1 MiB request-body ceiling;
• a Cloudflare native rate-limit binding;
• D1 migration and deployment configuration;
• application and Cloudflare Worker version response correlation;
• explicit secret, identity, CORS, abuse, observability, migration, and rollout checks in PRODUCTION.md.

Admin remains opt-in on the production preset:

uvx create-hayate my-app \
  --template workers \
  --preset production \
  --with admin

The admin profile copies unmodified MIT-licensed snapshots of reviewed, exact commits into the generated source tree. This preserves offline, zero-network generation and avoids floating branches and Pywrangler's VCS-lock limitation; exact commits and licenses are recorded under admin/. The generated site uses escaped plain-text branding, contrast-checked theme tokens, hashed-CSP styling, keyboard/assistive-technology semantics, and the upstream application-scoped message-catalog contract.

Local CI drives the generated preset over both real ASGI HTTP and real workerd. The workerd path applies a real D1 migration, writes through the HTTP API, and reads the same authenticated data through MCP.

Design

• Zero-dependency CLI. Generation uses only the standard library and bundled, versioned components; it performs no network fetch.
• Small composition surface. One base app, one Workers runtime overlay, four feature components, and explicit auth/production components replace copied full-template combinations.
• Orthogonal frontend ownership. Runtime and backend features compose first; one frontend overlay may add only non-colliding files. htmx calls the same domain and storage functions as the JSON API; React consumes generated OpenAPI types without introducing a second backend; Astro keeps public build-time content separate from browser-only private state.
• Portable application core. src/app.py does not change between ASGI and Workers. Runtime resources enter through the Hayate request context.
• Safe observability by default. Request correlation wraps every generated identity, production, and optional feature boundary; access events contain narrow metadata and the exact final response status without query strings, headers, or bodies.
• Feature-complete Workers default. WorkerEntrypoint remains the default. HTTP-only services can explicitly request --workers-entrypoint global.
• Evidence over claims. CI runs unit tests, every dependency composition, wheel-based frontend compatibility, real ASGI, real workerd, D1 migrations, MCP, workflow audit, and dependency audit.

The internal design memo (Japanese, per project convention) is DESIGN.md; release history is in CHANGELOG.md.

Status: alpha (0.14.x). Generated projects pin released compatibility lines. Public APIs may still move before 1.0.

License

MIT