Docs

Documentation

Everything you need to go from a first sentence to a live app: the quick start, the full topic tree, guides, troubleshooting and what changed lately.

Start building

Start where you are

Three doors into the same product. Pick the one that matches what you want to do first.

Build your first app

New here? The quick start below takes you from an empty workspace to a published app in five steps, using the same flow every GateBuild app follows.

Talk to the AI chat

Already building? The editor chat is where apps are shaped: Build mode makes changes, Discuss mode plans them with you first, and Plan mode maps a bigger build before a single credit is spent on code.

Connect integrations

When your app needs the outside world — payments, email, a spreadsheet, a CRM — connectors plug it in, usually from a sentence in chat. The Integrations section of the tree below covers each one.

Quick start: your first app in five steps

This is the canonical path. Every app on GateBuild — a booking page, a store, a dashboard — travels it the same way.

  1. Describe

    Write what you want in plain words: who it is for, what it does, what it needs to remember. One honest paragraph beats a perfect specification.

  2. Generate

    GateBuild assembles the whole app at once: pages, database, logins and hosting. You get a working first version, not a mockup.

  3. Iterate by chat

    Ask for changes in conversation — a new field, a different layout, an extra rule. Small edits land in seconds; bigger ones are planned with you first.

  4. Connect

    Add payments, email, files and outside services through connectors. Your app stops being an island and starts doing real work.

  5. Publish

    One click puts the last finished version live on its own subdomain, after the built-in security scan. Your drafts stay private until you say so.

Step 6 — Grow

After publishing, the work turns outward: analytics show who is using the app, the SEO tools help people find it, and workflows take the repetitive parts off your desk. Publishing is the middle of the story, not the end.

Your first prompt

The first prompt is the highest-leverage sentence in the whole build. Five ingredients make it work.

Who it is for

Name the user: "for my salon's customers", "for our delivery drivers". The builder shapes screens, words and permissions around that person.

The problem

Say what hurts today: double bookings, lost invoices, a spreadsheet nobody trusts. The problem decides what the first version must do well.

The screens

List the pages you can already picture: a booking page, a list of orders, an admin view. You do not need all of them — the obvious ones are enough.

The data

Name what the app must remember: customers, appointments, products, payments. That becomes the database — no schema design required from you.

The style

A few words on look and tone — calm and medical, bold and playful — or a site you like the feel of. Colours and fonts can change later in one place.

Other ways in

A prompt is not the only door. You can start from a plan the chat drafts with you, from an existing page URL, from a design file, or from attached files — a spreadsheet becomes data, a document becomes content.

Browse the documentation

The full category tree. Every topic below is a real docs section; the tree grows with the product, and this page grows with it.

Getting Started

  • Quick start
  • First prompt
  • Editor tour
  • Superagents intro

Building Your App

  • Chat modes
  • Components library
  • Canvas
  • Pages
  • Reverting changes
  • Branches
  • Collaborators
  • Commenting
  • Workflows
  • Mobile experience

Setting Up Your App

  • Custom domain
  • Payments setup
  • App-store submission

Integrations

  • Using integrations
  • Connectors catalog
  • Per-connector guides

Performance & SEO

  • SEO & GEO optimization
  • Search visibility

Superagents

  • Creating a Superagent
  • Connecting channels

Account & Billing

  • Plans, workspaces and credits
  • Email change
  • Password reset
  • Account deletion
  • Signed-in devices

Workspaces

  • Roles
  • Secrets & API keys
  • Webhooks
  • Workspace domain

Developers

  • Backend overview
  • Quickstart templates
  • SDK reference
  • CLI commands
  • Apps API

Enterprise

  • SSO & SCIM
  • Audit logs
  • Data residency
  • Backup & restore

Ask the docs

The docs assistant answers from this documentation — the same assistant sits on every docs page.

Guides

Longer, step-by-step walkthroughs, organised by what you are trying to do.

App Building Website Creation Vibe Coding 101 Backend
App Building

Build a booking app in 6 steps

Services, time slots, a calendar that refuses double bookings, and reminder emails — the full path from one sentence to a working reservation system.

Try it in the builder
Website Creation

Build a business website in 5 steps

A homepage that says what you do, a services page, an about page and a contact form that actually reaches you — written in your words, not placeholder text.

Try it in the builder
Vibe Coding 101

Your first prompt: from idea to working app in 4 steps

The beginner's path: what to write first, what the builder hands back, how to ask for changes, and when to publish the first version.

Read the quick start
Backend

Design your app's data in 5 steps

What your app remembers decides what it can do. This guide walks through naming your records, their fields and who may see each row — in plain words.

Try it in the builder
Pricing

How much does GateBuild cost?

The full pricing explainer: the five plans, the two credit meters, what a typical change costs, and how to choose the plan that fits your building pace.

See pricing
Pricing

Is GateBuild free?

Yes — the Free plan is a real plan, not a trial. What it includes, where its limits sit, and the honest signs that you have outgrown it.

See pricing

Troubleshooting

The four problems builders meet most, and the first fix for each. If the first fix does not clear it, the Support page explains what happens next.

Security-scan findings

Your publish stopped on a scan finding. First fix: open the finding — each one names the issue in plain words (an exposed secret, a missing login check, a weak data rule) and offers an AI-proposed fix. Apply it, or ask in chat why it fired.

GitHub sync conflicts

The same file changed in the editor and in your repo. First fix: open the sync view and compare the two versions side by side; pick per file which side wins. Nothing is overwritten silently, and the losing version stays in history.

Domain verification pending

Your custom domain is connected but not yet verified. First fix: check the DNS record the setup showed you is exactly in place at your registrar — verification follows the record, and most delays are a record that has not propagated yet.

Credit pause

Building paused because a credit meter ran out. First fix: open the usage view to see what the credits went to — then upgrade, earn, or add a top-up pack. Manual visual edits are always free, even during a pause.

Changelog

Two tracks: what builders see, and what developers build on. Both are also published as RSS feeds.

Product changelog

2026-11-21 — Internal test site live. The GateBuild product site opens for internal testing: landing, templates, pricing and this documentation.

2026-11-21 — Launch preparation. The rented-API brain wiring lands: the generation engine can run on a frontier model API, metered per build, with the local brain kept for light work.

2026-11-20 — v1 core. The first working core: four templates (booking, form, dashboard, store), the batteries (database, auth, files, email), hosting with publish and rollback, and the subscription billing skeleton.

Developer changelog

BrainProvider contract. The brain layer is an interface, not a vendor: local and rented-API brains implement the same contract, so the model behind a build can change without touching the engine.

Router cost log fields. Every routed build now logs its model and estimated cost alongside the route, so credit pricing is set from measurements, not guesses.

Pool store row-level security. Tenant isolation is enforced inside the store itself: every record carries its builder and app identity, and the store refuses cross-tenant reads.

Reading is good. Building is better.

Your first app is one sentence away — the docs will be here when you need them.

Start building