Your AI builds. A person decides.
Leaf is made for companies whose teams build with AI. Here is what keeps a mistake, a leak or an abuse away from your sites, in plain words.
Every role sees what it needs. Nothing more.
Your AI acts on behalf of one person, with that person’s role. People invited from outside the company only reach the texts and images of one project.
Nothing reaches your visitors without a person.
Your AI makes the change
It works on a copy of the site, never on the one your visitors see.
A preview at its own address
Hidden from search engines, with its own test database, test accounts and test payments.
A person approves
Putting a site online is a person’s click by default. An owner can let the AI do it, project by project.
Online, history kept
Every change to the code is kept. The last ten versions of a site stay ready to put back online.
Each site in its own box.
A site built by one team can never read another site, our platform, or your secrets.
One address per site
Each site has its own address and runs apart from the others on Cloudflare. Leaf removes any cookie a site tries to share with other sites.
Sites never touch our database
A site reads its published content through Leaf, with a read-only key that opens that one project.
Building in a closed room
A site is built in a throwaway container with no internet, except the package registry through a filter, and no secret inside.
Outgoing calls to declared addresses
A site’s server code reaches only the addresses its project declares. Everything else is refused, redirects included.
Secrets typed by a person
The AI says a site needs a key; an owner or admin types it in the dashboard. It is sealed (AES-256-GCM), never shown again, never readable by the AI.
Real data away from unchecked code
Previews use their own database and test accounts. Real data only reaches code a person put online.
Easy to give, easy to take back.
No password to steal
People sign in to Leaf with a link sent by email, or with Google. Accounts on your own sites have their passwords hashed (scrypt).
AI connections you can cut
Each person’s AI connection is listed in the dashboard. Cutting it stops the AI at once, even in the middle of a task. Owners and admins see everyone’s.
Leaving ends access
Removing someone from the organisation ends their AI connections and their access to its projects at once.
Every change has a name
Each change to a site records the person it was made for, and whether their AI or the dashboard made it.
The platform in Europe, your sites close to your visitors.
- Accounts and organisations
- Content and translations
- Your sites’ user accounts
- Form submissions
- Billing
- Pages, images and files
- Server code
- Databases
- Real time
- Card details
- Payouts of your own sales
Take it with you, or delete it.
Export a project
Its code, its content in every language, its images and files and its translations, in one file.
Delete for real
A project, an organisation or your account, from the dashboard. The site goes offline and its data is removed.
Statistics without cookies
Visits are counted with an anonymous fingerprint that changes every day: nobody is followed from one day to the next.
Keeping phishing off Leaf.
Links checked
Redirects that send visitors to other sites are checked against Google Safe Browsing.
Sites on their own domain
Sites live on leafpages.dev, never on getleaf.dev: a bad site cannot borrow Leaf’s name or cookies.
Suspension
Leaf can suspend a site or an organisation used for phishing, fraud or malware.
Report a site
Write to [email protected] with the page’s address. Every report is read.
A question from your security team?
We answer every question by email, and send our data processing agreement on request.