Apps, data & members
Beyond websites: databases, secure actions and signed-in members — all from chat.
wish4 builds more than brochure sites. Ask for an app — a booking system, a directory, a members area — and the builder sets up what it needs. Here's a full app built start to finish:
A real database
When your app needs to store things (bookings, listings, RSVPs), the AI defines data tables for it and wires the pages to read and write them. You'll see it in the chat as a “Defined tables” step. Each table has access rules — public, members-only, or owner-only — so visitor data stays where it belongs.
Secure actions & secrets
When a page needs to call an outside service (send an email, hit an API), the AI creates a server action — the call runs on wish4's servers, not in the visitor's browser. If it needs an API key, it asks you with a secure key request in the chat: the value goes straight into the encrypted vault and is never shown in the conversation, never sent to the AI model, and never embedded in your pages.
Never paste an API key as a normal chat message — always use the secure request form when the AI asks, or add it in Integrations.
Members
Switch the site to Members only in Publishing & visibility and visitors sign in with their email. Each becomes a member of your site — the AI can build members-only pages, per-member data and “my account” flows on top.
Describe the whole app in one go — *“a padel court booking app: visitors sign in, pick a court and a time slot, and I see all bookings in an admin page”* — and let the AI decide the tables.