One-time license: buy once, own the source, no subscription

What "buy once, own the source" actually means

BuilderJS ships as a one-time CodeCanyon license (item 27146783) in two tiers, $52 (Regular) and $99 (Extended). You pay that once and you receive the full source — the ~140KB vanilla-JS engine, 42 element types, 59 property controls, 31 canvas overlays, 30+ templates, and the reference PHP backends — to host on your own infrastructure. There is no SaaS layer, no monthly fee, no per-seat charge, no usage metering, and no phone-home telemetry. Because the editor is a library you embed (not a hosted service you rent), the cost of running it is your own server cost, which you already pay. The honest boundary: the *code* is yours to keep and run forever, but author support and version updates are time-boxed (roughly 6–12 months per CodeCanyon's standard support window). After that window you self-maintain the source you own. We deliberately never call support or updates "lifetime" — only the license to use the code you bought is perpetual.

Honest 1/3/5-year TCO: one-time license vs monthly SDK

Here is the comparison that matters before you commit. BuilderJS is a single up-front cost: $52 (Regular) or $99 (Extended), paid once, with no recurring fee thereafter — your only ongoing cost is the server you already run. Compare that to embeddable builder SDKs billed monthly. As of June 2026, Unlayer's embed plans run $250/mo (Launch), $750/mo (Scale), and $2,000/mo (Optimize), with a forever-free tier and ~10% off annual (source: https://unlayer.com/pricing). As of June 2026, GrapesJS Studio SDK lists $200/mo (Startup, 20,000 sessions) and $2,000/mo (Business, 50,000 sessions), with per-session overages of $20 and $10 per extra 1,000 respectively, plus a 1,000-session free tier (source: https://grapesjs.com/sdk/pricing). Run the math on a mid-tier $250/mo plan: ~$3,000 over 1 year, ~$9,000 over 3 years, ~$15,000 over 5 years — and that climbs further with session overages or white-label add-ons. A $750/mo plan reaches ~$45,000 over 5 years. BuilderJS's up-front $52/$99 does not recur. The trade you are weighing: a SaaS subscription includes ongoing vendor-hosted updates and support for as long as you pay; the one-time license gives you the source to keep, with author support time-boxed to ~6–12 months after which you self-maintain. Verify every competitor figure on the vendor's own pricing page before you decide.

What you own — and what you still bring yourself

"Own it" is precise here, not marketing. You own and self-host the editor: the drag-drop canvas, the 42 elements and 59 controls, the JSON-first model with lossless getData()/load() round-trip, the dual output that exports either modern-CSS page HTML or Outlook-safe email HTML through the EmailExportPipeline (flexbox-to-table conversion, SVG-to-PNG, @media mobile-stack, MSO conditional comments, CSS inlining), the 20+ locale i18n with RTL, and the reference PHP backends (MySQL/SQLite/S3 save, upload, auth, realtime) that you copy and can port to Node, Go, or Python. You can extend it without forking — register custom Elements, Widgets, and Controls via Builder.registerElement, add themes, and wire pluggable vendor-neutral AI hooks. What BuilderJS is NOT: it is the editor you embed, not a platform. It does not send email, host or publish pages, run funnels, do CRM or automation, or process payments. For an email vertical it builds the Litmus-tested, client-safe markup — you bring your own sending. For landing pages it builds the page markup — you bring your own hosting. It is also multi-tenant *capable* (closure-captured), but your app owns tenant isolation, seats, and billing.

Why a finished, supported, framework-agnostic library beats wiring up free parts

There are capable open-source editor cores you could assemble for free, and they are a fair option. The reason teams buy a one-time license instead is not "cheaper than free" — it is finished, supported, framework-agnostic, and it builds both email and pages out of the box. BuilderJS arrives as a working product: 30+ templates and 200+ samples Litmus-tested across 22 email clients, the full email-export pipeline that turns a modern-CSS design into Outlook-safe table markup, 31 canvas overlays for the editing UX, and reference backends you can run on day one. It mounts unchanged in React, Vue, Svelte, Angular, Next.js, Laravel, or plain HTML, so you are not married to one framework's ecosystem. You get a time-boxed author-support window (~6–12 months) to get unblocked during integration, and after that you maintain source you fully own. The honest framing: with free parts you trade money for assembly and ongoing maintenance time; with the one-time license you trade an up-front $52/$99 for a finished, embeddable editor and no recurring bill.

Frequently asked questions

• Is there really no monthly fee or subscription? expand_more

  Correct. BuilderJS is a one-time CodeCanyon license (Regular $52 / Extended $99) paid once. There is no SaaS account, no monthly fee, no per-seat charge, no usage metering, and nothing phones home. Your only ongoing cost is the server you self-host it on, which you already run. By contrast, embeddable builder SDKs billed monthly — for example, as of June 2026 Unlayer's embed plans at $250–$2,000/mo (source: https://unlayer.com/pricing) and GrapesJS Studio SDK at $200–$2,000/mo plus per-session overages (source: https://grapesjs.com/sdk/pricing) — recur for as long as your app exists.

• Does "own it" include lifetime support and updates? expand_more

  No, and we are deliberate about this. You own the source code perpetually — that license to use the code never expires. But author support and version updates are time-boxed to roughly 6–12 months under CodeCanyon's standard window. After that you self-maintain the source you already own. We never describe support or updates as "lifetime"; only your right to keep and run the code is permanent.

• Over 5 years, is a one-time license actually cheaper than a monthly SDK? expand_more

  In most cases the up-front license costs far less over time, but verify the exact figures yourself. BuilderJS is a single $52 or $99 payment, with no recurring fee after that. A monthly SDK at, say, $250/mo (a mid-tier rate as of June 2026) totals roughly $3,000 / $9,000 / $15,000 over 1 / 3 / 5 years, and more once session overages or white-label add-ons apply. The genuine trade-off: the subscription bundles ongoing vendor-hosted updates and support for as long as you pay, whereas the one-time license gives you the source with author support time-boxed to ~6–12 months. Always confirm current competitor pricing on the vendor's own page.

• What does the license let me build — email, pages, or both? expand_more

  Both, from one editor. BuilderJS produces page HTML with modern CSS for web and landing pages, and Outlook-safe email HTML through its EmailExportPipeline (flexbox-to-table, SVG-to-PNG, @media mobile-stack, MSO conditional comments, CSS inlining), with templates Litmus-tested across 22 clients. Important boundary: BuilderJS builds the template and markup only. It does not send the email or host the page — you bring your own sending service and your own hosting.

• Can I use it in a multi-tenant SaaS, and do I have to share revenue? expand_more

  You can — BuilderJS is multi-tenant capable via closure-captured configuration, and there is no per-seat charge, usage meter, or revenue share. The Extended CodeCanyon tier ($99) is the one to choose if end users are charged. The honest caveat: BuilderJS supplies the embeddable editor; your application owns tenant isolation, user seats, and billing. Review the CodeCanyon license terms for your specific distribution model before launch.