How a web app is put together

When you describe an app, the builder produces a complete piece of software with the same shape every time. Knowing that shape helps you ask for the right things and understand what you see in the dashboard.

Pages

Your app is a modern single-page web application. Each screen a visitor can open is a page with its own address inside your app, such as /, /pricing or /dashboard. The builder writes the pages, the navigation between them and the shared layout, and styles everything from one theme so the whole app changes together when you ask for a different look.

The database

Anything the app remembers lives in a table: customers, bookings, orders, tickets. The builder defines each table with typed fields and permissions, seeds it with realistic starter rows so the app never opens empty, and wires the pages to read and write it. You can browse and edit every row yourself under Database. See Your app's database.

Accounts

If the app has private or per-user data, it gets sign-in: email and password, Continue with Google, or both. Every new account is an ordinary user; you are the first admin. Roles and permissions are checked on the server for every request, not just hidden in the interface. See Users, sign-in and roles.

Backend functions and automations

Work that must not happen in the visitor's browser, calling another service with your own key, a nightly job, a webhook from a payment provider, runs as a backend function on the server. An automation runs a function on a schedule or when data changes. See Backend functions and Automations.

Email, files, AI and PDFs

These are platform services your app calls without any setup: it sends email under its own name, stores private uploads, calls AI for summaries and structured answers, and renders PDFs from its own layouts. They are billed to you, the owner, never to your app's users.

Hosting

Every app is hosted for you. It gets a free address the moment you publish, and you can connect a domain you own. Certificates are issued and renewed automatically. See Publishing and Custom domains.

The builder's memory

The builder keeps private notes on each app: the decisions you made together, the parts you asked it to leave alone, what is half-finished. That is how a follow-up message a week later picks up where you left off instead of starting again.

The code is yours

Open any file under Code, edit it there, or download the whole project as a ready-to-run package. Your data and backend functions keep running on Praxivara either way. See Editing the code yourself.