Junban Desk comes in three editions. They share the same “needs action” queue and agent workspace and behave almost identically in day-to-day use — the differences are in how you run it, who hosts it, and where your data sits. Each edition has its own privacy policy; they are not interchangeable, so use the one for the edition you actually run.
| Open source (Forge) | Marketplace (Forge) | Cloud (hosted) | |
|---|---|---|---|
| How it runs | You deploy it into your own Jira site with Atlassian Forge | Installed from the Atlassian Marketplace; managed Forge app in your site | Hosted web app at app.junbandesk.com |
| Runs inside Atlassian | Yes — your tenant | Yes — your tenant | No — hosted on Cloudflare |
| Source | Open source | Closed source | Closed source |
| Price | Free (self-hosted) | Paid | See site |
| How you get it | GitHub | Atlassian Marketplace (coming soon) | Sign in at app.junbandesk.com |
| Updates | You redeploy | Managed by us | Managed by us |
| Privacy policy | OSS policy | this site | app.junbandesk.com/privacy |
Everything in the user guide applies to all three editions unless a note says otherwise.
The free, self-deploy edition. You install it into your own Jira site as an Atlassian Forge app, so it runs entirely inside your Atlassian tenant — nothing is hosted by us and no data leaves your Atlassian account. You manage the deployment and its updates yourself.
The managed, paid edition on the Atlassian Marketplace. Same in-tenant Forge model — it runs inside your Atlassian site and stores no data outside it — with a managed release and updates, and commercial support from Collaboration Services.
The hosted service at app.junbandesk.com. No install: you sign in with your Atlassian account over OAuth 2.0 (3LO), and every Jira request runs under your own token and your own Jira permissions. It runs on our infrastructure (Cloudflare) rather than inside Atlassian, which is why it has its own privacy boundary and its own privacy page. It also supports classic JSM and Customer Service Management projects.
Your edition determines your privacy policy — they are not shared:
The two Forge editions (Open source and Marketplace) keep all data inside your Atlassian tenant. The Cloud edition additionally holds your session server-side while you are logged in, and deletes it when you log out — its privacy page covers exactly what that means.
Only the open-source edition has a public repository. The Marketplace and Cloud editions are closed source; these docs link the open-source repo and each edition’s own privacy page, never a private repository.