Vorx vs website builders

Website builders made publishing a professional site something anyone can do in an afternoon. Vorx aims at a different target: applications with data, users and logic. Knowing which you actually need saves a lot of wasted effort.

Pages versus apps

A website builder is organised around pages. You pick a template, drop in text and images, arrange sections, publish. It's the right tool for a marketing site, a portfolio, a landing page or a blog — anything whose job is to present content to visitors.

Vorx is organised around an app. You describe what it should do — who logs in, what data it holds, what happens when someone clicks — and it builds the screens, data model, auth and backend. The unit of work is behaviour, not layout.

Data and logic

Website builders can bolt on forms, a store or a booking widget, usually through plugins. That covers common cases well. The moment you need custom rules — records that relate to each other, per-user views, workflows with state — you're fighting the tool.

• Website builders excel at presenting content to visitors
• Vorx apps are built around records, relationships and per-user data
• Custom logic in a page builder means stacking plugins; in Vorx you describe it
• Auth, roles and protected screens are first-class rather than add-ons

If your project is mostly a database people read from and write to, that's an app.

Who sees what

A page builder's content is the same for everyone who visits, and its access controls usually stop at a password on a page. An app's whole job is often the opposite: this client sees their invoices and nobody else's.

Vorx enforces that scoping in the database itself rather than by hiding a link, which is the difference between a private area and a genuinely private one.

Interactivity and realtime

If two users changing the same record should see each other's updates, you've outgrown a page builder.

Every Vorx app has its own database and backend, so two people can each have real edit access to the same record — behaviour a content-first page builder isn't designed to offer at all. Live, realtime sync between simultaneous edits (VorxSync) is on our roadmap; today, each save is a normal request to the server rather than an instant, offline-capable one.

Ownership and flexibility

Website builders are typically closed platforms: you build in their editor, host on their infrastructure, and moving means rebuilding. For a simple site that trade-off is usually fine — convenience in exchange.

Vorx generates a real codebase you can take with you, so when requirements grow you have somewhere to grow into.

When a website builder is the right call

Use one when the goal is a great-looking site that presents content: marketing pages, a portfolio, a blog, an event page, a brochure with a contact form. For that job it's faster, cheaper and perfectly suited, and reaching for an app builder would be overkill.

Choose Vorx when people log in and do things: dashboards, internal tools, trackers, marketplaces, or any product where the data and logic are the point.

Plenty of teams run both — a website builder for the public marketing site, Vorx for the app behind the login. Though if you'd rather keep one tool, Vorx builds marketing sites too; see Launch a marketing site.

In the docs: Welcome.