Getting started

From the first sentence to an app that runs

• Building your first appWhat to write in the first box so that the first build already gives you something usable.
• What exactly gets createdFiles, tables, an address and a project code — and where each of them sits on screen.
• Changing things after the first buildYou carry on writing in plain language. Every change is a build, and every build is a version.
• Starting from a templateEvery template is a whole app that already runs. Cloning copies the structure, never the data.
• When a build failsWhat is checked before a version is saved, why it costs you nothing, and what to try next.

The console

Eleven screens, one per question

• The console: eleven screensThe editor builds, the console runs. What is on each screen, and how to go straight to it.
• The log: what happened and what it costTwo columns — actions in the project, and builds with their tokens and credits.

Data and permissions

Tables, who sees what, import and export

• Who sees what, and how it is enforcedFour rules per table, five possible audiences, and a check on the server on every request.
• Editing records yourselfAdding, editing and deleting by hand — and where a deleted record goes.
• Importing a CSV fileThree steps, and the third shows exactly what will go in before anything is written.
• Getting your data outThree different exits: one table, the user list, and the whole project.
• A table's history, and going back in timeWhat changed, when, and how to return a whole table to the state it was in at a given hour.
• Test modeTry the app out without leaving rows behind that nobody wants.

Your site's users

Sign-up, invitations and roles

• Your users' accountsThey sign up to your site — not to our system — and everyone comes in as an ordinary user.
• Invitations and sign-up approvalLet somebody in by name, or require every sign-up to go through you.

Going live, addresses and security

What is public, where it sits, and what is blocked

• What is public, what is private, and when it goes liveThere is no “publish” button. A build that passes the check goes live on its own — and one switch decides who gets in.
• Going backEvery build is a version. Restoring does not delete what came after it — but it does immediately replace what is live.
• The free addressEvery project gets one straight away. Changing it is a house move, not a rename.
• Connecting a domain of your ownA TXT record proves ownership, and only a real DNS query marks it “verified”.
• Redirects from an old addressWhat to do the day after you rename a page.
• The security screenTwo switches, and a list of what is protected whether you open this screen or not.
• Taking it off the air, and deleting itTwo different actions — and what is left after each of them.

Being found, and measuring

Google, social, and who actually visited

• How your site appears in Google and on socialTitle, description and share image — for the whole site and for each page.
• Who visited the siteCounted by us, with no third-party script and no estimates.
• The platform badgeThe small badge in the corner — what it is, and how to remove it.

Credits and billing

How it is measured, what is not charged, and how to stop it

• How a credit is measuredOne credit = $0.10, worked out from tokens actually measured, after the version was saved.
• How to stop spendingA ceiling per build, per day and per month — yours, and checked before the work starts.
• What is in each plan4 plans, what they cost, and what is open on all of them.

Connect and extend

Live data, keys, and the knowledge library

• Live Israeli data in your siteShabbat times, holidays, Home Front Command alerts and exchange rates — with no key and no outside service.
• Driving Vixtur from outsideOne API key, and an MCP server that connects your agent to your projects.
• What the build already knowsAn open-source Israeli knowledge library, design systems written for Hebrew, and the tools an agent can call.

Want to see how it works underneath — the security, the price? There are guides that go into the detail.Contact us