Astro Visual Editors Compared: AeroLaunch Builder, CloudCannon, TinaCMS, Morrisson

Search for “Astro visual editor” and you get four products that barely resemble each other. One is a hosted platform with team roles and a monthly bill. One is an open-source CMS you wire into your repo. One is a 15 MB desktop app. One starts from a finished theme and hands you a zip. They all let a non-developer change an Astro site without opening a code editor, and that is roughly where the similarity ends.

This is a practical comparison of the four: CloudCannon, TinaCMS, Morrisson from Lexington Themes, and the AeroLaunch visual builder. Prices and plan details were checked in September 2026 and will drift, so treat them as a snapshot. If you want the wider map of every no-code approach to Astro first, including Git-based and headless CMSs, read the no-code Astro builders guide. This piece goes one level deeper on the four that offer a visual, on-page or point-and-click experience.

The four at a glance

	AeroLaunch visual builder	CloudCannon	TinaCMS	Morrisson
What it is	Browser builder for AeroLaunch themes	Hosted CMS and site platform	Git-backed CMS with visual editing	Desktop content editor
How you edit	Click any section of the real rendered theme	In-context editing on your rendered pages, plus forms	On-page editing via a sidebar and forms in your React or Astro app	Frontmatter forms and a Markdown editor
What you can edit	Every section of every page: headlines, copy, images, lists, pricing, blog posts, site settings, out of the box	Whatever a developer configures as editable: page data, components, Markdown, images	Content in the schema a developer defines: Markdown, JSON and frontmatter, with on-page editing where a page is wired for it	Markdown and frontmatter files only, so blog posts and content collections, not the hardcoded sections of a landing page
Works with	AeroLaunch themes you own (10 in the editor today, more added over time)	Any Astro project you connect	Any Astro project you configure	Any Astro project on your machine
Where content lives	In your exported project	Your Git repo, synced through their platform	Your Git repo	Your Git repo, on disk
Pricing model	$39 one-time unlock (regular $49), included in the $199 All-Access bundle	From $55 per month, or $49 per month billed yearly, for 3 users	Free for 2 users; from $24 per project per month for teams	$29 one-time, lifetime updates
Hosting	None required, you host the export anywhere	Included on their platform	Bring your own	Bring your own
Team features	Single editor; two separate site projects per theme, unlimited edits and downloads	Users, permissions, scheduling on higher tiers	Roles and a review workflow on paid plans	Per-file history, Git publishing with preflight checks
Leaves you with	A complete Astro project zip, runnable with npm	Your repo, but editing stops when the subscription does	Your repo, editing keeps working on the free tier	Your repo, the app keeps working
Best for	Launching a new site from a premium theme, no code	Teams editing a live Astro site with a publishing workflow	Developers adding editing to their own Astro project	Solo devs and small teams editing Markdown content

The rest of the article walks through each one with the honest trade-offs, then a short decision list at the end.

The biggest difference: what is actually editable

Pricing gets the attention, but the line that decides whether a tool is useful to you is the “What you can edit” row. In a typical Astro theme, blog posts live in Markdown files, and everything else, the hero, the feature grid, the pricing table, the testimonials, the footer, is written into the page components. A tool that edits Markdown and frontmatter reaches the blog and stops there.

That is where Morrisson sits: it is a good editor for content collections, and it does not touch the sections that make up a landing page. TinaCMS reaches whatever a developer has moved into its schema, and CloudCannon reaches whatever a developer has configured as editable, so both can cover a whole site, but someone has to do that wiring first, page by page. The AeroLaunch builder is the only one of the four where every section of every page is editable on day one with no setup: change the headline, replace any image, rewrite the pricing, reorder or remove sections, write the blog, and change site-wide settings, all on the real rendered site. It is less a content editor than a way to customise the whole theme without opening the code.

AeroLaunch visual builder

The AeroLaunch builder takes a different starting point from the other three. Instead of attaching an editor to a codebase you already have, you begin with a finished, professionally designed Astro theme and edit it directly in the browser. The canvas is the real built site, not a preview approximation, and every page is fair game, not just the blog: click a headline and type, replace any image on any page, add, remove or reorder sections, edit the pricing table, write a blog post, change site-wide settings like colours and contact details, and wire integrations such as forms and analytics from one panel. When you are done you download a complete Astro project with your content serialised in, run npm install && npm run dev, and it works. Nothing stays running on AeroLaunch after that.

It is a one-time $39 unlock (regular $49), and it is included in the $199 All-Access bundle, so bundle owners do not buy it separately. You need to own at least one AeroLaunch theme, and the free themes count. Ten themes are editable in the builder today, with the rest of the collection being added one at a time and unlocking automatically for everyone who owns them. It is in beta: fully usable, with new themes and editing features shipping regularly.

