Side by side
The same questions, asked of each category. "Dashboard CMS" means WordPress, Drupal, Craft and similar; "website builder" means Wix, Squarespace, Webflow, Framer and similar; "headless CMS" means Contentful, Sanity, Storyblok, Payload, Strapi and similar.
| Custom site with inlay | Dashboard CMS | Website builder | Headless CMS | |
|---|---|---|---|---|
| What it is | An editing layer built into a custom-coded site. Sign in and the live page is the editor. | A content system with themes and plugins, edited in a separate admin area. | A hosted platform with templates and a visual editor. | A content API and admin; a separate frontend renders the site. |
| Design | Fully custom. No theme underneath; the developer writes the markup and CSS. | Theme-based, customizable with page builders or development. | Template-based, flexible within the template's limits. | Fully custom frontend, built and hosted separately. |
| Where editing happens | On the real page, in the real CSS. Drafts, device previews, comments and work orders built in. | In a dashboard, with a block editor or page-builder plugin; preview in a separate view. | In a visual editor that approximates the published page. | In forms in the admin; preview depends on what the frontend wires up. |
| Marking up content | Mostly none. inlay discovers editable text; attributes are the exception. | Templates map fields to the theme. | Not applicable; the builder owns the markup. | Every field is modeled and fetched by the frontend. |
| Repeating content | Typed collections with generated forms, drafts, scheduling, search, validation and SEO templates. | Posts and custom post types, often via plugins. | Collections or CMS items, within platform limits. | Its strength: rich content models with an API. |
| Hosting | One Cloudflare Worker per site. No origin server, container or database to run; visitors never load the editor. | A PHP host or managed WordPress host, plus a database. | Included in the subscription. | The CMS is hosted by its vendor; the frontend is hosted separately. |
| Maintenance | No plugins to patch. Updates reach every site as one version bump. | Core, theme and plugin updates and security patches, often on a paid plan. | Handled by the platform. | Two systems to keep current: the CMS and the frontend. |
| Ownership | You own the site and its code. Content is versioned in your own repository. | You own the site and can move hosts; plugins and themes carry their own licenses. | You rent the platform; leaving usually means rebuilding. | You own the frontend; content lives with the vendor unless self-hosted. |
| Growing into software | Built into the same codebase: routes, admin pages, plugins, scheduled jobs, one sign-in. | Through plugins; genuinely custom features need development. | Limited to the platform's apps and integrations. | Built in the frontend or in other services; the CMS stays a content store. |
| Who installs it | A developer: yours, or Cary Digital Design. | Anyone, with a host; agencies for custom work. | Anyone. | Developers. |
| Cost model | Project price, hosting included, no per-change invoices. | Hosting plus a build, often with monthly maintenance and hourly changes. | Monthly subscription, plus your time. | Vendor subscription plus frontend build and hosting. |
inlay versus a dashboard CMS
A dashboard CMS makes the site a rendering of a database you edit somewhere else. inlay makes the site the source of truth and edits it in place.
WordPress and its peers earned their share of the web for good reasons: an enormous ecosystem, a plugin for almost anything, serious e-commerce, and any developer can work on them. If you have an in-house team that already knows one, or a very large editorial operation, a dashboard CMS is a reasonable default.
The costs show up later. Core, theme and plugin updates need someone watching them. Security patches and performance tuning become a maintenance plan. And the admin area looks nothing like the page visitors see, so editors guess what their words will look like. inlay removes the second system: there is no admin to learn, nothing to patch on the site, and the editor is the page. Cary Digital Design's longer article, Inlay vs. WordPress, Wix, and Squarespace, goes into cost and migration in more detail.
inlay versus website builders
A website builder gives you a template and an editor on a rented platform. inlay gives a custom-coded site an editor without taking over the design.
If you need a simple site this week, have the time to build it, and a template genuinely fits, a hosted builder is the honest answer. They are inexpensive, they handle hosting and updates, and the editors are approachable.
The trade-offs are a platform you cannot take with you, a design that lives within the template, and a ceiling you hit the first time the business needs something the platform does not offer. inlay is the other way round: the design is written as ordinary custom code with no theme underneath, the site and its content are yours, and when the business needs a portal or a back office it is built into the same site.
inlay versus headless CMSs and visual-editing add-ons
A headless CMS separates content from presentation and asks a frontend to put them back together. inlay never separates them.
Headless systems are a good fit when the same content feeds several frontends, or when a large team models content formally. The price is two systems: every field is modeled in the CMS and fetched by the frontend, previews have to be wired up, and editors still work in forms. Several headless vendors now add a visual-editing mode that overlays the rendered site, which narrows the gap but keeps the two-system architecture underneath.
inlay starts from the page. Text is editable because it is on the page, not because someone modeled a field for it. Where structure is genuinely needed (posts, events, listings) its typed collections and content API cover what most small and medium sites use a headless CMS for, inside the same Worker that serves the site. A site that truly needs to feed several frontends from one content store is a case for headless.
Where inlay is the better fit
- The design has to be yours. No theme underneath, no "we customized a template".
- Non-technical people will keep it current. Menus, events, posts, staff bios and prices change often, and nobody wants a dashboard to learn or a developer invoice for a typo.
- The site will grow into software. A portal, a listings database or a back office can be built into the same codebase. That is how Open Pattern runs an aircraft brokerage on it.
- You are tired of maintenance. No plugins to patch, hosting included, and inlay updates reach every site as a single version bump.
- You build on Cloudflare Workers, or are happy to, and want one Worker to be the whole platform.
Where it is not
- You want to sign up and start today. inlay is distributed privately and installed by a developer. A website builder is self-serve.
- You need a large plugin ecosystem or a particular off-the-shelf integration that only exists for WordPress or a hosted platform.
- One content store must feed many frontends. That is what a headless CMS is for.
- You need open-source software you can fork. inlay is not open source; a site extends it through adapters, plugins and its own routes rather than by patching core.
Moving to it
Content from WordPress, Wix, Squarespace and similar platforms can be exported into a clean custom site with inlay built in, and many of Cary Digital Design's website projects start exactly that way. Plugins and apps are the part to look at closely: booking tools, stores and custom integrations sometimes have to be rebuilt or reconnected, and that is what changes the price. The studio reviews what is involved before anyone commits, and gives a straight answer about fit. That conversation starts here.
Questions people ask next
-
Is inlay a WordPress plugin or a WordPress alternative?
Neither, exactly. WordPress is a full content management system you install and run. inlay is an editing layer built into a custom-coded website, so the website itself is the product and inlay is how the team edits it. If you are choosing between them, you are choosing between a theme-based CMS with a separate admin and a custom-coded site that is edited in place.
-
Is inlay a headless CMS?
No. A headless CMS stores content behind an API and leaves rendering to a separate frontend. inlay keeps the site as the source of truth and adds editing to the real page, though its typed collections and content API cover what most small sites use a headless CMS for.
-
Is inlay a website builder like Wix, Squarespace or Webflow?
No. inlay does not generate any of the site's design. A developer writes the markup, CSS, routes and hosting, and inlay adds editing to what they built. Website builders give you a template and a visual editor on a rented platform.
-
Can content be moved from WordPress, Wix or Squarespace to a site with inlay?
Yes. Content from those platforms can be exported into a clean custom site with inlay built in, and many of Cary Digital Design's website projects start that way. Plugins and apps such as booking tools, stores and custom integrations are the part to look at closely, since they sometimes have to be rebuilt or reconnected.