ON YOUR COMPUTER
Local
For developers who need Papliba processing on their own machine.
- Processing & saved workspace
- Developer’s computer
- Identity
- Local CLI connections
- Operated by
- You
Release archives through your administrator
Read the Local guideCHOOSE YOUR EDITION
Same workspace. Your choice of home.
The runner is the backend that connects to Azure and processes your requests. Its location is the important difference between the three editions.
IN YOUR ORGANIZATION
Self-hosted
For organizations that want to operate their own Papliba server.
- Processing & saved workspace
- Customer-operated server
- Identity
- Your organization’s Entra tenant
- Operated by
- Your organization
Deployment package; administrator setup required
Read the Self-hosted guideMANAGED HOSTING
Cloud
For browser access with the backend operated in Papliba’s Azure environment.
- Processing & saved workspace
- Papliba-operated server
- Identity
- Approved Entra tenants
- Operated by
- Papliba
Managed access is not open yet
Read the Cloud guideSTART WITH YOUR DATA REQUIREMENT
Where can your Azure information be processed?
“Only on my laptop.”
Choose Local. The runner and saved workspace stay on that computer. Azure and GitHub still receive API requests; optional AI can send prompts externally.
“On our company’s server.”
Choose Self-hosted. Your organization operates identity setup, the backend, database, encryption keys, upgrades, and backups.
“On the product provider’s server.”
Cloud can fit that requirement once available. It processes Azure results and stores workspace data on Papliba’s infrastructure.
Private workspaces in this release
Hosted workspaces belong to individual users. Shared organization workspaces, invitations, self-service billing, and multiple application replicas are not implemented.