Help centre
31 articles about what the system actually does. If something is missing, write to us.
Getting started
From the first sentence to an app that runs
What to write in the first box so that the first build already gives you something usable.
Files, tables, an address and a project code — and where each of them sits on screen.
You carry on writing in plain language. Every change is a build, and every build is a version.
Every template is a whole app that already runs. Cloning copies the structure, never the data.
What is checked before a version is saved, why it costs you nothing, and what to try next.
The console
Nine screens, one per question
Data and permissions
Tables, who sees what, import and export
Four rules per table, five possible audiences, and a check on the server on every request.
Adding, editing and deleting by hand — and where a deleted record goes.
Three steps, and the third shows exactly what will go in before anything is written.
Three different exits: one table, the user list, and the whole project.
What changed, when, and how to return a whole table to the state it was in at a given hour.
Try the app out without leaving rows behind that nobody wants.
Your site's users
Sign-up, invitations and roles
Going live, addresses and security
What is public, where it sits, and what is blocked
There is no “publish” button. A build that passes the check goes live on its own — and one switch decides who gets in.
Every build is a version. Restoring does not delete what came after it — but it does immediately replace what is live.
Every project gets one straight away. Changing it is a house move, not a rename.
A TXT record proves ownership, and only a real DNS query marks it “verified”.
What to do the day after you rename a page.
Two switches, and a list of what is protected whether you open this screen or not.
Two different actions — and what is left after each of them.
Being found, and measuring
Google, social, and who actually visited
Credits and billing
How it is measured, what is not charged, and how to stop it
Connect and extend
Live data, keys, and the knowledge library
Shabbat times, holidays, Home Front Command alerts and exchange rates — with no key and no outside service.
One API key, and an MCP server that connects your agent to your projects.
An open-source Israeli knowledge library, design systems written for Hebrew, and the tools an agent can call.