
# Databases & vector on Railway

Compare documented Databases & vector deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/databases-vector/
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: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

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

2 listings.


## OpenSearch

Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.

- Listing: https://launchinyourcloud.com/directory/opensearch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.
- Licensing model: open-source
- Installation: Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.
- Architecture: Customer-operated distributed cluster with index shards and replicas on persistent storage, plus optional Dashboards and ingestion components
- Operations: Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
- Product website: https://opensearch.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Sample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Official Docker images run OpenSearch nodes and Dashboards on compatible container hosts. Persistent index storage and host memory and kernel settings are operational requirements; distribution through a cloud registry does not establish a provider deployment badge.


### Category fit

- databases-vector: Indexes and searches vectors alongside metadata, with lexical, nearest-neighbor, semantic and hybrid retrieval. Embedding generation requires an appropriate configured model or externally generated vectors.

- data-analytics: Distributed search and aggregation engine with OpenSearch Dashboards for exploring and visualizing indexed data.

- observability: Search and analytics over ingested operational data, including log analysis and monitoring; collection, ingestion and dashboard configuration remain deployment work.

- ai-tools: Vector storage, semantic search and retrieval for AI applications and RAG. Embedding generation and model connectors have separately configured runtimes and data flows.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/opensearch-analytics (checked 2026-11-12). 


### Cloud deployment evidence

- Self-operated OpenSearch and Dashboards on Railway (railway): https://railway.com/deploy/opensearch-analytics
  The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The OpenSearch Software Foundation is organized under the Linux Foundation. Official release records show OpenSearch 3.9.0 released on 29 September 2026 and continuing maintenance planning. Project case studies describe production adoption by Atlassian, LINE and other organizations; managed-service case studies demonstrate project adoption rather than proving self-hosted account boundaries.

Reviewed 2026-11-10.

- OpenSearch Software Foundation: https://opensearch.org/foundation/

- Current releases and maintenance policy: https://opensearch.org/releases/

- Current released artifacts: https://opensearch.org/downloads/

- Named production case studies: https://opensearch.org/case-studies/

### Sources

- OpenSearch Core capabilities and architecture: https://opensearch.org/platform/opensearch-core/

- Vector search documentation: https://docs.opensearch.org/latest/vector-search/

- Official Docker installation: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- Security demo configuration: https://docs.opensearch.org/latest/security/configuration/demo-configuration/

- Release downloads and Apache-2.0 licensing: https://opensearch.org/downloads/

- Upstream Apache-2.0 license: https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

- OpenSearch 3.10.0 release: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0

### Licensing sources

- https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

### Infrastructure sources

- https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- https://opensearch.org/platform/opensearch-core/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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 Security plugin supports the SAML 2.0 browser SSO profile, primarily for OpenSearch Dashboards. This is not a general authentication method for every direct OpenSearch client/API call. Scope: OpenSearch Security plugin and Dashboards browser login. Source: https://docs.opensearch.org/latest/security/authentication-backends/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker installation guide provides official images and Compose examples. Configure the required administrator password, persistent data and security settings; demo certificates/settings are not a production security baseline. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide sets a default 1-GB JVM heap and recommends allocating about half of system RAM to heap. It does not establish one complete production minimum: data/index size, roles, replicas, ingestion, Dashboards, vectors and storage performance must be sized separately. A JVM default is not HA capacity. Scope: Upstream JVM/install defaults; full production footprint unresolved. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/index/ (reviewed 2026-11-20).

- License pricing: Documented. The OpenSearch core is Apache-2.0 licensed. Plugins and bundled components require their own licence review; commercial support, managed Amazon OpenSearch Service, model services and infrastructure have separate prices. Scope: Upstream OpenSearch core licence; managed service pricing excluded. Source: https://raw.githubusercontent.com/opensearch-project/OpenSearch/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenSearch 3.10.0 was published November 18, 2026. It removes experimental Views and macOS x64 archives and contains material remote-store, indexing, heap, snapshot, translog, and OOM fixes; match OpenSearch Dashboards and plugins to 3.10. Scope: Upstream OpenSearch 3.10 release. Source: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0 (reviewed 2026-11-18).







## 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.






