Being failover-ready means your team isn’t forced to scramble when a platform fails. Rewind starts with a daily backup of Jira and Confluence, then adds predefined options that keep your team working while the incident is resolved.








They’re outside everyone’s control. A damaging bulk change or a broken configuration can stop work too, even while the site stays up.
Rewind backs up Jira and Confluence every day. When something is changed or deleted, you restore exactly what was affected, from a single page or work item to a whole space.
During an Atlassian outage, Pilot Light opens your latest backup in a web portal that runs separately from Atlassian. Your team can still get to what’s in Jira and Confluence and keep working.
A second Jira site in a different region, kept in sync after every daily backup. Your team can switch to it when your main site is lost, can’t be trusted, or its region is down for an extended period. Hot Standby can help you achieve a recovery time (RTO) of under 6 hours.
Read-only access to your latest Rewind backup, in a web portal that runs separately from Atlassian. In Jira, people open the work items they need, with descriptions, comments, and history. In Confluence, they browse spaces and pages in their usual hierarchy and open attachments. Each person sees the spaces mapped to their Atlassian groups.
During an Atlassian outage, when people can’t reach Jira or Confluence. Your team keeps working from what’s in Jira and Confluence while Atlassian restores service, and nothing has to be moved back afterward.
Turn it on yourself in the Rewind app. Set up your backup configurations first, then link one in Pilot Light and activate the people who can use it. Start with your most important content: the spaces and people your team would need first during an outage.
The backup configuration that Pilot Light for Confluence works from, with the spaces it covers
A second Jira site in your Atlassian organization, set up in a different region from your main site. Rewind syncs it with your main site after every daily backup, and you can sync it on demand, for example before a migration or a big bulk change. It holds the previous day’s data, so the recovery point is about 24 hours. Hot Standby can help you achieve a recovery time (RTO) of under 6 hours.
What syncs: Spaces, work items with their attachments and comments, fields, boards, sprints, workflows, statuses, and permission schemes.
Hot Standby for Jira is for when your main Jira site is lost, can’t be trusted, or its region is down for an extended period. The standby site sits in a different region, and switching to it is a deliberate team decision. For an Atlassian-wide outage, or a short one, Pilot Light is the answer.
Rewind guides the setup with you and runs checks on your site before the first sync.
A few work items, pages, or a space were changed or deleted
An Atlassian outage, and people need what’s in Jira or Confluence to keep working
The main Jira site is lost, can’t be trusted, or its region is down for an extended period
A migration or a big bulk change is coming up in Jira