SupaScale Terms of Service & Supabase Docker Capacity Disclaimer
Last updated on SupaScale: 2026-11-12
| Publisher | SupaScale Editorial Desk |
|---|---|
| Registered Details | Independent Digital Infrastructure Publication |
| License of Estimates | Provided "AS IS" for Engineering Capacity Planning |
| Rate Snapshot Warning | Retrieved 2026-11-12 — Always Verify Live Checkout Terms |
1. "As-Is" Engineering Nature of SupaScale Supabase Docker Estimates
All 12-container memory equations, PostgreSQL shared_buffers recommendations, pgvector HNSW formulas, and docker-compose.override.yml configurations published on SupaScale by SupaScale Editorial Desk are provided strictly "AS IS" for capacity-planning guidance.
Actual production RAM and NVMe IOPS depend on your schema width, Row-Level Security (RLS) policy joins, concurrent ImgProxy image dimensions, and Linux kernel sysctl settings. Always validate WAL-G and pg_dumpall restores on staging hardware before production cutover.
2. Upstream Hosting & Supabase Cloud Pricing Changes Cited on SupaScale
Public vendor prices and Supabase Cloud overage rates cited on SupaScale reflect public pricing pages retrieved on 2026-11-12. Promotional introductory discounts, multi-year billing commitments, free credit durations, and renewal rates change frequently—you must verify exact final pricing and SLA terms on the vendor checkout page before purchasing.
3. Operator Security Responsibility & Limitation of Liability on SupaScale
Servers deployed through outbound links belong 100% to your own hosting account. You remain solely responsible for firewalling PostgreSQL port 5432, rotating JWT_SECRET and service_role credentials, and maintaining encrypted off-host backups. Neither SupaScale nor SupaScale Editorial Desk (Independent Digital Infrastructure Publication) is liable for upstream downtime, data loss, or vendor billing disputes.