Build an application
Build an independently released application against Cloud's public runtime contract.
2 min read
Updated 2026-08-28
#applications#architecture#deployment
The normal application is standalone: it has its own repository, version, image, and release cycle and connects to Cloud through published packages.
Start with Platform model for the ownership and runtime boundary, then create the first standalone application.
Choose the project shape
Choose the repository from release ownership. The public application contract stays the same.
| Project | Choose it when |
|---|---|
| Standalone | The application team owns the repository, image, compatibility decision, and release |
| Built-in | Cloud maintainers intentionally release the application with the platform |
Do not begin in the Cloud monorepo only to gain access to internal imports or workspace aliases. Use the monorepo path only when the application is intended to ship as part of Cloud itself; see Monorepo development.
Build tasks
| Task | Page |
|---|---|
| Create and verify a standalone service | First application |
Look up every defineApp() option |
Define an application |
| Prepare data and manage process work | Application lifecycle |
| Publish routes through the gateway | Routes and discovery |
| Add middleware and HTTP APIs | Server requests |
| Add translations and locale-aware formatting | Internationalization |
| Write labels, feedback, errors, notifications, and Help | Product language and tone |