Security, Trust & Atlassian Programs: Release Management, Roadmaps & Product Portfolio
Key Takeaways
Release Management, Roadmaps & Product Portfolio for Jira stores your scope, forecasts, capacity models, and pending changes inside your own Atlassian tenant, unlike most Marketplace release and roadmap apps, which are Connect apps that copy Jira data to vendor-operated servers.
As a Runs on Atlassian Forge app, it makes no outbound calls to Divim or any third party: no analytics SDK, no external error reporter, and no vendor-side copy of your roadmap.
All compute and storage run on Atlassian Forge (Forge SQL and KVS), inheriting Atlassian's SOC 2, ISO 27001, and tenant-isolation posture, with stored data following the data-residency region of your host Jira Cloud site.
The app carries both the Runs on Atlassian and Cloud Fortified designations, uses Atlassian-managed authentication with no vendor-held credentials, has no third-party subprocessors, and acknowledges vulnerability reports within five business days.
It pairs that trust posture with enterprise forecasting: probabilistic p50/p85/p95 dates from Monte Carlo over real Jira throughput, multi-team capacity blending, portfolio roll-ups, WSJF/RICE/MoSCoW prioritization, and a critical-path view, all without data leaving Atlassian.
The shortest security review you'll run this quarter. Most release-management and roadmap apps on the Marketplace are Connect apps that copy your Jira data to vendor-operated servers. Release Management, Roadmaps & Product Portfolio never does. Your scope, forecasts, capacity models, and pending changes are stored inside your own Atlassian tenant, so the answer to "where does our data go?" is simply: it doesn't leave.
▶ Try it free on the Atlassian Marketplace · Read the Divim Trust Center →
What "Runs on Atlassian" means for your buyers
No data egress. The app makes no outbound calls to Divim or any third party. There is no analytics SDK, no external error reporter, and no vendor-side copy of your roadmap.
Atlassian-hosted, end to end. All compute and storage run on Atlassian Forge (Forge SQL + KVS), inheriting Atlassian's SOC 2, ISO 27001 and tenant-isolation posture.
Your data residency, honored. Stored data follows the data-residency region of your host Jira Cloud site automatically.
Procurement-ready. A single badge answers the questions security teams ask first (hosting, egress, and residency) and shortens the path from trial to rollout.
Trust at a glance
Attribute | Release Management, Roadmaps & Product Portfolio |
|---|---|
Atlassian programs | Runs on Atlassian (auto-verified Forge app) · Cloud Fortified |
Platform | Atlassian Forge, fully serverless |
Customer data sent to Divim | None |
Third-party subprocessors | None (Atlassian is the sole infrastructure provider) |
Data residency | Follows your Jira Cloud site |
Encryption | TLS in transit · encrypted at rest (Atlassian-managed) |
Authentication | Managed by Atlassian, no vendor-held credentials |
Vulnerability response | Acknowledged within 5 business days |
Why enterprise teams choose it with confidence
Release Management, Roadmaps & Product Portfolio pairs an enterprise-grade trust story with an enterprise-grade forecasting story: probabilistic p50/p85/p95 release dates from Monte Carlo over your real Jira throughput, multi-team capacity blending, portfolio roll-ups and living roadmaps, WSJF/RICE/MoSCoW prioritization, and a critical-path view, all computed without a single byte of your data leaving Atlassian.
Documentation & resources
Divim Trust Center: company-wide security, privacy & compliance
Security Policy · Data Security & Privacy Statement · User Guide
Trust-program participation verified on the Atlassian Marketplace. Reviewed at least annually. Security questions: support@divim.io.