Glossary
The words this documentation uses, defined plainly.
Account
You: one sign-in, one profile. An account can belong to several workspaces.
Audit trail
A record of every merged change, who approved it and when.
Builder
The part of Automo Build that reads your message, plans the change, writes the code and checks the result.
Conductor
The orchestration layer for running many projects at once: fleet view, Protected Code Zones, moderation and live health. See Conductor.
Credit
The unit building work is measured in. See How credits work.
Custom domain
A domain you own, pointed at a project, so the app lives at your address.
Custom sandbox
A sandbox image that wraps AI-assisted engineering around an existing stack such as Rails, Java, Go, Python or Node.
Database
The part of the app that remembers things after the browser closes. Records live in tables with access rules.
Doctor
A read-only AI SRE that diagnoses problems on the live app and drafts a fix for approval. See Doctor.
Environment
Either preview (where you are working) or live (what other people see). Publishing moves the preview to live.
Guardrails
Governance for AI changes: business areas, risky-change detection, plain-English policies, human review and an audit trail. See Guardrails.
Integration
A service connected to a project, such as a payment provider, an email sender, a calendar or an AI model.
Live
The published version of the app, served on its address or your custom domain.
Migration
A structured change to a database that already contains data, such as adding a column. Migrations need care and a backup.
Preview
The always-current version of the project while you build. Customers do not see it.
Project
One app: its code, database, history and publishing settings.
Protected Code Zone
An area of code, such as billing or auth, locked so the AI cannot change it without the required approval.
Publish
The action that makes the current preview the live app.
QA
Automated testing that replays key journeys in a browser and gates publishing. See Automated QA.
Role
What a person is allowed to do in a workspace. Separate from the roles inside your app.
Secret
A private value, such as an API key, used only by server code and never placed in browser code.
Security scanning
Static scans, dependency checks and live probes that confirm real vulnerabilities. See Security scanning.
Server function
Code that runs on the server rather than in the browser. Used for anything that needs a secret or a trusted check.
Version
A saved state of a project after a change.
Webhook
An automatic message from one system to another when something happens.
Workspace
The shared home for a team: members, projects, billing and integrations.
Was this page helpful?