Astro frontend. Hono backend. One Cloudflare deployment.

Ship a fast fullstack app without splitting the stack in half.

This starter runs Astro SSR on Cloudflare Workers and forwards every /api/* request into Hono. The UI is server-rendered, the form posts to the API, and deployment stays inside one runtime boundary.

AstroHonoCloudflare Workers

<120ms

Edge-first responses

Astro SSR runs on Cloudflare Workers, with Hono powering API routes under the same deployment.

1 worker

Shared fullstack runtime

The UI and JSON endpoints ship together, which keeps local development and deploys predictable.

4 scripts

Tight deployment path

Install once, develop with Astro, preview with Wrangler, and deploy straight to Cloudflare.

Why this shape works

Astro owns rendering, Hono owns the API surface.

You get component-driven pages, zero client framework lock-in, and a backend that can grow from a few endpoints into a larger edge API without reworking the deployment target.

  1. Pages render through Astro in output: "server" mode.
  2. Astro’s catch-all API route forwards requests to Hono.
  3. Wrangler deploys the built worker and static assets to Cloudflare.

Exercise the backend

Send a project intake

Waiting for input.