Storage Deployment Model
1. Revyz-Managed Storage
Customer data is stored in Revyz's AWS account and stored in our supported AWS data centers. More information about our supported AWS data centers is available here. You can learn more about our encryption methodology here.
Data Stored in Revyz’s AWS Account
Data Flow:
Authentication & Access: After installing the Revyz app on your Jira/Confluence site, Atlassian creates a unique dedicated user that enables the app to access your Atlassian environment data (as identified in the image above as 1 ) The created user is unique to the app and the site.
Data Collection: Using unique tenant-isolated compute infrastructure, Revyz leverages this Atlassian-created user to securely retrieve data and metadata from your site via TLS 1.2 encrypted connection
Data includes Jira projects, issues, comments, attachments, Confluence spaces, pages, blogs, comments, attachments and associated configuration objects
Data Storage: Data retrieved is encrypted, and stored in Revyz's AWS S3 storage
Encryption of the data is on a per customer basis with separate and unique encryption keys for each customer / tenant
All backup data maintained within Revyz's secured infrastructure is stored in an encrypted manner at rest and data is always encrypted in-motion
2. Customer-Managed Storage (BYOS)
Customer data is stored in the Customer's Own Public Cloud Storage Account. As of Q2 2025, Revyz supports AWS and Azure public clouds for storing backup data.
Data Stored in Customer Specified Public Cloud Storage
Data Flow:
Authentication & Access: After installing the Revyz app on your Jira/Confluence site, Atlassian creates a unique dedicated user that enables the app to access your Atlassian environment data (as identified in the image above as 1 ) The created user is unique to the app and the site.
Data Collection: Using unique tenant-isolated compute infrastructure, Revyz leverages this Atlassian-created user to securely retrieve data and metadata from your site via TLS 1.2 encrypted connection
Data includes Jira projects, issues, comments, attachments, Confluence spaces, pages, blogs, comments, attachments and associated configuration objects
Direct Transfer: All retrieved data is transferred directly without any staging of the retrieved data to your own cloud storage account using a Revyz user (as identified in the image above as 2 )with limited permissions to read & write to your storage
Storage: Data resides exclusively in your public cloud environment (AWS S3 or Azure Blob Storage), maintaining your full control and ownership
Metadata Management: Revyz retains only app specific metadata about backup states and configurations to facilitate future backup or restore UI operations
Notes
Revyz is built on public cloud infrastructure provided by AWS, which is considered as a sub-processor for Revyz
Revyz does not use any other third party sub-processor (besides AWS) for any data operations such as data staging, processing, transformation & egress
The data may be momentarily held in the customer specific unique isolated compute instances’s memory before it is moved to its final destination
Data in motion is encrypted using TLS, Atlassian mandates a minimum of TLS 1.2
it is the customers responsibility to ensure that data is encrypted at rest. Most public cloud providers enable encryption of data at rest by default.
Details on Revyz policies for encryption available here
Reference: Amazon S3 Encrypts New Objects By Default
Reference: Azure Storage Encryption for Data at rest
Revyz Apps supporting Customer Managed Storage / Bring Your Own Storage (BYOS)
You can find all the Revyz apps here