WebRobot
App Builder · pages

Documentation · App Builder

App Builder

What the App Builder is

The App Builder turns a description of an app into a working web app that runs AI agents for its users.

Three parts work together:

  • The manifest. One document (kind: VerticalApp) describes the whole app: its pages, the form users fill in, the data it keeps, the roles of its users, its agents, what starts them, who approves their work, and how users pay. There is no other source code to write.
  • The runtime. One shared, multi-tenant web server serves every published app. When a request arrives on <slug>.webrobot.eu, the runtime loads that app's published manifest and renders it. There is no build step: a new version is a new manifest.
  • App Studio. The visual editor in the Cloud Dashboard (/dashboard/app-studio). You describe the app to an AI co-pilot, review its proposal on a canvas, change any part by hand, and publish.

The canvas, the property panels, the JSON tab and the co-pilot all edit the same manifest.

Main concepts

ConceptWhat it is
ManifestThe definition of the app (apiVersion: webrobot.eu/v1alpha1, kind: VerticalApp, metadata, spec). See The manifest.
SlugThe app's identifier and address: 3 to 40 characters, lower-case letters, digits and hyphens, starting with a letter. It never changes once the app exists.
DraftThe manifest you are editing, saved with Save draft. A draft can contain problems; it is never public.
Published versionA frozen copy of the draft, made by Publish. Each publish gets the next version number (v1, v2…). Users of the app always see the latest published version.
RuntimeThe server that renders published apps at <slug>.webrobot.eu (and at your own domains), and drafts at preview-<slug>.webrobot.eu. See The runtime.
AgentsThe AI workers of the app, declared in spec.agents. In the draft each agent carries its own profile (profile.inline). At publish each one becomes an agent profile of your organization on the platform. See Agents and automation.
Agent profileThe platform object that actually runs an agent (model, instructions, tools, budget). The published manifest points to it by id (profile.ref).
Formspec.inputForm: the fields a user fills in before an agent runs. The agent's goal is built from them.
CollectionsRecords the app keeps (spec.data.collections): bookings, orders, cases. Agents and forms write them, views show them. See Data.
ViewsThe pages of the app (spec.views): pages built from blocks, the run form, history, reports, tables, charts, chat, approvals and more. See Views and pages.
TriggersEvents that start an agent, a team or a data job: a record written, a webhook, a purchase, a decision, a time.
ApprovalsHuman checkpoints: an agent asks, a person with a given role approves or rejects, and the decision resumes the work.
BillingHow the app's users pay you: free, credits, subscription, per transaction. Payments go to your organization's Stripe account. See Billing.

How they relate: a user signs in (roles come from spec.auth), opens a view, fills the form or writes a record. That starts an agent, directly or through a trigger. The agent works on the platform with its profile, may use the app's collections as tools, may stop for an approval, and writes its result into a view or a collection. Billing decides what the run costs the user.

Lifecycle of an app

  1. Describe. Type what the app should do in the box at the top of App Studio.
  2. Design. The co-pilot builds a manifest and shows it on the canvas as a proposal.
  3. Review. New boxes are green, changed ones amber. You Apply or Discard the proposal, then check the boxes and edit them.
  4. Save draft. The manifest is stored for your organization. The slug is now taken.
  5. Preview. Open preview opens the saved draft at preview-<slug>.webrobot.eu. Agents do not run in the preview and payments are off.
  6. Publish. The agents become agent profiles of your organization, the app gets its own API key on the first publish, and the app goes live at <slug>.webrobot.eu. See Publishing.
  7. Use. Users sign in, run agents, pay. If the app has an admin view, its admins see users, balances, credit top-ups and the latest runs there.
  8. Change. Describe a change to the co-pilot (Propose change) or edit the boxes, then save.
  9. Republish. The same agent profiles are updated, the version number goes up, and the app's data stays.
  10. Export. Optionally, Export code puts the app's code in your GitHub repository, with Android and iPhone shells if you want them. See Export to GitHub and phones.

What you can and cannot do

You can:

  • describe an app in plain language and get a complete manifest in a few minutes;
  • edit every part visually, or edit the whole manifest as JSON;
  • run several agents per app, in teams, with triggers, approvals, schedules and memory;
  • keep records in collections and show them as tables, cards, charts, lists, maps and bookings;
  • add your own Python functions that run in a sandbox (no network, no files);
  • let users pay you with credits, plans or per transaction, through your Stripe account;
  • serve the app on your own domains;
  • export the code to GitHub and build Android and iPhone apps from it.

Not available yet:

  • Agents do not run in the preview. Publish to try a real run.
  • Data jobs (spec.data.jobs) are created as pipelines on the platform at publish, but the runtime does not run them.
  • Channels other than web (phone, Telegram, email) are kept in the manifest but not connected yet.
  • Some phone features cannot be used yet by any part of an app (contacts, Bluetooth, background location, phone reminders, speech to text). See Export to GitHub and phones.

Documentation map

PageWhat it covers
OverviewThis page: what the App Builder is, its concepts and lifecycle.
QuickstartFrom a description to a live app in App Studio, step by step.
App StudioThe editor in full: co-pilot, canvas, inspector, page editor, settings, preview, apps list.
The manifestThe structure of a VerticalApp manifest and how its parts fit together.
Sign-in and rolesHow users sign in, roles, what anonymous visitors can see.
DataCollections, records, who owns them, retention, files.
Views and pagesEvery view type, pages built from blocks, the menu and the header.
Agents and automationAgents, goals, tools, teams, triggers, approvals, schedules, templates, memory, Python slots.
MessagingEmails and notifications the app sends, and channels.
BillingCredits, packs, plans, pay per use, Stripe Connect payments.
PublishingDrafts, preview, what Publish does, addresses, custom domains, republishing, deleting.
Export to GitHub and phonesThe GitHub export, the web code, the Android and iPhone builds.
The runtimeHow the shared runtime serves apps, and what it does for them.
ValidationProblems and warnings, what blocks publishing and how to fix it.
ReferenceEvery manifest field, generated from the JSON Schema.

For a guided introduction to writing manifests, follow the tutorial at webrobot.eu/learn/manifest.