Static-first marketing pages, connected to ZShip checkout

Use this page as a fast SEO-friendly pricing surface. The lightweight island can call ZShip payment endpoints, while account and order management stay in the Nuxt/ZShip workspace.

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
Template Fit

When to choose Astro vs the full workspace

Capability
Launch
Growth
Platform
Static HTML first
SEO marketing pages
Docs / Blog / Case Studies
Pricing checkout island
Account dashboard
Nuxt handoff
Nuxt handoff
Nuxt handoff
AI Playground
Use web-nuxt
Best for
Launch site
SEO site
Content + workspace

Astro Template Questions

A few practical answers about where this template fits in the ZShip stack.

Use it for SEO-first SaaS websites, AI product launch pages, documentation hubs, blogs, pricing pages, case studies, changelogs, and lightweight public product fronts.
Astro shines when most of the page can be static HTML. A full workspace has richer state, authentication, orders, support, and AI workflows, so those flows remain better suited to Nuxt/ZShip.
Only small islands that need interaction: mobile navigation, pricing toggles, checkout buttons, form states, and similar UI controls.
Yes. Local Astro API routes proxy pricing and checkout requests to ZShip backend services using Cloudflare Service Bindings or local HTTP fallback.
Yes. Update zship.app.json for appKey, domain, canonical URL, brand, and workspace links, then customize the content collections.

Ready to ship a static-first SaaS site?

Use ZShip Astro Template for the public SEO layer, then hand off authenticated workflows to the ZShip workspace.

View Pricing