Backups, recovery and business continuity
Your property records matter beyond today.
Property information builds up over years. Tenancy histories, compliance records, documents and portfolio information need to remain organised and protected as your business grows.
Fructus combines managed infrastructure, database backups, separate document backup arrangements and operational checks to support the continuity of the service.
Last reviewed: 11 October 2026
Different protections, each with its own job.
Application source code, database records, primary document storage and separate document backups are different things, protected in different ways. This page explains each one, what it helps with and where its limits are, so you can understand the arrangements behind the service.
Built on established infrastructure
Fructus is built from a small number of established services, each with a distinct role.
- Replit hosts the production application.
- Supabase provides the production database, authentication and primary document storage.
- GitHub provides version-controlled application source and automated operational workflows.
- Cloudflare R2 provides separate backup storage for covered documents.
- Using several services gives us different operational capabilities. It does not mean automatic failover or uninterrupted availability.
Database backups
Fructus uses provider-managed database backups to help protect the records behind your portfolio. These backups form part of our recovery arrangements alongside separate protection for supported document files.
Our production database is backed up daily by Supabase, with restoration controls available. Database backups cover the records held in the database, such as property, tenancy and compliance details. Uploaded file contents are stored separately and are not included in these database backups. Separate backups for covered files are described below.
Separate document backups
Your primary documents are stored in Supabase Storage. In addition, a scheduled backup process copies covered ordinary uploaded documents and organisation logos to separate backup storage on Cloudflare R2.
The process runs through GitHub Actions, uses integrity checks on copied files, and keeps backup records and manifests. It has a record of successful scheduled operation. Not every uploaded file is covered: restricted tenancy evidence, for example, is held under its separate access arrangements and is not part of this backup process.
Application source and deployment recovery
Fructus application code is kept under version control, and our deployment infrastructure supports maintaining and restoring application versions.
Source code history is different from database or document backups. Returning to an earlier version of the application does not restore data, and it is not automatically compatible with every later database change.
Operational health checks
Fructus runs scheduled production readiness checks, including authenticated application checks. Backup health reporting and alert logic help identify operational issues.
Scheduled checks help us identify potential service or backup issues.
Planning for disruption
Fructus relies on the combination of managed infrastructure, backups, operational records and recovery capabilities to support the resilience of the service.
Recovery depends on the type and extent of an incident and the information available from the relevant backups.
Access to your records
Authorised users can download documents from Fructus and use selected reporting and export capabilities in the application. If you have questions about access to your information or service continuity, please contact us. Personal data is covered by our Privacy Policy and contractual arrangements by our Customer Terms.
Backups and recovery, answered.
Does Fructus back up its database?
Yes. Fructus uses Supabase-managed production database backups, which run daily, with restoration controls available. These backups cover database records; uploaded files are protected separately.
Are my uploaded documents backed up separately?
Covered documents are. Primary documents are stored in Supabase Storage, and a separate scheduled process copies ordinary uploaded documents and organisation logos to Cloudflare R2, using integrity checks and backup records. Not every file is included: restricted tenancy evidence is not part of this separate backup process.
Where are Fructus document backups stored?
Primary documents are held in Supabase Storage, and the production Supabase project is hosted in the London region. Separate backup copies of covered documents are stored in Cloudflare R2. We do not currently state a specific geographic location for the R2 backup copies.
Is the application source code backed up?
Fructus application source is version-controlled in GitHub, and our deployment infrastructure supports maintaining and restoring application versions. Source code history is separate from database and document backups and does not restore customer data.
How does Fructus check that its service is working?
Fructus runs scheduled production readiness checks, including authenticated application checks, and uses backup health reporting and alert logic. Scheduled checks help us identify potential service or backup issues.
What happens if Fructus experiences an outage?
We would work to restore the service using our managed infrastructure, database backups, separate document backups, version-controlled application source and operational records. How recovery proceeds depends on the type and extent of the incident, so we do not promise specific recovery times or uninterrupted availability.
Can I download or export my information?
Authorised users can download documents and use selected reporting and export capabilities in Fructus. There is not currently a single complete organisation export package. If you have questions about access to your information, please contact us.
Property management built for the long term.
Keep your portfolio information organised in one place, with practical backup and operational arrangements supporting the service behind it.
Want to know how your information is protected? Read about security at Fructus
This page is informative and does not form part of your contract with Fructus. Binding terms are set out in our Customer Terms and Privacy Policy.
Last reviewed: 11 October 2026