Deploy overview
Upload files or source code. Agent Lab builds them into a version, gives it an address and runs it on Google Cloud. Every version is kept.
What you can deploy#
dist/. No server needed.Web serviceSource code with a Dockerfile, for webhooks, APIs, and code that uses a secret or calls other services.Deploy with an AI toolLet Claude Code or Codex create the project, upload and go live for you over MCP.Move from another hostWebsites, Docker services, PostgreSQL and MySQL, cron jobs and domains. Preview first, then switch DNS, with no downtime.Add a database, a cache or your own image#
REDIS_URL.How it works#
- Create a project Pick a name and an address label. The label becomes part of the project's address.
- Upload What you upload decides what the project is: source code with
package.jsonis built automatically, anindex.htmlat the top makes a web page, aDockerfilemakes a service. - Build and check The platform builds a new version and scans the files for secrets, personal data and scripts loaded from elsewhere. A web service's image is also scanned for vulnerable packages. Every version gets its own preview address.
- Go live A project's first version goes live on its own. While the workspace has only the production environment, every newer version does too; with more environments, you choose when the newest version goes live.
- Fix and deploy again If a new version has a problem, fix it and deploy again. To try versions before visitors see them, use a separate environment, such as staging.
Key concepts#
| Term | Meaning |
|---|---|
| Project | A site or service you deploy, with its own address, versions and settings. |
| Version | What one upload built. Versions are never overwritten. |
| Public address | The address visitors open. It shows the live version. |
| Internal address | An address only your organization's services can call. |
| Environment | Another line of versions of the same project, with its own settings, secrets and databases. |
The glossary lists these terms in every language.
Where it runs#
Static sites, web services and scheduled jobs run on Google Cloud in asia-east1, and so do Redis caches. A database's region is chosen when you create it: asia-east1, asia-northeast1, us-central1 or europe-west1, and it can't be changed later.
Visitors' requests pass through Google's global load balancer and Cloud CDN, so static files may be answered from the Google location nearest the visitor.
Web page or service?#
If anything runs on a server, deploy a web service
That includes receiving a webhook or a form, using an API key, and calling another service from the server. An API key in a web page can be read by every visitor.