Every Supabase product and feature, marked as supported, different on SupaHost, or not available. Covers the database, Data API, Auth, Storage, Realtime, Edge Functions, cron, CLI and platform.
SupaHost runs the open-source Supabase stack, so most features work exactly as they do on Supabase Cloud. Some work differently because of how SupaHost is built, and a few aren't available. This page lists them product by product.
How to read the tables:
Supported: works as in open-source Supabase. Your existing code and SQL should run unchanged.
Different: available, but set up or limited differently on SupaHost. The note says how.
Not available: not offered today.
Database
Feature
Status
Notes
Postgres 17
Supported
One database per project on a shared Postgres server per instance.
Extensions
Supported
Whatever the supabase/postgres image ships. Check with select * from pg_available_extensions.
pg_cron
Different
Built into every project. Don't run create extension pg_cron; it fails. See Cron.
Database webhooks and pg_net
Supported
pg_net and the supabase_functions schema are installed in every project.
Vault
Supported
Supabase Studio
Different
One Studio per project, opened by the owner from the dashboard. Starts on first visit (about 20 s).
Studio Logs and Reports pages
Not available
Direct Postgres connections
Different
Business and Enterprise only, through a restricted SSH tunnel. Other plans use the Data API, Studio, MCP or exports.
Connection pooler (Supavisor)
Not available
Read replicas
Not available
Daily backups
Supported
Kept 7 days (Builder, Pro) or 14 days (Business). Cover databases, not Storage files.
Point-in-time recovery
Different
Included on Pro (7 days) and Business (14 days), not on Builder.
Restore one project
Supported
Restores never touch other projects. The previous database is kept for 3 days.
Database export (pg_dump)
Supported
One click on the Backups tab.
Disk size
Different
No compute or disk add-ons to pick. The disk grows automatically.
Database advisors
Different
MCP get_advisors runs three checks: RLS disabled, RLS without policies, mutable function search path.
Data API and keys
Feature
Status
Notes
REST API (PostgREST)
Supported
Max 1000 rows per request.
Exposed schemas
Different
Fixed to public, storage, graphql_public and pgmq_public. Can't be changed.
GraphQL (pg_graphql over HTTP)
Not available
There's no /graphql/v1 endpoint.
anon and service_role keys
Supported
Legacy HS256 JWT keys, on the Connect tab.
Publishable and secret keys (sb_publishable_, sb_secret_)
Not available
Asymmetric JWT signing keys
Not available
Tokens are signed with the project's JWT secret (HS256).
Key or JWT secret rotation
Not available
TypeScript type generation
Supported
MCP generate_typescript_types, or the Supabase CLI against a local database.
Custom domains
Supported
With automatic HTTPS. 1, 3 or 10 included depending on plan.
Auth
Feature
Status
Notes
Email and password
Supported
Minimum password length is configurable (6 to 72).
Magic links and email OTP
Supported
OAuth providers
Supported
19 providers, including Google, GitHub, Apple, Microsoft, GitLab, Discord, Slack, LinkedIn, Keycloak and WorkOS.
Anonymous sign-ins
Supported
Toggle on the Auth tab.
TOTP multi-factor auth
Supported
Phone, SMS and WhatsApp sign-in
Not available
Phone MFA
Not available
Custom SMTP
Not available
Emails are sent by SupaHost from [email protected], with your App name as the sender name.
Email templates
Different
Five templates with editable subject, heading, message and button text.
Site URL and redirect URLs
Supported
Wildcards allowed. URLs must start with http:// or https://.
Manual identity linking
Supported
Toggle on the Auth tab.
Disable sign-ups, skip email confirmation
Supported
Toggles on the Auth tab.
Access token lifetime
Supported
300 s to 7 days.
Rate limits
Different
Email sending is capped at 30; other limits use Auth's defaults and can't be changed.
Admin API (auth.admin.*)
Supported
With the service_role key, on servers only.
SAML 2.0 SSO
Supported
Add providers on the Auth tab; see SAML 2.0 single sign-on. supabase sso CLI commands don't work.