SaastroSaastro
Open Source

Build fasterwith Saastro

A complete toolkit for web developers. UI components, themes, and CMS — all designed for Astro.

Get StartedView on GitHub

50+

Components & blocks

100%

TypeScript

0kb

Default JS

MIT

License

Everything you need

A complete ecosystem of tools designed specifically for Astro developers.

Component Library

UI

50+ accessible components and blocks for Astro. Vanilla JS, zero dependencies, copy-paste ready.

Vanilla JSTailwind CSSAccessibleDark mode
Form Builder

Forms

Visual form builder with validation, multi-step flows, and submission handling.

Drag & dropValidationMulti-stepWebhooks
Theme Catalog

Themes

Production-ready Astro themes. Landing pages, blogs, portfolios, and more.

Free & ProResponsiveSEO readyFast
Coming Soon
Headless CMS

CMS

Content management for Astro sites. Self-hosted or cloud, your choice.

MarkdownMedia libraryAPIPlugins

Replace five tools

One place for content, forms and deploys

The problem

Your site is a project.It should be a page you edit.

Every copy change becomes a ticket, a branch and a deploy. That is why nothing gets changed.

The person who writes the copy is not the person who can publish it.

So the site stays as it was launched, and the launch was a year ago.

How it works

Three steps and you are live

No setup call, no migration project. Connect, configure, publish.

  1. Connect your repo

    Point Saastro at a GitHub repository. It reads what is there — no rewrite, no lock-in.

  2. Configure the content

    Collections, locales and forms are declared once. The editor picks them up on the next load.

  3. Publish

    Every push builds and deploys. Rolling back is a redeploy of the previous version.

Built for

Teams that ship their own words

Not an agency retainer. Not a page builder that owns your markup.

The repository stays yours, the content lives in your locales, and the editor is a layer on top — not a place your site gets trapped in.

You own it

Your repo, your history, your deploys. Leaving is a git clone, not a migration project.

Made to last

Zero-JS blocks, typed props and a build-time contract that fails when a section stops being editable.

Why not a builder

The same five decisions, made the other way around

What you give up with a hosted builder, and what you keep here.

Hosted builder

Saastro

Your markup lives in their database.
Your markup lives in your repository.
The editor decides what is possible.
The blocks are code you can read.
Leaving means rebuilding.
Leaving means cloning.
One language, or a plugin.
Locales are first-class.
Their uptime is your uptime.
It deploys to your own account.

Get started

Put the first page up this afternoon

Scaffold from this theme, connect the repo, and publish.

Read the docsSee the blocks

MIT licensed. No account required to try it.