SaaS resilience

Keep your team moving when Jira or Confluence goes down.

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.

25,000+ organizations trust Rewind with their data
The stakes

Outages happen to every platform, Atlassian’s included.

They’re outside everyone’s control. A damaging bulk change or a broken configuration can stop work too, even while the site stays up.

01

60% of organizations experienced at least one Jira outage in the past year.

02

73% of organizations report that Jira outages directly impact delivery timelines.

03

90% report productivity loss from Jira outages; 77.4% from Confluence outages.

Source: Rewind SaaS Resilience Report, Q4 2025. Based on a Q4 2025 survey of IT, Cloud Ops, and Engineering leaders at companies with 500-10,000+ employees.
What you get

Failover-ready capabilities that start with your daily backup.

A daily backup of Jira and Confluence

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.

Pilot Light for Jira and Confluence

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.

Hot Standby for Jira

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.

The capabilities

Each one fits a different situation.

Pilot Light for Jira and Confluence

Your latest work, open during an outage

What it is

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.

When it applies

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.

How to start

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 Jira work item open in Pilot Light for Jira
Hot Standby for Jira

A second Jira site your team can move to

What it is

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.

When it applies

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.

How to start

Rewind guides the setup with you and runs checks on your site before the first sync.

Reviewing a Hot Standby setup before the first sync
Which applies when

Match the response to the incident.

The situation
What applies

A few work items, pages, or a space were changed or deleted

Restore from the Rewind backup

An Atlassian outage, and people need what’s in Jira or Confluence to keep working

Pilot Light for Jira and Confluence

The main Jira site is lost, can’t be trusted, or its region is down for an extended period

Hot Standby for Jira

A migration or a big bulk change is coming up in Jira

Back up on demand first, then sync Hot Standby

Get failover-ready for Jira and Confluence.

Frequently Asked Questions

Questions teams ask before they set these up

Which plans include Pilot Light for Jira and Confluence, and Hot Standby for Jira?
Both are included in the Advanced plan. Hot Standby is for Jira, and Pilot Light covers Jira and Confluence. Backup and restore are in every plan.
No. Hot Standby is included in the Advanced plan, and Rewind doesn’t charge extra for the standby. It’s a second Jira site in your Atlassian organization, so depending on your Jira plan, Atlassian license fees may apply.
If Atlassian is down everywhere, or the outage is short, use Pilot Light for Jira and Confluence. People keep working from the latest backup of Jira or Confluence while Atlassian restores service, and nothing has to be moved back. 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. Data copies one way, from the main site to the standby, so work done on the standby has to be reconciled afterward. That’s why a short outage calls for Pilot Light.
No. Switching to Hot Standby is a deliberate decision your team makes, and it follows set steps.
Rewind Labs Preview is where we release capabilities that are tested and working while we keep adding to them and scaling them. Open means everyone on the plan can turn it on. While Pilot Light for Jira and Confluence is in the preview, it has usage limits as we validate it at scale: up to 3 backup configurations, with up to 25 people activated on each, so up to 75 people in total. There’s no limit on the number of Confluence spaces. Start with your most important content.