Stack: Jira Software
Okta disaster recovery for Jira and Atlassian admins
Jira federated through Okta — typically via the Atlassian Access SSO product — means project tracking, sprint planning, and incident ticketing all sit behind the Okta authentication policy. A single bad policy push can knock engineering out of Jira at the worst possible moment.
Butterfly captures versioned snapshots of the Okta configuration governing Jira and Atlassian Cloud access — the SAML or OIDC app, the SCIM feed, assigned groups, sign-on policies, and Workflows automations. Restore preview shows the diff before any revert.
What you get
How Butterfly fits Jira Software
Atlassian SSO app is versioned
Every backup captures the Okta-side Atlassian Cloud app integration — SAML signing certificate, attribute mapping, assigned groups, and sign-on policy.
SCIM provisioning to Atlassian organization
The Okta-to-Atlassian SCIM connection is part of every snapshot. Group-to-Atlassian-organization mapping, attribute mapping, and the assignment population are captured.
Group rules drive Jira product access
Group rules are how most teams scale who-can-access-which-Jira-project. Butterfly versions every rule.
What goes wrong
Three incidents you have already seen variations of
Sign-on policy change blocks engineering mid-sprint
A device-trust tightening caught the engineering group expression. The team could not reach Jira during a sprint demo. Restore preview surfaces the policy diff.
SCIM-driven license downgrade strips access to Jira Software
A SCIM attribute mapping change moved a population to an Atlassian license tier that did not include Jira Software access. Restore preview surfaces the mapping diff.
Group rule cleanup drops a customer-success org from Jira Service Management
A directory cleanup removed the group rule feeding the CS-jsm-agents group. Service tickets piled up. Restore preview restores the rule.
Honest scope
What Butterfly captures — and what it does not
In scope
The Okta-side configuration governing Jira and Atlassian Cloud access: the Atlassian SAML / OIDC app integration, attribute mappings, SCIM provisioning configuration, assigned users and groups, group rules driving Atlassian product access, sign-on policies, and Workflows automations.
Out of scope
We do not back up Jira tickets, project configuration, Confluence pages, or any Atlassian-side state. Atlassian-side backup is owned by Atlassian's own export tooling or third-party tools purpose-built for that surface.
Plans
Free, Standard, or Business
Free
$0 / forever
- 1 Okta connection
- 7-day retention
- 1 total backup
- No credit card
Standard
$1 / user / month — $99 minimum
- 2 Okta connections
- 90-day retention
- Restore preview + dry-run
- Audit Pack PDF (framework-filterable)
Business
$2 / user / month — $299 minimum
- Unlimited Okta connections
- Unlimited retention
- Continuity (warm standby)
- Priority restore support
Pricing reference: /upgrade. Provider coverage today: Okta, Okta Workflows, Auth0.
Regulatory shape
Compliance and audit angle
SOC 2 CC6 (logical access) and ISO 27001 A.5.16 (identity management) apply most directly to engineering-tooling identity continuity.
Butterfly's own SOC 2 Type II work is in progress; current status lives in the Trust Center.
Frequently asked
FAQ
Does Butterfly back up Jira tickets or Confluence pages?
No. Butterfly backs up the Okta configuration governing Jira / Atlassian Cloud access. Atlassian-side data backup is a different category.
Does this cover Jira Service Management as well?
Yes. The Okta-side configuration covers all Atlassian Cloud products gated by the same SSO app.
Can we restore a single group rule without touching others?
Yes. Restore preview lets you pick the scope before committing.
Recover your Okta org in minutes, not hours
Talk to Mick (the founder) for a 30-minute demo, or start the free trial. No credit card for the free tier.
More stacks
Okta DR for other stacks
Trust posture, subprocessors, and security details: Trust Center.