Understand Cloud access

Current availability

Managed Cloud access is not open yet. This public product website is available without signing in, but it is not a hosted Papliba workspace. Cloud provisioning and production acceptance are still in progress. There is no self-service registration or billing in this release.

How Cloud works

The application backend and PostgreSQL run in Papliba’s Azure environment. Approved Microsoft Entra tenants can be admitted by an operator. Each signed-in user has a private workspace. A browser is sufficient; a local runner is not required.

Signing in establishes your application identity. Connect Azure separately requests delegated access to Azure Resource Manager. Papliba’s server uses that token to query the resources your identity can read, and processes those responses. Hosted Azure results and saved workspace data therefore reach the Papliba server.

Connection and workspace limits

• Reconnect Azure when the delegated token expires; background token renewal is not implemented.
• Hosted inventory never falls back to the server owner’s Azure CLI session.
• Shared workspaces, invitations, billing, and unattended workflow execution are not available.
• Local workspace data is not automatically uploaded to Cloud.

Choose according to your data requirement

If your organization requires Papliba processing to remain on the developer’s computer, use Local. If processing can happen on a company-operated server, consider Self-hosted. Cloud requires approval to process that data on Papliba’s infrastructure.