“Supabase is probably the strongest match for what you're describing.”
“Native PostgreSQL Row-Level Security.”
“Integrated authentication.”
“JWT claims accessible inside RLS policies.”
“Automatically generated REST and GraphQL APIs.”
“Storage permissions integrated with database RLS.”
“Realtime and Edge Functions.”
“It combines PostgreSQL-native RLS, authentication, APIs, storage, and realtime functionality without requiring you to assemble several independent services.”
“Firebase | Firestore security rules, not PostgreSQL RLS”
“Firebase | Firestore security rules, not PostgreSQL RLS”
“Appwrite | Uses its own permission system”
“Appwrite | Uses its own permission system”
“Convex | Authorization through application functions”
“Convex | Authorization through application functions”
“Authentication.”
“Managed PostgreSQL.”
“Hasura-powered GraphQL API.”
“Storage.”
“Serverless functions.”
“Realtime subscriptions.”
“One important distinction: Nhost primarily uses Hasura's permissions system for authorization. This is not equivalent to Supabase's native PostgreSQL RLS approach.”
“AWS Amplify | Primarily AWS-managed data and authorization services”
“AWS Amplify | Primarily AWS-managed data and authorization services”
“Hasura | Primarily API-level permissions, not native PostgreSQL RLS”
“Hasura | Primarily API-level permissions, not native PostgreSQL RLS”
“Neon provides serverless PostgreSQL with native PostgreSQL RLS support.”
“Native PostgreSQL policies.”
“Database branching.”
“Autoscaling and scale-to-zero.”
“Neon Auth integration.”
“Data API for HTTP-based database access.”
“The main difference: Neon is more database-centric than Supabase. You may need to assemble more of your backend infrastructure yourself.”