Static-first SaaS website starter

ZShip Astro Template

A static-first Astro template for SEO, content growth, and lightweight conversion pages. HTML renders fast by default, while islands handle pricing, checkout, forms, and navigation.

View Pricing Platform Stack
ZShip Astro Template dashboard preview

Why this Astro template works

Fast static HTML

Most pages render as crawlable HTML, which is ideal for SEO, content distribution, and fast first paint.

Small JavaScript islands

Hydrate only the pieces that need state: pricing toggles, checkout buttons, forms, menus, and login checks.

Content-heavy by design

A good fit for docs, blogs, changelogs, case studies, comparison pages, and product launch pages.

Clean ZShip handoff

Keep full account, order, support, and AI workspace flows in Nuxt/ZShip while this site stays lightweight.

Astro for public pages, ZShip for workspace flows

Use this localized public layer for landing pages, pricing, docs, blogs, and case studies. Authenticated account, order, support, and AI workflows should continue in the Nuxt/ZShip workspace.

Best fit

SaaS marketing websites
AI product launch pages
Documentation sites
Blogs and changelogs
Pricing and comparison pages
Case studies and resource hubs

The full ZShip platform stack behind web-astro

Static Web Layer

Astro, MDX, sitemap, SEO metadata, and static HTML for landing pages, docs, blogs, pricing, and product content.

Nuxt Workspace

Nuxt owns richer authenticated dashboards, orders, support, profile, billing, and AI Playground flows.

React Islands

Small hydrated islands handle checkout, pricing toggles, login checks, forms, and navigation where browser state is needed.

Cloudflare Workers

Backend services run as Workers with service bindings, public-key protected HTTP fallback, and Worker-native deployment.

D1 / KV / R2

D1 persists platform data, KV handles cache-like state, and R2 stores uploads, generated media, and CDN assets.

Hono Services

ZShip backend Workers use lightweight HTTP services for auth, payments, support, email, CDN, provider, and AI workflows.

Payments

Stripe and Creem checkout endpoints are proxied through Astro API routes so public pages never carry provider secrets.

AI Gateway

AI workloads stay in ZShip services and Nuxt workspaces while the Astro site remains fast, crawlable, and conversion-focused.

Public Astro Layer for SEO and conversion

Static-first HTML

Most public pages ship as fast, indexable HTML instead of a heavy client-side app shell.

Content collections

Use Markdown and MDX for product pages, docs, blog posts, legal pages, changelogs, and resources.

SEO infrastructure

Metadata, canonical URLs, localized routes, sitemap, robots, and OG images are owned by the Astro template.

Backend-safe proxy

Pricing, checkout, and login requests go through Astro BFF routes instead of exposing backend secrets to the browser.

Static-first HTML
Content collections
SEO infrastructure
Backend-safe proxy

Backend Workers Layer for ZShip services

Auth and users

node1-auth provides login, user identity, sessions, credits, API keys, and project-aware account data.

Payments

Payment services handle plans, Stripe, Creem, checkout, webhooks, orders, subscriptions, and billing handoff.

Support and email

Support tickets, notifications, and email delivery live in backend Workers designed for Cloudflare deployment.

Service bindings

Workers communicate through Cloudflare Service Bindings in production, with local HTTP fallback for development.

Auth and users
Payments
Support and email
Service bindings

Workspace/Product Layer for authenticated workflows

Nuxt product UI

Nuxt handles richer authenticated interfaces such as dashboards, billing, orders, profile, and support.

AI workflows

AI Playground and provider workflows belong in ZShip services and Nuxt where app state is deeper.

CDN and storage

R2-backed CDN services can serve uploads, generated files, product assets, and media from the same platform.

TypeScript and pnpm

The workspace uses TypeScript, pnpm scripts, Wrangler, and shared conventions for repeatable local and Cloudflare builds.

Nuxt product UI
AI workflows
CDN and storage
TypeScript and pnpm

ZShip Astro Questions

Where this template fits inside the full ZShip platform.

No. web-astro is the static-first public layer for SEO, marketing, docs, blog, pricing, and lightweight conversion. Full dashboard workflows stay in Nuxt/ZShip.
Only small islands that need browser state: pricing toggles, checkout buttons, forms, language selection, mobile navigation, and login checks.
Astro API routes proxy requests to ZShip backend Workers using Cloudflare Service Bindings in production and HTTP fallback in local development.
It can connect to auth, payment, pricing, support, email, CDN, and AI-related services through server-side proxy routes, while keeping secrets off the client.
ZShip

Ship the public site with Astro, keep the app layer in ZShip

Use this template for fast acquisition pages and connect only the interactive edges to ZShip backend services.

View Pricing

A pricing block for lightweight conversion

Plans stay statically rendered while the checkout button hydrates as a small ZShip payment island.

I $49 / Per Month $490 / Per Month

Launch

For a single SEO-first product site, launch page, docs hub, or content-led SaaS front door.
Features Included
  • Astro static HTML pages
  • Blog, pricing, docs, and case-study content
  • ZShip pricing and checkout proxy
  • Full dashboard workspace
  • Multi-brand rollout kit
Recommended
I $99 / Per Month $990 / Per Month

Growth

For content-heavy SaaS sites that need fast pages, strong SEO, and a clean path into ZShip payments.
Features Included
  • Everything in Launch
  • Interactive pricing island
  • SEO metadata and sitemap
  • Cloudflare Worker deployment
  • Nuxt workspace handoff
I $199 / Per Month $1990 / Per Month

Platform

For teams using Astro as the public content layer and Nuxt/ZShip as the authenticated product workspace.
Features Included
  • Everything in Growth
  • Multiple marketing and content sections
  • Template-ready brand manifest
  • Service binding aware API routes
  • Full workspace ownership