The honest limits: it only edits AeroLaunch themes, so it is not a tool for an Astro site you already built. It is a single-editor workflow, with two separate site projects per theme (your own site and a client’s, say), each editable and downloadable as often as you like, not a team CMS with roles and approvals. And after you export, further edits happen in the code or by re-exporting from the builder, not through a live admin on the deployed site.

Choose it when you want a polished site live this week from a theme, edited without code, and you want to walk away owning a normal Astro project. Skip it when you need to retrofit editing onto an existing codebase or you have a team that publishes daily.

CloudCannon

CloudCannon is the most complete hosted option of the four. You connect your Astro repository, describe your components and content structures in its configuration, and editors get in-context editing on the rendered pages plus structured forms, a component browser, and asset management. Edits sync back to Git, so your repository stays the source of truth, and CloudCannon hosts and builds the site for you. Higher tiers add branching workflows, content scheduling and custom permissions.

Pricing starts at $55 per month, or $49 per month billed annually, for 3 users and unlimited sites, with a 21-day trial and no free tier. The Team plan is $350 per month for 15 users with scheduling and branching workflows, and there is a custom Enterprise tier.

The honest limits: it is a subscription, and the editing experience lives on their platform. Your repo remains yours, but the moment you stop paying, the visual editor, previews and hosting go with it. The configuration work to make components editable is real, and it is developer work. For a single marketing site it is a lot of platform.

Choose it when a team needs to edit a live Astro site with reviews, scheduling and a proper publishing workflow, and the monthly cost is easy to justify. Skip it when there is one editor, one site, and no appetite for a recurring bill.

TinaCMS

TinaCMS is a Git-backed CMS with an open-source core and a hosted cloud for authentication and the Git backend. You define your content schema in code, and editors get an admin sidebar with on-page visual editing for content that is wired to it, plus forms for everything else. Content is written back to Markdown and JSON in your repository on save, so it works naturally with Astro’s content collections.

The free plan covers 2 users on the hosted cloud, and it is free for as long as you want it. Team is $24 per project per month (or $290 a year) for 3 users with a review workflow, Team Plus is $41 per project per month for 5 users, and Business is $249 per project per month for 20 users with API access. Extra seats are priced per user on each tier.

The honest limits: it is a developer’s tool first. Someone has to install it, define the schema, and decide which fields are visually editable. The visual mode is best when your pages are built to work with it, and it is a lighter, less “click anything” experience than CloudCannon or a theme-based builder. Hosting is yours to arrange.

Choose it when you are a developer with an existing Astro project who wants free, no-lock-in editing for a client or a small team. Skip it when nobody on the team wants to write a content schema.

Morrisson

Morrisson is a small desktop app from Lexington Themes for macOS, Windows and Linux. It opens an Astro project on your machine and gives you a frontmatter form editor with a YAML toggle, a Markdown editor with a formatting toolbar, image upload and optimisation, per-file history with conflict detection, and Git-based publishing with preflight checks. It is a one-time $29 purchase with lifetime updates.

The honest limits: it is a content editor, not a visual page editor. You edit the Markdown and frontmatter files that drive your site, not the rendered page, so it reaches blog posts and content collections and stops at the landing page. The hero, the pricing table, the images in a feature grid, anything written into a page component, stays a developer job. It needs the project on your machine, and it assumes a Git workflow. Everything stays file-based, which is the point, and also the ceiling.

Choose it when you or a small team already run an Astro site on Markdown and want a friendlier way to write and publish. Skip it when the editor needs to see the page while they edit, or has never used Git.

How to choose

• You are starting a new site and want it live fast, without code. Pick a theme and use the AeroLaunch visual builder. You spend your time on content, not layout, and you export a normal Astro project.
• You already have an Astro site and one developer maintaining it. TinaCMS on the free plan gives editors an admin without a bill.
• You already have an Astro site and a team that publishes often. CloudCannon, if the monthly cost fits.
• Your site is Markdown-driven and the editors are comfortable with Git. Morrisson is a cheap, focused upgrade over a text editor.
• You want to own the result outright. All four keep content in files, which is rarer than it should be. The builder and Morrisson also stop costing money after the one-time purchase; TinaCMS stays free at two users; CloudCannon is the only one where the editing experience itself is rented.

The ownership question, again

Every comparison of Astro editors ends up at the same place: when you are done editing, what do you have left? With TinaCMS and Morrisson, a repository with Markdown in it. With CloudCannon, the same repository plus a platform you are paying to keep the editor alive. With the AeroLaunch builder, a downloaded Astro project that runs on your laptop and deploys anywhere, with no service in the loop.

None of those is wrong. They are different bets on who edits the site and for how long. If the honest answer is “one person, at launch, and occasionally afterwards”, a theme plus a one-time builder is the shortest path from idea to a live site you fully own. If the answer is “a team, every week, with approvals”, pay for the platform that was built for that. See how the builder works, or start from the wider no-code Astro guide if you are still deciding which kind of tool you need.