Webflow builds websites: marketing pages, blogs, portfolios, content in a CMS. Luna Park builds applications: logic, user accounts, and data that users create. They rarely compete for the same project.

- **Visual logic.** Interface and backend logic built as graphs.
- **User accounts.** Sessions, roles, and OAuth2 built in.
- **Complete export.** Frontend and backend as Vue and Node.js.

![Sunset Park in the Luna Park editor](https://luna-park.app/static/assets/builder-DAXbtfYB.png "Sunset Park, a demo site built with Luna Park.")


## At a glance

Webflow builds websites, Luna Park builds applications. The main differences: logic, data, and code export.

| | Luna Park | Webflow |
|---|---|---|
| **Made for** | Web applications | Websites and content |
| **Logic** | Visual scripting graphs, compiled to JavaScript | Interactions, custom code, external tools |
| **Data** | PostgreSQL, written by your users | CMS collections, edited by your team |
| **Backend** | Routes and crons | None visual. Webflow Cloud hosts code-based apps |
| **User accounts** | Users plugin: sessions, roles, OAuth2 | Third-party tools (Memberstack, Outseta...) |
| **Code export** | [+Full application] (Pro) | [~Static HTML, CSS, JS] Without CMS content |
| **Pricing** | Free, or Pro at €25/month or €300 once | Site plans + workspace plans |

## Example: a waitlist form

Visitors enter their name, email, and favorite ride, and get a ticket number.

::: columns
### Luna Park

1. Place the fields and a button, each field bound to a variable.
2. On click, a graph sends the variables to a backend route and shows the ticket.
3. The route inserts a row in the `Waitlist` table and returns its id.

---

### Webflow

1. Add a form block.
2. Submissions are stored in the site's form submissions.
3. Saving them to a database or returning a ticket number needs Zapier, Make, or custom code.
:::

::: gallery
![The click logic of the waitlist form](https://luna-park.app/static/assets/logic-C66duI84.png "On click: read the fields, call the route, show the ticket.")

![The Waitlist table in the editor](https://luna-park.app/static/assets/database-BIq5wdGO.png "The entries, in the project's PostgreSQL database.")
:::

## Code export

Webflow's export leaves out everything dynamic: CMS content, forms, accounts. Luna Park exports the complete application, frontend and backend.

![The waitlist component compiled to Vue](https://luna-park.app/static/assets/code-BUYWx0sG.png "The waitlist, compiled to Vue and TypeScript.")

## Other differences

- **Logic.** Webflow retired its Logic automation tool in 2025 and User Accounts in 2026. In Luna Park, [visual scripting](/docs/visual-scripting/introduction) runs in the interface and the backend.
- **Data.** Orders, messages, profiles: relations, constraints, and transactions in [PostgreSQL](/docs/backend-data/database), with [routes](/docs/backend-data/routes) and [authentication](/docs/backend-data/auth) controlling access.
- **SEO.** Each Luna Park page has its own title, description, and social image, and the backend serves a sitemap ([SEO](/docs/deployment/seo)).

![The SEO panel of a page](https://luna-park.app/static/assets/seo-BCDFkDXI.png "SEO settings of the Sunset Park home page.")

## Which one to choose?

::: columns
### Luna Park

- You build an app: SaaS, dashboard, marketplace, internal tool.
- Users have accounts and create data.

---

### Webflow

- You build a website: marketing pages, blog, portfolio.
- Your team edits content in a CMS.
:::

Many products use both: a Webflow marketing site, and a Luna Park app behind the "Log in" button.

## Before switching

- Luna Park is not a CMS.
- Page tags are written by the server, but page content renders in the browser. For content sites that rely on search traffic, Webflow fits better.

::: info
Based on Webflow as of October 2026. See [webflow.com](https://webflow.com) for current features and prices.
:::