
# Backend platforms on Vultr

Compare documented Backend platforms deployments on Vultr, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/vultr/backend-platforms/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Vultr account and compute instances
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.vultr.com/products/compute/instances/cloud-compute/provisioning (checked 2026-11-20).
- Network: Instance networks and firewall rules
- Identity and access: Cloud account access and server SSH keys
- Installation guidance: Provision compute through the console, API, CLI or Terraform, then install and operate the documented application.
- Guidance source: https://docs.vultr.com/products/compute/instances/cloud-compute/provisioning
- Guidance reviewed: 2026-11-12


### 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.
Source: https://docs.vultr.com/products/network/vpc-networks/provisioning (reviewed 2026-11-14).

The listings below have evidence for Vultr. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## Supabase Self-Hosted

Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.

- Listing: https://launchinyourcloud.com/directory/supabase/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0
- Licensing model: open-source
- Installation: Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server image
- Architecture: Customer-operated PostgreSQL database and containerized backend services
- Operations: Customer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
- Product website: https://supabase.com/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The listed self-hosted distribution uses open-source components; the Supabase platform repository is Apache-2.0. Managed-cloud features and paid support are separate from this public self-hosted distribution, and bundled components retain their own licenses.

The official installation runs PostgreSQL and supporting services through Docker Compose on a Linux server or VPS. This is persistent application infrastructure, even when it exposes functions.


### Category fit

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

- databases-vector: A PostgreSQL-based application data platform with database APIs, authentication and storage services. This entry covers the self-hosted stack.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/supabase-community/supabase-on-aws (checked 2026-11-21). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/guides/supabase (checked 2026-11-21). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application (checked 2026-11-21). 


### Cloud deployment evidence

- Supabase community AWS CloudFormation/CDK deployment (aws): https://github.com/supabase-community/supabase-on-aws
  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.
  Source type: community-template; reviewed: 2026-11-21; vendor support: not-assessed.

- Self-host Supabase in a Railway project (railway): https://railway.com/guides/supabase
  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.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.

- Deploy the Supabase Marketplace application on Vultr Compute (vultr): https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application
  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.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Self-hosting scope and responsibilities: https://supabase.com/docs/guides/self-hosting

- Official Docker deployment: https://supabase.com/docs/guides/self-hosting/docker

- Platform repository license: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- Self-host Supabase in a Railway project: https://railway.com/guides/supabase

- Deploy the Supabase Marketplace application on Vultr Compute: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application

### Licensing sources

- https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- https://supabase.com/docs/guides/self-hosting

### Infrastructure sources

- https://supabase.com/docs/guides/self-hosting/docker


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted Auth service supports external OAuth providers, including a configurable Keycloak issuer. This serves end users of applications built on Supabase; it does not establish organizational SSO for the self-hosted Studio/admin dashboard. Review provider, redirect, signup and administrative access separately. Scope: Self-hosted application-user Auth service; Studio federation excluded. Source: https://raw.githubusercontent.com/supabase/auth/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream docker directory contains the multi-service Compose stack and related environment/configuration files. Follow the self-hosting guide for a matching deployment version and replace secrets. Scope: Self-hosted multi-service stack; not the monthly developer newsletter version. Source: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. For all components, the guide gives 2 CPU cores, 4 GB RAM and 40 GB SSD as a minimum; 4 cores, 8 GB+ and 80 GB+ SSD are recommended. Optional analytics increases requirements. Scope: Docker stack for development and small-to-medium production; not every workload. Source: https://supabase.com/docs/guides/self-hosting/docker (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






