Edit your static site visually.
Siguro CMS puts a visual editor on top of the Astro site your developers built. Marketing clicks a section, changes it, and ships in minutes. Developers get every edit as a git commit in the repo they already work in. Nothing moves into a vendor database.
We work with 20+ amazing partners
Page builders rent you a website. We think you should own yours.
Webflow and Framer are quick to start and expensive to leave. Your site lives in their database, renders through their runtime, and exports as HTML you can't maintain. A headless CMS gives developers their stack back, but marketers lose visual editing and go back to filing tickets.
Siguro CMS does both jobs. Marketers edit the live site visually. Developers keep a plain git repo, their own components, and their own hosting. If we disappeared tomorrow, your site wouldn't notice.
From an edit to live in four steps
This is the whole publishing workflow. No tickets, no handoffs, no waiting for the next sprint.
Click the section you want to change
Open your site in the CMS and turn on edit mode. Click any section and edit its text, images and settings with a live preview of the real page.
Save. It becomes a git commit
The CMS writes the change into your repo as a commit with a clear message. Your content history shows who changed what and when.
Check it on a preview link
Pending changes build to their own private URL. Review on your phone or send the link to a teammate for sign-off.
Publish. It merges and goes live
Publishing merges to your main branch. Your host rebuilds the site and the change is live in about a minute. Rollback is one click.
What it does
The features your marketing team gets, and what your developers keep.
Edit the real page
The editor is your live site with editing turned on. What you see while editing is exactly what ships.
Your own components
Pages are assembled from the components your developers already built, so every new page stays on brand.
Full history and rollback
Every edit is a git commit. See who changed what and when, and revert any change in one click.
Preview links
Unpublished changes build to a private URL. Share it and get sign-off before anything goes live.
A/B testing built in
Duplicate a page as variant B and split traffic at the edge. No third-party testing script slowing your pages down.
SEO fields on every page
Set titles, descriptions, canonicals and structured data per page. All of it renders into static HTML that search engines read.
Content lives in your repo
Everything is YAML and Markdown files next to your code. Search it, script it, feed it to AI tools, move it anywhere.
Fast pages
The site builds to static HTML with almost no JavaScript, so Lighthouse scores stay green without extra work.
Runs on your accounts
Your GitHub, your Netlify or Vercel, your domain. We are never between your visitors and your site.
How it compares
Siguro CMS next to the two usual options.
| Siguro CMS | Page builders (Webflow, Framer) | Headless CMS (Contentful, Sanity) | |
|---|---|---|---|
| Where your content lives | Your git repo | Their database | Their database |
| Tech stack | Your own. Astro and your components | Theirs, proprietary | Yours, glued together over APIs |
| Visual editing | On the real page | In their canvas | Rarely. Forms and fields |
| Leaving | Clone the repo. Done. | Lossy HTML export, rebuild from scratch | Migrate schemas and content |
| Version history | Full git history, one-click rollback | Limited snapshots | Per-entry versions |
| Performance | Static HTML, green Lighthouse | Builder runtime overhead | Depends on your build |
| Ongoing cost | Your hosting bill | Per-seat, per-site plans | Usage-based tiers |
Common questions
Siguro CMS runs on sites we build or migrate to Astro. If you're on Webflow, WordPress or a custom stack, we migrate the site into your own repo first, and your team starts editing the day it lands.
If you can edit a doc, you can edit the site. Marketers work visually on the page. Developers keep working in git like nothing changed, because to them the CMS is just another committer.
Your code and content live in your GitHub repo. The site deploys to your own Netlify, Vercel or Cloudflare account. We never sit between your visitors and your site.
Yes. Content is plain YAML and Markdown, so edits from code and edits from the CMS coexist in the same git history. Content changes can even be reviewed like pull requests.
Nothing breaks. The repo, the content and the hosting are already yours, so there is no export and no migration. That's the point.
Want your site to work like this?
- Works with a new or migrated site
- Set up by us, owned by you
- Nothing to migrate off later
