Build applications with Cloudgate
On this page
Cloudgate web apps combine an interface with workflow APIs and shared identity services. Choose visual widgets or application source according to the interaction you need to build.
Choose an authoring mode#
| Mode | Good fit |
|---|---|
| Visual Builder | Operational dashboards, forms, lists, and API-backed internal tools |
| Code Editor | Custom layouts, routing, components, and source-based development |
| App Store / templates | Starting from an established application or reusable design |
Open Web Apps → Web Apps to manage the selected application. Visual-builder pages and components belong to a specific app; open that app's builder from the app list.
Define the API contract first#
For each page, list the data it reads and the actions it can perform. Confirm request methods, required fields, identifiers, response wrappers, and denied-access behavior.
Build one complete path before adding many screens: load a record, display it, handle an empty result, and show a useful error. For write interactions, validate on the server even if the form also validates locally.
Use shared services deliberately#
Apps can use IdP users and roles, notifications, files, and other tenant services. Some settings apply across apps, including identity and email configuration. Check that scope before changing a shared setting for one app.
Operate the app#
Use Dashboard and Analysis to inspect traffic and app activity. Use workflow logs for the API calls behind the page. App metrics and gateway metrics answer different questions: a page visit is not the same as a successful business operation.
App releases have their own review and rollback lifecycle. Workflow dependencies must be compatible with the app version you publish.
Continue with the Visual Builder, Code Editor, or first-app guide.
Need to investigate a problem? Start with troubleshooting
