Building & deploying apps

Your bot can build real software for you — not a toy, but a working app that lives at a real URL. You describe what you want in plain language; your bot turns that into a plan, writes the code, and hands you back something you can use. You never have to touch the code yourself.

What you can build

• Websites and landing pages — a marketing page, a brochure site, or a page on your own domain.
• Tools and apps — a form, a dashboard, a small web app with its own database, logins, and file storage.
• Internal apps — something just for you or your team to track work, manage data, or automate a process.

If you can describe what it should do, your bot can usually take a first pass at building it. The more clearly you describe the goal, the better the result.

How the build conversation works

You don't fill out a form or write a spec. You talk to your bot:

1. You describe the goal. "I want a page where customers can book a call," or "build me a tool to track invoices." Your bot asks clarifying questions until it understands what "done" looks like.
2. Your bot writes a plan. It captures the vision, the screens, what each feature needs, and how it'll know each piece actually works. This plan is the contract for the build.
3. It spawns code sessions to build it. Your bot opens separate working sessions (see Sessions) that write the actual code, run tests, and check their own work.
4. It opens pull requests. Each chunk of work becomes a reviewable change. Your bot reviews and merges them itself — you don't have to.
5. You get a working app. Once it's deployed, your bot confirms the URL serves a real, working page and hands you the link.

You can let the build run on its own and check in when you want a status, or stay in the loop and watch each step — your call.

Where your apps run

There are two homes for an app, and they serve different purposes:

• GATE-hosted (for building and development). While you're building and trying things out, your app runs on GATE's own infrastructure at yourapp.yourorg.<your GATE base domain> (for example, https://yourapp.acme.example.com using your GATE base domain). There's nothing to set up and nothing to pay for — it's the workshop where the app comes together. This is for development, not for running a real customer-facing business long-term.
• Your own server (for production you own). When you're ready to run an app for real, your bot can set it up on your own Hetzner server — a box in your name, on your account, paid by you. You own it outright; your bot just provisions and operates it. This is the right home for anything customer-facing or business-critical.

You don't have to decide this up front. Start in the workshop, and move to your own server when the app earns it.

Going deeper

For the full step-by-step — from first pitch to live URL — follow the Build and deploy an app walkthrough. To understand where code runs and what's included, see Projects and hosting. And once something is live, you can tune its design by talking — see Editing live pages (VCA).