Open-source website builder and CMS, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

What it is: Open-source (MIT) drag-and-drop website builder and CMS built on PHP Laravel — think Squarespace, but the code runs on your server and nobody can raise your subscription price [2].
Who it’s for: Non-technical founders, solopreneurs, and small businesses who want a visual, no-code website builder with built-in e-commerce, and who are tired of paying monthly SaaS fees for a site that doesn’t change much [2][5].
Cost savings: Squarespace’s Business plan runs $23/mo; Commerce tiers hit $28–52/mo. Microweber is MIT-licensed software — zero licensing cost. Self-hosting on a $5–6/mo VPS is the full bill [5].
Key strength: True real-time drag-and-drop editing with built-in e-commerce — no WooCommerce plugin required, no separate store add-on, no extra monthly fee [2][README].
Key weakness: Small community (3,399 GitHub stars) compared to WordPress or Joomla, limited third-party ecosystem, and performance is notably sensitive to hosting quality and site complexity [1][2].

What is Microweber

Microweber is a drag-and-drop website builder and CMS built on PHP and the Laravel framework. It lets you build websites, online stores, and blogs without writing code — you drag elements onto a page, edit text in place, and see the result immediately. The GitHub repository describes it plainly as a “Drag and Drop Website Builder and CMS with E-commerce” [README].

What sets it apart from traditional CMSes like WordPress or Joomla is the editing model. Most CMSes separate the backend editor from the frontend display — you write content in an admin panel, hit publish, and see how it renders. Microweber collapses that into a single live-edit view: you click on your live page, drag a block, type a heading, and the page changes in real time [README][2]. It’s closer to Webflow or Squarespace’s editing experience than it is to WordPress.

The project is genuinely open source under the MIT license — no “fair-code” restrictions, no usage caps, no commercial deployment fees. Version 2.0, running on Laravel 10, is the current release [README]. As of this review it sits at 3,399 GitHub stars. That’s a modest number compared to n8n (100K+) or WordPress itself, which tells you something about adoption relative to the ambition.

The software ships with a default template called “Dream” (75+ pre-built layouts) and a premium “BIG” template (350 layouts across 20 categories) for which you pay a one-time license [website][README]. The CMS itself costs nothing. You pay for hosting.

Why people choose it

The comparison articles available for Microweber [1][3][4][5] are mostly structured comparison pages rather than deep hands-on reviews, so the picture here is drawn from what those sources agree on and from the README and official site.

Versus WordPress. WordPress is the default answer for non-technical founders building a website, but it brings real complexity: plugins for everything, updates that break things, security vulnerabilities from a massive target surface, and a WooCommerce setup that requires separate plugins just to sell a product [1]. Microweber’s argument is simpler: one install, built-in e-commerce, no plugin juggling. The trade-off is brutal though — WordPress has tens of thousands of plugins, themes, and a developer community of millions. Microweber has a small fraction of that ecosystem. If you ever need functionality that isn’t built-in, you’re writing a custom module or going without [1].

Versus Joomla. Joomla is also open-source and powerful, but notoriously hard for non-technical users. Its access control system and content hierarchy are flexible to the point of confusion. Microweber’s advantage here is user experience — the editing interface is designed for people who don’t understand the word “taxonomy” [4]. The downside: Joomla has a large extension library and a more mature community. Microweber doesn’t.

Versus Craft CMS. Craft is a developer’s CMS — excellent content modeling, clean code, strong documentation. It’s built for agencies and web professionals building bespoke experiences [3]. Microweber is the opposite: optimized for non-technical users who want results today, not bespoke architectures. If you’re a developer, you’d likely reach for Craft or a headless CMS before Microweber. If you’re a founder who wants to build a store without hiring a developer, Microweber is easier to start with [3].

Versus Squarespace. This is the comparison that matters most for the audience this site covers. Squarespace is excellent — polished templates, managed hosting, no server maintenance — and it costs $16–52/mo depending on your tier, every month, indefinitely [5]. Microweber offers a comparable drag-and-drop editing experience with comparable built-in e-commerce, under an MIT license, with zero recurring software cost. The gap you’re giving up is Squarespace’s managed infrastructure, template quality, and the guarantee that it just works without you touching a server [5]. That’s a real gap, but it’s a one-time setup problem, not a monthly bill.

Features

Based on the README and official website:

Core website builder:

Real-time drag-and-drop page editing — elements repositioned live, text edited in place [README][2]
75+ pre-built page layouts in the “Dream” template [README]
350 layouts across 20 categories in the paid “BIG” template [website]
Modular architecture — content blocks, image galleries, video embeds, contact forms, custom modules [2]
Blog platform with categories, tags, comments control, SEO-friendly URLs [website]
Custom pages with different layout presets per page [README]

E-commerce (built-in, no plugins required):

Product listings with inventory management [website]
Checkout process with coupon codes [website]
Payment gateway integrations [website]
Custom fields per product [website]
Order management [website]

Admin panel:

Content management for pages, posts, and products [README]
Category organization for all content types [README]
Custom module support [README]

Technical underpinning:

PHP 8.2+ on Laravel 10 [README]
Supports MySQL, PostgreSQL, SQLite, MSSQL [merged profile]
REST API [merged profile]
Plugin/module system [merged profile]
Apache and Nginx support [README]
Available on DigitalOcean Marketplace, Azure Marketplace, Linode Marketplace, Vultr Marketplace, Plesk plugin [README]

What’s missing or unclear:

No SSO or multi-user RBAC details documented publicly
Plugin/module marketplace size is not documented (no count available)
No built-in AI tools or AI-assisted content features mentioned in current sources

Pricing: SaaS vs self-hosted math

Microweber does not charge for the software. The MIT license means zero recurring fee for the CMS itself [merged profile][README].

What costs money:

The “BIG” template license — one-time purchase, amount not publicly listed on the homepage without clicking through to purchase [website]. This is optional; the “Dream” template is free.
Your hosting infrastructure.

Self-hosted cost breakdown:

VPS: $4–8/mo on Hetzner, Contabo, or DigitalOcean (a 2–4 GB RAM instance handles a typical small business site)
Domain: ~$12/year
Optional: managed MySQL if you don’t want to administer it yourself (~$7–15/mo on managed providers)
Total realistic ongoing cost: $5–15/mo

Squarespace for comparison [5]:

Personal: ~$16/mo (no e-commerce)
Business: ~$23/mo (e-commerce with transaction fees)
Basic Commerce: ~$28/mo (no transaction fees, limited features)
Advanced Commerce: ~$52/mo

WordPress.com for comparison:

Business (first tier with plugins): ~$25/mo
Commerce: ~$45/mo

Concrete savings for a small business running a store:

A founder paying $28/mo for Squarespace Basic Commerce — the minimum tier to avoid transaction fees — pays $336/year. Self-hosting Microweber on a $6/mo Hetzner VPS costs $72/year plus the one-time BIG template license if you want more layout options. That’s roughly $260/year saved, every year, plus full ownership of the data and infrastructure.

The math is better for heavier users. A Squarespace Advanced Commerce subscription at $52/mo is $624/year. The same site self-hosted on Microweber costs $72/year in VPS fees. $550/year in savings ongoing, with no vendor able to raise the price on you.

Caveat: this ignores your time and technical ability. Squarespace is managed — hosting, backups, security patches, CDN. Microweber self-hosted means you handle all of that. If your time is worth money, factor it in.

Deployment reality check

Microweber is available on DigitalOcean Marketplace, Azure Marketplace, Linode Marketplace, and Vultr Marketplace — meaning one-click deployment is possible on four major cloud providers [README]. That’s a meaningful advantage over tools where you’re hand-wiring a docker-compose stack on a bare VPS.

For a technical user using a marketplace app: 15–30 minutes to a running instance. The marketplace handles the server provisioning, PHP setup, and initial configuration. You add a domain and set up HTTPS (usually via Certbot/Let’s Encrypt), and you’re live.

For a technical user doing a manual install: The README lays out the PHP extension requirements clearly (bcmath, curl, gd, intl, mbstring, zip, and more) and provides the apt install command [README]. Laravel’s Artisan handles the rest. Expect 1–2 hours on a clean VPS, including database setup and Nginx configuration.

For a non-technical founder doing it themselves: Budget 3–5 hours if you’re using a marketplace app and following a step-by-step guide. Budget an afternoon or a hired hand if you’re going from scratch.

What can go wrong:

Performance is explicitly flagged in multiple comparison sources as dependent on hosting quality and site complexity [1][2][3]. A cheap shared host or an undersized VPS will feel sluggish. This is a PHP/Laravel app — it needs real resources.
The plugin and theme ecosystem is small. If you need a specific integration (payment gateway, marketing tool, booking system) that isn’t built-in, you may find it doesn’t exist for Microweber. You’re either building a custom module or using an embed/iframe workaround.
GitHub activity is moderate — 3,399 stars [merged profile] and steady releases (2.0.16 is current), but this is not a project with a massive engineering team behind it. Long-term support trajectory is harder to predict than with WordPress.
No documented community size. No Trustpilot, no G2, no Reddit thread volume visible in the available sources. The feedback loop for knowing if you’re hitting a known bug is thinner than with major CMSes.

Pros and Cons

Pros

MIT license, zero software cost. No per-site fees, no commercial restrictions, no vendor lock-in on the license [merged profile][README]. Build a client site and hand it over. Resell the deployment. Fork it. All legal, no agreements needed.
True real-time editing. The live drag-and-drop editing experience is the genuine differentiator — it’s closer to Webflow or Squarespace than to WordPress’s admin-edit-preview loop [README][2]. Multiple sources cite this as the standout feature.
E-commerce built in. No WooCommerce, no plugin, no extra monthly fee for a store. Inventory, checkout, payments, and order management are native [2][website]. For a founder who just wants to sell things, this removes a layer of complexity.
Marketplace deployments. One-click deploy on DigitalOcean, Azure, Linode, Vultr — lowers the technical bar significantly compared to tools requiring manual compose setup [README].
Multiple database support. MySQL, PostgreSQL, SQLite, MSSQL [merged profile]. More flexibility than tools that lock you to one engine.
Modular/extensible. Clean Laravel codebase means developers who need custom functionality have a well-structured starting point [2][3].
No per-transaction fees on your store. Unlike Squarespace Business tier, there are no platform-imposed transaction fees on self-hosted Microweber.

Cons

Small community and ecosystem. 3,399 GitHub stars [merged profile] is modest. Plugin/module catalog is undocumented in size but clearly much smaller than WordPress or Joomla’s [1][4]. If you need a specific integration, check before committing.
Performance is hosting-dependent. Multiple sources flag this as a known limitation — the app needs a properly sized server [1][2][3]. Shared hosting and cheap VPSes will hurt you.
No independent deep reviews found. All third-party sources available are structured comparison pages from one aggregator site [1][2][3][4][5], not hands-on long-form reviews. This is itself a signal — the tool hasn’t attracted the review volume of WordPress or even Ghost.
Self-hosting is still required. There’s no free managed Microweber cloud tier [website]. You either self-host or… there isn’t another option. For a founder who wants to just pay $X and have someone else handle the server, Microweber isn’t the answer.
Less feature depth than specialized platforms. For pure blogging, Ghost is more polished. For pure e-commerce at scale, WooCommerce or Shopify has more. Microweber is a generalist tool that covers both adequately rather than excelling at either [1][3].
Template premium. The most capable template (BIG, 350 layouts) requires a paid license [website]. Pricing isn’t transparent without clicking through to purchase — a mild irritation when evaluating.
Less mature REST API. The API is listed as a feature [merged profile], but there’s no documentation surfaced in available sources comparable to WordPress’s REST API ecosystem.

Who should use this / who shouldn’t

Use Microweber if:

You’re paying $23–52/mo for Squarespace or a similar SaaS builder and your site doesn’t change fundamentally enough to justify that recurring cost.
You want a visual, drag-and-drop editing experience without touching code, but you also want to own the infrastructure.
You need built-in e-commerce without a plugin layer — product listings, inventory, checkout — for a small to medium catalog.
You’re comfortable deploying via a marketplace (DigitalOcean, Vultr, etc.) or have someone to handle the one-time setup.
You’re building a site for a client and want to hand over a system they can edit themselves without training.

Skip it (use WordPress + WooCommerce) if:

