Managed database
ContainerHub operational data lives in PostgreSQL managed by Supabase, not in local files or self-hosted servers.
Back to ContainerHub
Security, availability, and recovery
Where your data lives and how it is protected
ContainerHub stores operational data in a Supabase-managed PostgreSQL database. Supabase documents that projects are deployed in AWS regions, with controls such as backups, Point-in-Time Recovery, encryption, and access policies.
The right promise is not that data loss is impossible. The professional promise is serious infrastructure, access controls, data exportability, and a measurable recovery plan.
Cloud infrastructure
Supabase deploys projects in AWS regions, a cloud provider used globally for critical workloads.
Company-level separation
ContainerHub structures information by tenant/company and applies access controls so each user sees only what they should.
Data exports
Inventory, reports, and operations can be exported in open formats such as CSV, XLSX, and PDF so customers can keep their own copies.
Card payments (PCI)
Subscription payments are processed by Stripe (PCI DSS Level 1). ContainerHub does not store full card numbers; checkout uses Stripe-hosted pages over HTTPS.
What we would tell a customer
ContainerHub data does not live on a laptop or an improvised server. It lives in a Supabase-managed PostgreSQL database, on AWS cloud infrastructure, with security and recovery measures documented by the provider.
Short answer
“Your information is stored in Supabase PostgreSQL, deployed on AWS. It is not kept in loose files or self-managed servers. We also use access controls, backups, exports, and recovery processes.”
Honest answer
“No serious provider promises absolute zero risk. What matters is reducing risk through managed infrastructure, recovery, traceability, permissions, and exportable copies.”
Backups and recovery
Supabase documents daily backups for paid projects and Point-in-Time Recovery as an add-on for restoring the database to a specific moment. Exact retention depends on the plan and active configuration.
Database
Primary restoration happens in PostgreSQL: tables, rows, relationships, and application metadata.
Customer exports
Downloadable reports let customers keep copies of critical information outside the platform.
Files and photos
Supabase clarifies that database backups do not automatically restore deleted Storage objects. Files need a specific backup policy.
Official Supabase documentation
These are the public links we recommend when a customer asks for technical evidence about infrastructure, backups, security, and availability.
Infrastructure regions
Supabase documents that projects are deployed in AWS regions.
Database backups
Daily backups by plan, restore process, and Point-in-Time Recovery.
Security at Supabase
Encryption, certifications, backups, and Supabase security practices.
Supabase SLA
Availability commitments, support, and service credits.
Supabase Status
Public service status, uptime history, and incidents by service and region.
Compute and Disk
Each Supabase Platform project has its own Postgres instance.
Row Level Security
Granular row-level authorization model in PostgreSQL.
Storage Access Control
Access policies for objects, buckets, and files in Supabase Storage.
What we can formalize for Enterprise customers
For operations that need stronger contractual certainty, ContainerHub can turn this posture into measurable commitments: RPO, RTO, retention, restore drills, and external file backups.
Defined RPO and RTO
Encrypted external backups
Periodic restore drill
Files and photos policy