Web application overview
Connect an independently deployed PC web application so customers can open it from Console. You own its build, deployment, authentication, and maintenance; integration requires no changes to Console or another application's source code.
Choose an opening mode
| Mode | Customer experience | Requirements |
|---|---|---|
| Redirect (default) | Use the application on its own page | Configure the existing HTTPS application URL |
| Isolated iframe | Use the application inside the Console workspace | Adapt to the public container protocol; recommended for third-party embedding |
| Trusted qiankun mount | Mount the business interface directly in the workspace | Adapt the public lifecycle; obtain independent security approval and explicitly publish |
Both embedded modes retain the independent URL, with retry and open-in-new-window recovery. An iframe provides cross-origin isolation. Directly mounted code shares the host page's permissions; the qiankun sandbox is not a third-party security boundary.
Follow the steps for each opening mode. Embedding your application in Console and embedding a platform commercial page inside your application are separate directions. Subscription integration also requires checkout and return handling.
Integration scope
The current scope is PC browsers. Mobile SDKs, mini-program packages, and a dedicated client are not required. Embedded applications must implement the public Manifest, container SDK, and qiankun lifecycle. A plain web URL can use redirect mode.
Integration workflow
- Create an application in the developer console, starting with Sandbox. See create and test an application.
- Under “Application management → Application listing”, configure the independent URL and opening mode. Embedded modes also require a public Manifest.
- Save the draft, wait for automatic artifact checks, then complete development testing in a real PC browser.
- Prepare separate Production configuration, create a version, submit for review, and explicitly publish the approved version.
Saving, checking, review, and publication have separate results. A new draft preserves the currently published customer version.
Add capabilities when needed
| Need | Documentation |
|---|---|
| Sign-in and customer spaces | Authentication, users and customer spaces |
| Security, credentials, and collaborators | Application security, application management |
| APIs and events | API products, event integration |
| Plans, subscriptions, and payments | Third-party SaaS subscriptions and payments |
Application visibility, sign-in, API permissions, and paid entitlements are configured and verified separately. Embedding grants none of these capabilities automatically.