Backend platforms on Vultr

Application backends, authentication, APIs, storage and databases.

1 documented option on Vultr. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Supabase Self-HostedAWS, Railway, VultrCustomer-operated
Servers / containers
Open Source / Open Core

Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0

Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server imageCustomer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
Scope and evidence

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

  • Supabase community AWS CloudFormation/CDK deployment — This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.

    Community template · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Self-host Supabase in a Railway project — Railway documents a community template for PostgreSQL, authentication, REST, storage, and Studio. The services communicate over private networking in the customer’s Railway project. Railway operates the underlying platform.

    Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Deploy the Supabase Marketplace application on Vultr Compute — Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.

    Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-21

Deployment evidence and category fit

Supabase Self-Hosted

PostgreSQL-based application backend with authentication, APIs, storage, realtime and functions; self-hosting does not include every managed-platform feature.

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

  • Deploy the Supabase Marketplace application on Vultr Compute ↗

    Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

    Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.

Cloud evidence reviewed 2026-11-21. Full listing and qualifications

Deployment and procurement checks

VPC provisioning
Vultr documents isolated IPv4 VPC networks with console, API, CLI and Terraform provisioning. Configure the selected location, address ranges and routes; private application access is separate from public ingress. Provider source ↗ · Reviewed 2026-11-14

For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.

Plan this deployment

Account boundary: Vultr account and compute instances. Access: Cloud account access and server SSH keys. Network: Instance networks and firewall rules.

Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings