Frappe Builder

Open-source website creation, honestly reviewed. Built on one of the most underrated frameworks in open source, and not widely known for a reason.

TL;DR

• What it is: Open-source (AGPL-3.0) visual website and page builder — think Webflow, but self-hosted and deeply integrated with the Frappe Framework [README].
• Who it’s for: Developers and designers already inside the Frappe/ERPNext ecosystem who want to build and publish web pages without switching tools. Less useful if you’re not already on Frappe [1][README].
• Cost savings: Webflow’s CMS plan runs $23–$39/mo; Framer starts at $10–$25/mo per site. Frappe Builder is free software, but the hosting stack it requires is not trivial — plan for a 4–8GB RAM VPS at $10–20/mo minimum [3].
• Key strength: Genuinely fast output pages. The benchmark numbers on their own homepage show a Lighthouse performance score of 98 on mobile, because the builder outputs clean HTML/CSS with no client-side JavaScript injected by default [website].
• Key weakness: It’s a component of the Frappe ecosystem, not a standalone tool. Self-hosting Frappe apps has documented discrepancies versus Frappe Cloud that even dedicated users run into — bugs, missing features, and environment-sensitive behavior that requires engineering effort to resolve [2].

---

What is Frappe Builder

Frappe Builder is a visual drag-and-drop website builder that runs on top of the Frappe Framework. You design pages in a Figma-like canvas, connect them to your Frappe database via Data Scripts, and publish them with one click. Frappe.io — the company’s own marketing site — is built and hosted using it, which is the clearest signal that it’s production-ready for at least one real workload [README].

The motivation behind it, per the README, was straightforward: existing website builders either couldn’t integrate with the Frappe ecosystem cleanly, or they injected so many scripts and styles that the resulting pages were slow. Builder was built specifically to output lightweight HTML/CSS and let performance be a first-class concern from day one [README].

What makes it distinct from the hundreds of generic drag-and-drop page builders is the Frappe CMS integration. If you’re running ERPNext or any Frappe app, your data is already in Frappe’s database. Builder lets you fetch that data, loop over it, and display it in a designed layout — product catalogs, blogs, portfolios, custom dashboards — without bolting on a separate CMS. That’s a real advantage if you’re already in the ecosystem. If you’re not, it’s an irrelevant feature attached to a significant setup cost [README][website].

The project sits at 1,940 GitHub stars — modest for its category, which tells you something about its reach. The Frappe Framework itself is one of the most used frameworks you’ve probably never heard of: companies like Zerodha, Blinkit, and ElasticRun run internal operations on it, and yet in a room full of senior developers, most people haven’t heard the name [1]. Frappe Builder inherits both the quality and the obscurity.

---

Why people choose it

The honest answer: most people who use Frappe Builder aren’t choosing it over Webflow or Framer. They’re choosing it because they’re already running ERPNext or another Frappe app and need to build a public-facing page that can pull live data from that app without an API layer in between [1][README].

The Medium piece by Navneet Maheshwari [1] — which covers the Frappe Framework broadly rather than Builder specifically — captures this well: Frappe’s strength is that a small team can build and maintain a complex application without a large dev team. The framework handles data models, UI, and logic in a single configuration-driven system. Builder extends that into the frontend design layer.

The performance angle is real. The website publishes benchmark data comparing Builder-generated pages against unnamed competitors on Google Lighthouse (mobile). Their numbers: FCP 0.8s vs 1.7s and 1.9s from competitors; Lighthouse score 98 vs 91 and 79. The methodology caveat is “nearly identical test pages” — take it directionally rather than literally — but the underlying reason is technically sound: no client-side JavaScript loaded by default, no framework hydration overhead, just HTML/CSS [website].

The Figma integration is legitimately useful. There’s a Figma-to-Builder plugin that lets designers import their designs directly and own implementation themselves, cutting out the developer handoff step. For small teams where the designer and the person who deploys the site are sometimes the same person, that’s a real workflow improvement [website].

The self-hosting gap is real too. A forum thread from October 2024 [2] documents exactly what happens when you try to run Frappe apps outside of Frappe Cloud: printing errors, the Print Designer app behaving differently than on managed hosting, Stripe payment integrations failing on custom Docker images. The response from a Frappe team member was essentially: self-hosting means you become the dedicated engineer who makes it work. That’s not unfair, but it’s an honest picture of what you’re signing up for [2].

---

Features

Visual editor:

• Figma-like canvas with a focused, uncluttered workspace [website]
• Layers view for organizing element hierarchy [website]
• Properties panel for typography, spacing, layout [website]
• Component picker with reusable block library [website]
• Template blocks for common patterns: headings, paragraphs, forms, lists, buttons, quotes, images, video [website]

Responsiveness and theming:

• Desktop, tablet, and mobile views side-by-side [website]
• Smart theming via CSS custom properties — light and dark mode variables that propagate automatically through surfaces and typography [website]
• Interactive states (hover, focus, active) set visually without writing CSS [website]

CMS and data:

• Data Scripts: fetch and loop over Frappe database records to build dynamic pages [README][website]
• Suitable for blogs, product listings, portfolios, custom layouts [README]
• No separate CMS layer required if you’re already on Frappe [README]

Publishing and performance:

• One-click publish [README]
• Output is clean HTML/CSS — no injected framework scripts [website]
• WebP image optimization built-in [website]
• Google Lighthouse score of 98 (mobile) on their benchmark [website]

Access and analytics:

• Protected pages with built-in login gate [website]
• Built-in page view and referrer analytics — no external scripts needed [website]
• Copy pages across sites [website]

Scripting:

• Client scripts, global scripts, and custom styles for developers who need to go beyond the visual editor [README]

Deployment:

• Docker Compose for local development [README]
• Easy-install Python script for production (two commands, ~5 minutes) [README]
• Frappe Cloud managed hosting via frappecloud.com [README]
• Dokploy templates for self-hosted deployment with a UI [3]

---

Pricing: SaaS vs self-hosted math

Frappe Cloud (managed): Frappe’s official hosting for Builder exists at frappecloud.com/builder/signup. Specific pricing tiers are not published in the data available for this review — you’d need to check the pricing page directly. Frappe Cloud generally follows a per-site model for their other products, so expect something in the $10–30/mo range for a basic site, but this is not confirmed data.

Self-hosted:

• Builder software: $0 (AGPL-3.0)
• Infrastructure: this is where it gets honest. Frappe apps are not lightweight. The official Dokploy self-hosting guide recommends a VM with 4 shared vCPUs and 8GB RAM [3]. On Hetzner, that’s roughly €14–20/mo. You can run it on 4GB RAM but with less headroom. This is significantly more resource-hungry than a typical $5–6 VPS workload.
• Domain and HTTPS: standard overhead, add $10–15/year.

Competing SaaS for comparison:

• Webflow: $14/mo (Basic), $23/mo (CMS plan with database items and API access), $39/mo (Business)
• Framer: $10/mo (Basic, 1 site), $25/mo (Pro)
• WordPress.com Business: $25/mo
• Ghost Pro: $9/mo (Starter) to $25/mo (Creator)

The math: If you’re already running a Frappe/ERPNext instance on a decently sized VPS, adding Builder costs nothing — it’s another app on existing infrastructure. That’s the scenario where self-hosting makes obvious financial sense. If you’re setting up a VPS specifically to run Builder for one website, the economics are less clear — a $15–20/mo VPS to replace a $23/mo Webflow plan is not a compelling savings story, especially before accounting for setup time.

---

Deployment reality check

The official path is a Python easy-install script that claims to produce a production-ready instance in about five minutes [README]. The Dokploy guide [3] shows a more realistic modern approach: spin up a Linux VM, install Dokploy (a Docker-based deployment platform), and use their pre-built Frappe templates.

What you actually need:

• Ubuntu 24.04 VPS with at least 4GB RAM (8GB recommended for comfortable headroom) [3]
• Docker and docker-compose
• A domain name with DNS A record pointing to your server
• HTTPS setup (Dokploy handles this via Let’s Encrypt if you use it; otherwise Caddy or nginx)
• An email address for the install script

What can go wrong:

The Frappe forum thread [2] is the most useful reality check here. Self-hosted Frappe deployments can diverge from Frappe Cloud in subtle ways: print formats fail, payment integrations behave differently, apps that “work on Cloud” don’t work identically on custom Docker images. One community member responded to the complaint by saying Frappe Cloud has “dedicated engineers to ensure components work” and that self-hosters need to fill that role themselves [2]. That’s accurate, but it means Frappe Builder’s self-hosted experience can require engineering troubleshooting that competing tools like Webflow or Ghost don’t.

The AGPL-3.0 license is also worth understanding: if you modify Builder and use it to offer a service, you must publish your modifications under AGPL. This is fine for internal use or publishing your own website, but matters if you’re building a multi-tenant SaaS on top of it.

Realistic time estimate: 30–60 minutes using the easy-install script on a fresh VPS if you’re technically comfortable with Linux. Half a day or more if you’re debugging environment-specific behavior or setting up Dokploy from scratch.

---

Pros and Cons

Pros

• Performance-first output. Pages built with Builder consistently score high on Lighthouse because there’s no client-side JavaScript loaded by default. This is architecturally baked in, not a configuration option [website][README].
• Frappe CMS integration is a genuine differentiator. If you’re on ERPNext or any Frappe app, you can fetch and display live database records in a designed layout without an API or a separate CMS. No other visual website builder offers this [README].
• Figma-to-Builder plugin. Designers can own implementation without a developer handoff step. Rare in this category [website].
• Built-in analytics and WebP optimization. Small things that usually require separate tools or plugins [website].
• Production-proven. Frappe.io itself — a real company’s public-facing marketing site — runs on Builder [README].
• Clean, focused editor UI. The website calls out “intentionally clean workspace, as opposed to cluttered traditional no-code tools” — user quotes on the site echo this [website].

Cons

• Ecosystem lock-in. Builder requires the Frappe Framework. If you’re not already running Frappe, you’re installing a full-stack application framework to get a website builder. That’s a significant overhead for a simple use case [README][1].
• Self-hosted experience diverges from Frappe Cloud. Documented bugs and missing functionality in self-hosted deployments — print errors, app behavior inconsistencies — that require engineering effort to resolve [2].
• AGPL-3.0, not MIT. The license restricts commercial redistribution of modifications. Competitors like Activepieces and Ghost offer MIT or more permissive licensing for their core [README].
• Low GitHub star count (1,940) for its category. Webflow, Framer, and even less-known alternatives have larger communities and more third-party content. Troubleshooting as a self-hoster will be harder [merged profile].
• Heavy infrastructure requirements. 4–8GB RAM minimum is a real cost floor for self-hosting, unlike lighter web publishing tools [3].
• Poor marketing and discoverability. A senior Frappe developer noted in 2024 that even rooms full of tech professionals hadn’t heard of Frappe [1]. Small community means fewer guides, plugins, and examples.
• Frappe Studio is a parallel product creating confusion. Frappe is also developing Frappe Studio, a separate low-code visual app builder for the Frappe Framework [4]. The distinction between Builder (website pages) and Studio (internal business apps) isn’t immediately obvious to newcomers.

---

Who should use this / who shouldn’t

Use Frappe Builder if:

• You’re already running ERPNext, Frappe HR, or another Frappe app and want to build a public-facing website that pulls live data from that instance without bolting on a separate CMS.
• You have a developer on the team who can handle Frappe environment setup and maintenance.
• Performance on published pages matters and you want clean HTML/CSS output by default.
• You or your designer uses Figma and wants to own the implementation step directly.

Skip it (use Webflow or Framer) if:

• You want a polished, managed website builder with a large community, thousands of third-party plugins, and no server to think about.
• You’re not already in the Frappe ecosystem — the overhead of adopting the entire framework for a website isn’t worth it.
• You need reliable self-hosted behavior without engineering debugging cycles [2].

Skip it (use Ghost) if:

• You’re building a blog or content-heavy site and want a clean, self-hostable CMS with predictable managed hosting costs and strong SEO defaults.

Skip it (use WordPress with a page builder) if:

• You need the widest plugin and integration ecosystem available in open source, even if the performance trade-offs are real.

---

Alternatives worth considering

• Webflow — the commercial benchmark for visual website builders. Largest ecosystem, most polished editor, fully managed, closed source, $23–39/mo for CMS-level features.
• Framer — designer-focused, React-based, managed SaaS, strong for marketing sites with interactions. $10–25/mo per site.
• Ghost — MIT-licensed, open source, self-hostable, best in class for blogs and newsletters. Lighter than Frappe, easier to self-host, $9–25/mo on managed Ghost Pro.
• WordPress + Elementor or Divi — the default answer for non-technical founders. Enormous ecosystem, heavier on resources than Ghost, but the most widely documented self-hosted option.
• Publii — desktop-app static site generator. Zero hosting complexity (generates static files), free, no server required. Very limited dynamic content.
• Frappe CMS (ERPNext built-in) — if you’re already on ERPNext, the built-in web page module handles simpler cases without installing Builder separately.

---

Bottom line

Frappe Builder is a capable, performance-focused website builder with a genuine technical advantage — clean HTML/CSS output and native Frappe database integration — that makes it compelling for exactly one audience: developers and teams already running Frappe apps who need a public-facing website that talks to their existing data. For everyone else, the adoption cost (full Frappe Framework stack, 4–8GB RAM, documented self-hosting inconsistencies) isn’t justified by the tool’s current maturity and community size. The 1,940 star count and the Medium author’s observation that a room full of senior engineers had never heard of Frappe [1] aren’t failures of the technology — they’re honest signals about where this tool sits in the market. It’s not competing with Webflow for mindshare; it’s serving the Frappe ecosystem from the inside. If that’s where you already are, it’s worth using. If it’s not, there are better-supported tools for building websites.

---

Sources

1. Navneet Maheshwari, Medium / Bootcamp — “Why Frappe (ERPNext) is One of the Most Underrated Open Source Framework?” (Jun 3, 2024). https://medium.com/design-bootcamp/why-frappe-erpnext-is-one-of-the-most-underrated-open-source-framework-8f6d94659ada
2. edardev, Frappe Community Forum — “Discrepancies Between Frappe Cloud and Self-Hosted Deployments for Frappe Apps” (Oct 2024). https://discuss.frappe.io/t/discrepancies-between-frappe-cloud-and-self-hosted-deployments-for-frappe-apps/134602
3. Hussain Nagaria, Frappe Blog — “Self-hosting Frappe/ERPNext Apps with Dokploy” (Feb 11, 2025). https://frappe.io/blog/tutorial/self-hosting-frappe-erpnext-apps-with-dokploy
4. Rucha Mahabal, FOSS United IndiaSFOSS 2025 — “Frappe Studio: The Visual App Builder for the Frappe Framework”. https://fossunited.org/c/indiafoss/2025/cfp/c69dnetbr0

Primary sources:

• GitHub repository and README: https://github.com/frappe/builder (1,940 stars, AGPL-3.0 license)
• Official website: https://frappe.io/builder
• Frappe Cloud signup: https://frappecloud.com/builder/signup
• Documentation: https://docs.frappe.io/builder