You need a large plugin ecosystem. WordPress’s 60,000+ plugins cover almost everything; Microweber’s module catalog is a fraction of that.
You need specific third-party integrations (CRM, email marketing, booking systems) that require established plugins with active maintenance.
Your long-term content strategy is complex — multi-author workflows, editorial pipelines, content taxonomies.

Skip it (stay on Squarespace) if:

You genuinely don’t want to think about servers. Squarespace’s managed hosting, CDN, SSL, and backups have real value if you want to focus entirely on the business.
Design quality is paramount and you need Squarespace’s professionally polished templates.
You have fewer than 5 pages and a simple product catalog where the monthly fee is worth the hassle elimination.

Skip it (use Ghost) if:

Your primary use case is publishing — blog, newsletter, membership content. Ghost is purpose-built for this and handles it with significantly more polish and feature depth than Microweber.

Skip it (use Shopify) if:

You’re running a serious e-commerce operation — dozens of integrations, advanced inventory, shipping rules, large product catalogs. Microweber’s built-in e-commerce is enough for a small store, not a scaling one.

Alternatives worth considering

WordPress — the obvious comparison. Vastly larger ecosystem, more plugins, more themes, steeper admin complexity. If you self-host WordPress + WooCommerce, the software cost is also zero (GPL license). Plugin quality is inconsistent; WooCommerce adds complexity. The right call for 90% of sites, but not always the easiest call [1].
Ghost — purpose-built for publishing and memberships. No drag-and-drop builder, but excellent for content-first sites with newsletters and subscriptions. MIT licensed, Node.js-based. Better than Microweber for blogging; weaker for e-commerce.
Joomla — also open-source, large extension library, solid access control. More powerful for complex sites but significantly harder for non-technical users [4].
Craft CMS — developer-oriented, excellent content modeling, Freemium licensing (free for solo use, paid for teams). Not for non-technical founders; very much for agencies building bespoke sites [3].
Grav — flat-file CMS, no database required, very lightweight. Good for static-ish sites but no visual builder and no e-commerce out of the box.
Squarespace — the paid SaaS alternative. Better templates, fully managed, no server work. Ongoing cost vs. self-hosting trade-off [5].
Webflow — visual builder closer to Microweber’s experience, with significantly better design output. SaaS pricing ($14–39/mo for CMS; commerce plans higher). No self-hosting option, but the editing experience and template quality are in a different league.

For a non-technical founder choosing between self-hosted options, the realistic shortlist is Microweber vs WordPress + WooCommerce. Pick Microweber if you want simplicity and live editing. Pick WordPress if you want ecosystem depth and long-term flexibility.

Bottom line

Microweber does what it claims: it gives non-technical users a visual, drag-and-drop website builder with built-in e-commerce, under an MIT license, for the cost of a VPS. The real-time editing experience is the genuine differentiator — it’s closer to Squarespace than to the admin-panel flow of most PHP CMSes. The math for replacing a $28–52/mo Squarespace subscription is straightforward: one afternoon of setup, one $6/mo server, done.

The honest caveats: the community is small, the plugin ecosystem is limited, and the available third-party reviews are thin — which means you’re taking on more discovery risk than you would with WordPress. This isn’t the tool for a scaling e-commerce store or a complex editorial site. It’s the tool for a founder who has a 5–15 page business site or a small store, is paying Squarespace every month for the privilege, and would rather pay once for setup and own the infrastructure permanently.

If the setup is the blocker, that’s exactly what upready.dev deploys for clients. One-time fee, you own it, nobody raises the price on you.

Sources

AppMus — WordPress vs Microweber Comparison (2026) | Feature by Feature. https://appmus.com/vs/wordpress-vs-microweber
AppMus — Microweber: Features, Alternatives & Analysis (2026). https://appmus.com/software/microweber
AppMus — Craft CMS vs Microweber Comparison (2026) | Feature by Feature. https://appmus.com/vs/craft-cms-vs-microweber
AppMus — Joomla vs Microweber Comparison (2026) | Feature by Feature. https://appmus.com/vs/joomla-vs-microweber
AppMus — Squarespace vs Microweber Comparison (2026) | Feature by Feature. https://appmus.com/vs/squarespace-vs-microweber