Supabase 评估：需要一体化 PostgreSQL 后端时的强选项

Supabase combines multiple services around a project database. It does not remove responsibility for PostgreSQL design, row-level security, authorization, connection behavior, backups, quotas, egress, and product-specific limits.¹²³

适用范围： Web and mobile teams that want PostgreSQL plus integrated backend services and are prepared to own schema and access-policy design

• The product wants independent lifecycle and vendor boundaries for database, auth, and storage.
• The team cannot safely design and test row-level security for client data access.
• Required regions, extensions, connection behavior, backups, or quotas do not fit the service.

• Full PostgreSQL databaseEach project uses PostgreSQL rather than a proprietary database abstraction.¹
• Integrated servicesAuth, Storage, Realtime, Functions, and APIs are designed around the project database.²³⁴
• Row-level security modelPostgreSQL policies can govern direct client data access when designed correctly.²
• Shared platform contextRealtime, storage policies, generated APIs, logs, and other services share the project boundary.³⁴

Plans combine organization or project packaging with product-specific included usage and overages across compute, database disk, egress, Auth users, Storage, Realtime, and Functions.⁵

Compute

Project compute is billed by size; current paid packaging includes compute credit⁵

Cost shape

Plan plus active projects, compute, database, egress, storage, Auth usage, Realtime, Functions, and add-ons⁵

Architecture boundary

Auth, Storage, Realtime, and APIs share the PostgreSQL-centered project context⁵