Skip to content

WeWeb

WeWeb is a visual web app builder that can use its own backend or connect your screens to a separate service.

Visit WeWeb

What do you build in the visual editor?

Build the pages and decide what happens when someone presses a button or submits a form. A workshop registration page might display sessions from a database and save a new registration when someone selects a time. Decide where the database and any sign-in will live before you connect the screens.

How do people get the latest version?

Publish the app from the editor. If your plan includes staging, use that separate address to check what changed before publishing to the address your customers use. Check which database each address connects to before testing submissions.

Which parts appear on the bill?

Compare the workspace plan for people editing the app with the hosting plan for the project visitors use. Check the editor seat and AI allowance, then the hosting limits for visits and data sent to visitors. Include any external database or email service you connect.

What comes with you if you host the app yourself?

The Essential workspace plan and above can export code. If the app uses WeWeb’s backend, you can export the interface and backend code together or separately. The database structure can come with the code. Saved records, uploads and secrets need a separate move.

For a self-hosted WeWeb backend, arrange PostgreSQL and file storage and reconfigure your connections. WeWeb documents that its built-in email service is unavailable after self-hosting. If you export only the interface, it still needs a working backend.

What would you move for a workshop registration app?

Use fictional registrations to work out whether you can carry over the screen, the bookings and the confirmations before choosing a host.

  1. Draw the pieces
    Put the registration page, its records, uploaded waivers and confirmation emails on separate lines.
  2. Mark what comes with the export
    Mark the code and database structure. Give the saved registrations, waiver files and email service their own migration steps.
  3. Write the first check
    On paper, have one fictional attendee register and return to see the booking. Mark which service needs to work for each step.