Platform categories
Visual CMS vs app builder vs internal tool builder
The core differences between three platform categories that often get grouped under the same low-code label.
A visual CMS controls publishing
A visual CMS helps teams publish pages and content inside a controlled frontend. The key workflows are editing, previewing, composing approved components, and giving non-engineers room to ship without breaking the system.
This category fits marketing pages, ecommerce content, docs, product pages, and campaign experiments. It is especially useful when the company already has a modern frontend stack and wants editors to work visually.
An app builder controls product logic
An app builder focuses on screens, state, workflows, database records, and user actions. Bubble and WeWeb-style workflows live closer to this category, though they approach the problem differently.
This category fits portals, marketplaces, SaaS MVPs, operational apps, and customer-facing workflows. The important questions are data modeling, authentication, performance, API access, and how much code ownership the team needs later.
An internal tool builder controls operations
An internal tool builder is optimized for admin consoles, dashboards, support tools, and back-office workflows. The interface matters, but reliability and permissions matter more.
If a tool will touch production data, compare role-based access, query safety, logs, deployment options, and how the team will maintain business logic. Internal tools are still software, even when they are built visually.