Software on Railway
Software with a documented deployment path in a customer environment on Railway.
61 listings, including 61 from other publishers. Search and filter Railway listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- Railway workspace, project and environment; platform-managed infrastructure
- Network
- Project/environment private networking with separately exposed public services
- Identity & access
- Workspace/project access and scoped deployment tokens
- Deployment tooling
- 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.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-12. Check region, service availability, backup destinations and support access for your deployment.
Deployment and procurement checks
- 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. 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.
Browse by category
30 categories on Railway. Counts show matching listings; a listing can appear in more than one category.
Business operations7 categories
Governance & industries3 categories
Content & collaboration5 categories
Data & analytics4 categories
Developer platforms & operations7 categories
AI tools & infrastructure4 categories
No categories match your search.
Documented software
Deployment evidence and qualifications
Self-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- Railway project deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents a Railway template that deploys the Activepieces application with PostgreSQL and Redis into the operator's project. Railway manages the underlying infrastructure; the operator configures secrets, application access, persistence and backups. This is separate from Activepieces Cloud and does not establish ownership of an underlying hyperscaler account.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages application configuration, secrets, integrations, backups and upgrades. AWS and Google Cloud paths require customer-managed infrastructure; Railway operates the underlying platform within the customer project.
Scope: This entry covers self-hosted Activepieces, not Activepieces Cloud. The AWS template can provision RDS PostgreSQL, Redis, load balancing and Route 53 integration. The Google Cloud guide uses a VM/container example with SQLite and in-memory Redis; confirm release compatibility and use the current production database and queue requirements. Railway deploys into a customer project on platform-managed infrastructure. Enterprise features require a separate license.
License: MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Railway project deployment ↗
Deployment evidence and qualifications
Self-hosted application for document-grounded AI chat, retrieval and agents.
- AnythingLLM Docker installation overview ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
Scope: The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.
License: MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- AnythingLLM Docker installation overview ↗
Deployment evidence and qualifications
Self-hosted community questions, answers and knowledge content.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Apache Answer application and persistent database/storage. The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database. This source is distinct from the Cloudron package.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Open-source web archiving application for retained, searchable copies of web content.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
AI observability and evaluation server for traces, datasets and application experiments.
- Phoenix self-hosting deployment options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
Scope: The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.
License: Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Phoenix self-hosting deployment options ↗
Deployment evidence and qualifications
Self-hosted no-code database for organizing, relating and collaborating on business data.
- Baserow Railway installation ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide creates a Railway project from the Baserow template and configures the deployed application. The guide requires enough memory and a paid plan rather than assuming the free trial is adequate. Railway operates the underlying infrastructure; the customer controls the application project.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application, database and storage, applies updates and configures backups.
Scope: Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.
License: MIT-licensed core with paid premium features and subscription terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Baserow Railway installation ↗
Deployment evidence and qualifications
Community GRC platform with supplier risk assessments, evidence documents and third-party records.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy on Railway. The vendor comparison explicitly includes TPRM, evidence/document management and SAML SSO in Community. SCIM, advanced audit trails and other Pro features have separate commercial terms; Pro air-gap claims do not establish Community disconnected support.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The vendor comparison explicitly includes TPRM, evidence/document management and SAML SSO in Community. SCIM, advanced audit trails and other Pro features have separate commercial terms; Pro air-gap claims do not establish Community disconnected support.
License: AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
Self-hosted structured content and API management application.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Cockpit Core application with persistent SQLite database and storage on Railway. Core is MIT-licensed. Commercial modules and add-ons have separate terms; the single writable SQLite volume does not establish active-active HA.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Core is MIT-licensed. Commercial modules and add-ons have separate terms; the single writable SQLite volume does not establish active-active HA.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
Self-hosted content and data management with APIs over your SQL database.
- Directus 12 community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected community template uses the official Directus 12.6.1 image pinned by digest, PostgreSQL, Redis and bucket storage in a customer Railway project. Confirm current license/tier limits, image compatibility, initial credentials and email configuration; this is not Directus Cloud.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates containers, database, caching, asset storage, monitoring, backups and upgrades.
Scope: Current Directus 12 uses MSCL-1.0-GPL, replacing older BSL terms. Core has limits; higher limits and advanced features require a paid license or qualifying grant. Verify licensing against the actual release and do not assume all source-available features are unrestricted. This entry excludes Directus Cloud.
License: Source-available MSCL-1.0-GPL; free Core tier and licensed capabilities; qualifying Open Innovation Grant
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Directus 12 community deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted customer engagement and messaging orchestration platform.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted collaborative wiki and documentation with real-time editing, spaces and page history.
- Community Docmost deployment with database, queue and storage ↗
Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The canonical community template installs the upstream Docmost image with PostgreSQL, Redis and persistent attachment storage in a customer Railway project. Its image is mutable: select a current pinned release and validate APP_SECRET, database/queue variables, HTTPS and backups against vendor instructions. Paid-feature claims on the template page do not override upstream edition licensing.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages workspace access, secrets, database and attachment recovery, mail configuration and upgrades. Railway operates the underlying platform within the customer project.
Scope: Review used upstream 0.97.0, which includes security updates. Select a current pinned image; the canonical Railway template uses latest. Do not use the older 0.95.0 template unchanged: upstream fixed a private-space metadata issue in 0.96.0. SSO, audit logs, AI and other paid features require appropriate entitlements. Optional AI, mail and link-preview integrations introduce external connections.
License: AGPL-3.0 core; Business and Enterprise features use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Community Docmost deployment with database, queue and storage ↗
Deployment evidence and qualifications
Self-hosted document ingestion, OCR, classification and search.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted electronic-signature and document workflow application with a Railway deployment path.
- Documenso deployment in a Railway project ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
Documenso's official documentation provides an official Railway template and a manual project workflow that provisions the application service and managed PostgreSQL, configures secrets and networking and exposes the customer's deployment URL. The page identifies the guide as a community contribution that may become outdated. This is community-contributed deployment guidance published in the upstream documentation, not a verified vendor support commitment.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages the Railway project, application secrets, PostgreSQL recovery, SMTP, signing certificates, domains, access controls, data retention and upgrades; Railway operates the platform.
Scope: The official Railway page labels its instructions as a community contribution that may become outdated. Confirm the current upstream image or source revision and template before deployment. Production signing requires correctly protected encryption keys, SMTP and signing-certificate configuration. This entry covers signing workflow automation, not full contract lifecycle management.
License: AGPL-3.0 Community Edition; Enterprise Edition uses a commercial license.
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- Documenso deployment in a Railway project ↗
Deployment evidence and qualifications
Self-hosted knowledge management with structured documents, templates and controlled publication workflows.
- Documize community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe deploys Documize Community with PostgreSQL in a customer Railway project. It builds a community fork rather than a vendor-maintained image; inspect its source and replace unsupported runtime base images before production. No Documize commercial-edition features or vendor support are implied.
- Source for the community Documize Railway build ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected build compiles the Documize Community Go backend and Ember frontend. Its runtime currently uses Alpine 3.16, so update the base and validate compatibility before production; the source establishes a deployment recipe rather than a security certification.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer controls application/database hosting, access, backups and upgrades.
Scope: Documize documents native binary deployment and supported database choices. Its commercial feature list includes approvals, revisions and lifecycle controls. Match the selected edition to policy workflow requirements; no provider-specific deployment support was verified.
License: Open-source Community and commercial options; edition features differ
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Documize community deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted document forms and electronic-signature workflows with API and webhook integration.
- Vendor-linked Railway application template ↗
Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.
Scope: Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.
License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Vendor-linked Railway application template ↗
Deployment evidence and qualifications
File-based wiki for documentation and shared knowledge.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
DokuWiki web application with persistent wiki pages, configuration and attachments. Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version. This source is distinct from the Cloudron package.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version.
License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted encrypted photo backup and sharing backend with web clients.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted supplier records, procurement documents, quotation attachments and supplier scorecards.
- ERPNext self-hosted deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe runs ERPNext with web, queue, scheduler and realtime services plus MariaDB and Redis in a customer project. It layers Railway-specific startup/storage handling over the upstream ERPNext v16 image. Supplier management is part of that ERPNext application; review versions, backups and integrations separately from vendor-hosted Frappe Cloud.
- Source for the ERPNext Railway image ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected community wrapper starts from frappe/erpnext:v16 and adapts process supervision and persisted site assets for Railway. Match the selected ERPNext/Frappe release and database requirements before deployment.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer or implementation partner operates the application and maintains backups and upgrades.
Scope: An adjacent procurement comparator: supplier records connect RFQs, quotations, orders, receipts and invoices; source quotations can be retained as attachments. Supplier scorecards support recurring performance evaluation. The reviewed sources do not establish turnkey certificate-of-insurance expiry or supplier-compliance document workflows. ERPNext advisory GHSA-cc74-rc2g-p7hw describes authenticated SQL injection in the Selling and Buying modules that can expose sensitive database and active-session data, enabling administrator account takeover. There is no workaround; upgrade to 15.121.6 or 16.37.0 or later. ERPNext v16.60.0 adds supplier and customer dashboards plus RFQ and account-dimension changes, and includes portal and permission hardening. Review custom supplier workflows and permissions before upgrading.
License: GPL-3.0; implementation and support separately arranged
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- ERPNext self-hosted deployment on Railway ↗
Deployment evidence and qualifications
Customer-operated business and customer engagement platform.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
erxes XOS application services, database, search and supporting microservices on Railway. The repository mixes a custom licence and commercially licensed Enterprise files. Review the selected modules; public code is not a blanket AGPL grant.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The repository mixes a custom licence and commercially licensed Enterprise files. Review the selected modules; public code is not a blanket AGPL grant.
License: Custom source-available application terms with separately licensed Enterprise components.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted CRM with sales records, customer-service features and email campaign management.
- EspoCRM self-hosted deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template deploys the official espocrm/espocrm image with PostgreSQL and persistent application files in the customer project. Review the selected release, background job configuration, email and backups. Paid workflow or other commercial extensions are not established by this core application deployment.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer maintains application/database containers or servers, scheduled work, email services, backups, upgrades and selected extension compatibility.
Scope: The core includes campaign management. The feature matrix places BPM and workflows in Advanced Pack, while sales/inventory functions are in Sales Pack. These paid extensions have separate license terms and should not be assumed to be part of the AGPL core. EspoCRM 10.1.2 fixes OAuth Server access tokens being rejected when 2FA is enabled and an administrator temporarily losing access to scopes after another administrator views that user's record access. Operators using OAuth or 2FA should update.
License: AGPL-3.0 core; commercial extensions use separate restricted terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- EspoCRM self-hosted deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted real-time collaborative text editor.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Etherpad application, database and persistent plugins and settings. Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. This source is distinct from the Cloudron package.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Open-source business operations platform for people, projects, time and financial records.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted HR software covering employee records, onboarding, leave, payroll and employee lifecycle events.
- Frappe HR self-hosted deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe deploys Frappe HR with the Frappe/ERPNext runtime, workers, scheduler, realtime service, MariaDB and Redis in a customer Railway project. It installs the upstream hrms version-16 app on an ERPNext v16 image. Review app/framework version alignment, payroll rules, credentials and backups; this is not Frappe Cloud.
- Source for the Frappe HR Railway image ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected community build installs the upstream frappe/hrms version-16 branch over the official frappe/erpnext v16 image, with Railway-specific process and storage handling. Confirm compatible application releases and modules before production.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer or implementation partner maintains infrastructure, security, backups and software updates.
Scope: Employee records include joining, employment, education and exit details. Legal hold, controlled disposition and jurisdiction-specific personnel-file retention were not established. Verify the applicable component license and support terms for the selected distribution. Frappe HR v16.60.0 requires Frappe v16.60 and contains five breaking changes alongside employee-profile, organization-chart, letter, and dashboard work. Review custom HR workflows and access rules before upgrading.
License: Open-source; verify applicable component license and support terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Frappe HR self-hosted deployment on Railway ↗
Deployment evidence and qualifications
Feature flagging and experimentation platform with a self-operated application and SDKs.
- GrowthBook community deployment template on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
This community template deploys the upstream growthbook/growthbook application image with MongoDB in a customer Railway project. Configure distinct frontend and API origins and preserve database/uploads. This is a community deployment path rather than a GrowthBook support commitment or GrowthBook Cloud subscription.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages application availability, metadata database, SDK configuration, identity, data connections, backups and upgrades.
Scope: The bundled MongoDB service is a development/staging starting point. Warehouse connections, event tracking and managed database services can cross account boundaries; enterprise-only functionality is not included by the core license. GrowthBook v5.2.1 is a security patch release recommended for all self-hosted users. It updates zlib and multiple dependencies with known vulnerabilities and removes super-linear regular-expression backtracking.
License: MIT Expat for core code; specified enterprise directories use the GrowthBook Enterprise License.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- GrowthBook community deployment template on Railway ↗
Deployment evidence and qualifications
Container and OCI artifact registry for managing software images within customer-operated infrastructure.
- Harbor community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe provisions Harbor core, portal, job service, registry, registry control, scanner and proxy roles with PostgreSQL, Redis and object storage. Its component wrappers derive from upstream Harbor images. Review consistent image versions, TLS, authentication, registry storage and scanning/update operations; community packaging does not imply CNCF or project support.
- Source for the Harbor Railway core wrapper ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected core wrapper derives from the upstream goharbor/harbor-core image (v2.15.2). Review the corresponding versions and configuration of every Harbor component before deploying the full community template.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages artifact storage, database, TLS, identity, scanner configuration, replication, backups and upgrades.
Scope: Scanning, signing and replication depend on the components and endpoints configured. Sending images to a remote registry or scanner changes data boundaries. Harbor v2.15.5 bounds audit and manifest request bodies, enforces actual decompression byte limits, redacts sensitive pagination and upload locations in rejection errors, and updates dependencies for high-severity CVEs. Operators on the 2.15 line should upgrade to v2.15.5 or a later supported patch.
License: Apache License 2.0 for upstream Harbor.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Harbor community deployment on Railway ↗
Deployment evidence and qualifications
CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite. Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted kanban boards for projects and team tasks.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Kan application, PostgreSQL and persistent data on Railway. The reviewed v0.7.0 tag is a prerelease. Treat it as an early project and validate migrations and recovery before relying on it for production work.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The reviewed v0.7.0 tag is a prerelease. Treat it as an early project and validate migrations and recovery before relying on it for production work.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
Self-hosted project, board and issue management application.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Kaneo frontend and API, PostgreSQL and persistent application data. The Railway recipe installs the application and database; local SQLite development examples are a different topology.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Railway recipe installs the application and database; local SQLite development examples are a different topology.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
Self-hosted LLM observability, evaluations and prompt-management platform.
- Langfuse v3 community Railway deployment ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
Scope: Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.
License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Langfuse v3 community Railway deployment ↗
Deployment evidence and qualifications
Customer-hosted project and task management application for cross-functional teams.
- Leantime community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe builds upstream Leantime with PHP, Nginx and database configuration in a customer Railway project. Review and set the actual Leantime release/build argument, compatible PHP version, persistent uploads and database backups. This is not the vendor-managed Leantime cloud service or a vendor support commitment.
- Source for the community Leantime Railway image ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected Dockerfile downloads a selected release from Leantime/leantime and requires LEAN_VERSION to be set. It uses PHP 8.3 and supervises the application services; the recipe needs version and configuration review rather than treating all template defaults as production-ready.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer maintains the PHP/database or container stack, configuration, file storage, backups and application/plugin upgrades.
Scope: Scope is the downloadable application. The vendor distinguishes its open-source project section and work dashboard from other offerings; do not assume all website or marketplace features are included. Verify each plugin license and compatibility separately. Releases v3.15.1 and v3.15.2 fix calendar-event exposure, continued use of deactivated-user sessions and tokens, draft-document leakage, cross-project comment leakage, and inactive-account LDAP/OIDC behavior. v3.15.3 fixes users being unable to resume or complete onboarding. All three releases state that no database changes are required; use v3.15.3 or later rather than stopping on an earlier 3.15.x patch. Plugin developers upgrading from before v3.15.0 must still replace the removed legacy HTMX ticket event aliases with the documented lt:tickets:* events or event classes.
License: AGPL-3.0 downloadable application; marketplace plugins have separate terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Leantime community deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.
- LibreChat one-click deployment on Railway ↗
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
LibreChat documents creating a Railway account, reviewing the template's three containers and environment variables, deploying the services and accessing the resulting LibreChat URL in the customer's Railway project.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
Scope: The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.
License: MIT
Cloud evidence reviewed 2026-11-15. Read the full listing and sources →
- LibreChat one-click deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted shared inbox and customer support desk.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted AI API gateway providing model routing, access controls and usage tracking.
- LiteLLM Railway and Render deployment options ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
Scope: The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.
License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- LiteLLM Railway and Render deployment options ↗
Deployment evidence and qualifications
Open-source email archiving, search and export service with a community Railway deployment.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Mail-Archiver application, PostgreSQL and persistent archive storage. The Railway template follows a moving application image. Review current upstream retention, deletion-lock and audit-export settings, pin the chosen release, and verify backup/restore and authentication before production use.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Railway template follows a moving application image. Review current upstream retention, deletion-lock and audit-export settings, pin the chosen release, and verify backup/restore and authentication before production use.
License: GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
Self-hosted lightweight notes, documents and knowledge timeline.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Memos application, SQLite database and attachment storage. Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system. This source is distinct from the Cloudron package.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted file synchronization and sharing server for team document collaboration.
- Nextcloud Server community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template deploys the official Nextcloud container with PostgreSQL, a persistent application volume and bucket storage in a customer Railway project. Review the selected release, trusted domains/proxies, background jobs, object-storage configuration and backups. Optional Office, Talk and third-party apps can require additional services; they are not implied by this server deployment.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the server, storage, backups and upgrades; select a supported release and deployment method.
Scope: Scope is the self-hosted Server and file-sharing capabilities. The installation manual distinguishes official AIO from community Snap, VM and Docker options, which Nextcloud GmbH does not officially support. Review separately selected applications, integrations and enterprise support terms.
License: AGPL-3.0 Server core; review selected applications separately
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Nextcloud Server community deployment on Railway ↗
Deployment evidence and qualifications
Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
- NocoDB community cloud installation methods ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
Scope: The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.
License: Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- NocoDB community cloud installation methods ↗
Deployment evidence and qualifications
Self-hosted ERP and CRM applications for sales pipelines, business records and operational workflows.
- Odoo Community 19 deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template deploys the official odoo:19.0 Community image with PostgreSQL and persistent application storage in a customer Railway project. It does not establish access to Enterprise modules. Review database-version compatibility, administrator credentials, filestore backups and the enabled modules; platform resource charges still apply.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer or implementation partner hosts the application, secures it, manages backups and applies updates.
Scope: Scope this entry to an installation on customer-selected systems rather than Odoo Online or Odoo.sh. Enterprise requires valid subscription entitlements, and the documented registration mechanism periodically contacts Odoo validation services. Do not assume every business app is included in Community.
License: Community LGPLv3; Enterprise uses the Odoo Enterprise Edition License; individual add-ons may have other licenses
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Odoo Community 19 deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted project management with work packages, schedules, agile boards and collaboration.
- OpenProject Community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template uses upstream OpenProject 17 application images with web, worker and scheduler roles, PostgreSQL, Redis, Hocuspocus and an edge proxy. This is a customer Railway project with platform-managed infrastructure. Confirm matching image versions, attachment storage, credentials, backups and Community versus licensed features.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages infrastructure, backups and updates; support scope depends on the selected plan.
Scope: OpenProject explicitly states that Enterprise add-ons remain open-source GPLv3 software, not proprietary extensions. The recommended production Docker path separates processes with Compose; the all-in-one quick-start container is not the recommended production setup. Feature availability and support depend on the plan. OpenProject 17.9.7 fixes a critical CVSS 9.4 flaw that allowed users, and anonymous visitors on public instances, to invoke unintended project operations including deletion or restricted-data reads. It also fixes a second-factor bypass and multiple authorization and disclosure issues. Installations on 17.2–17.4 must move to a patched supported release; patched 17.5–17.8 branches are also available. OpenProject 17.9.8 adds eight security fixes covering meeting authorization, cached activity and work-package disclosure, invitation-mail disclosure, repository-URL SSRF, external-storage virus-scan enforcement and unauthorized meeting-outcome movement. Upgrade the 17.9 line and review the linked advisories for other affected branches.
License: GPLv3 across Community and Enterprise software; paid Enterprise plans provide support, services and add-on enablement
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- OpenProject Community deployment on Railway ↗
Deployment evidence and qualifications
Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.
- Self-operated OpenSearch and Dashboards on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
Scope: 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.
License: Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Self-operated OpenSearch and Dashboards on Railway ↗
Deployment evidence and qualifications
Self-hosted assembly governance for agendas, motions, elections and meeting participation.
- OpenSlides 4.3 community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template documents the OpenSlides 4.3 service architecture, including proxy, client, backend roles, authentication, voting, media, realtime components, PostgreSQL and Redis. Adapters provide generated secret files for Railway. Verify every image is pinned to a mutually compatible release and review backups, public endpoints and voting/meeting requirements; this is not vendor-managed hosting.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates containers, application data, HTTPS, backups and upgrades.
Scope: The official project documents assembly management and a Docker Compose installation. This is a narrower meeting/decision workflow alternative rather than a complete board governance document system. No specific hyperscaler deployment was verified.
License: MIT open-source license
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- OpenSlides 4.3 community deployment on Railway ↗
Deployment evidence and qualifications
Community document management with OCR, full-text search, metadata and ingestion workflows.
- Community Railway Paperless-ngx stack ↗
Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The template provisions the application with PostgreSQL, Redis and a persistent volume in the customer project. Railway operates the platform. Pin and verify a current patched application image and volume paths against upstream instructions; the template documentation is not a tested deployment guarantee.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates application permissions, ingestion, backups, secrets and upgrades. Railway manages its platform resources; a Vultr VM also requires customer OS/container maintenance.
Scope: Review used upstream 3.5.0. Pin a current image before importing documents and coordinate database/document backups. The canonical Railway template uses a mutable latest tag; its setup text does not certify production readiness. An older separately reviewed 3.0.5 template predates an AI-permission fix and is not the recommended package. Optional email, document converters and AI integrations need separate access and data-flow review. Release 3.5.0 moves bulk operations to asynchronous processing, adds manual workflow triggers, tightens configuration-view and descendant-tag permissions, clears sessions automatically, and fixes the default MFA trusted-authentication setting. Some installations must adjust PAPERLESS_ALLOWED_HOSTS before upgrading.
License: GPL-3.0; conversion tools and other bundled components have separate licenses.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Community Railway Paperless-ngx stack ↗
Deployment evidence and qualifications
Lightweight document archive with text extraction, organization sharing, tagging and search.
- Community Papra application deployment in a Railway project ↗
Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
Deploys the application, persistent metadata volume, document bucket and mail-capture service into the customer Railway project. This is independent packaging, not upstream support certification. Review the wrapper and pin a current application image; retain storage/encryption secrets and configure a production mail relay.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages application access, secrets, storage, backups and updates. Railway operates its underlying platform; the community template runs in the customer project.
Scope: The reviewed application release is 26.7.1; Papra fixes only the latest version. Pin a current image and preserve database, documents and encryption keys together. The Railway wrapper adds initial-account setup and storage permissions; Mailpit captures mail until a real relay is configured. Optional OCR/model services, intake email and webhooks can send content outside the installation.
License: AGPL-3.0; dependencies and independently maintained packaging retain their own terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Community Papra application deployment in a Railway project ↗
Deployment evidence and qualifications
Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.
- Parseable OSS on Railway ↗
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream template runs the application in the customer's Railway project with a Railway Bucket for durable objects and a persistent volume for staged events.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: The customer manages credentials, data ingestion, persistent staging, object storage, access configuration, retention, backups and upgrades.
Scope: The standalone example is a single pod; distributed OSS has a separate vendor guide and is not automatically an HA guarantee. Chart 3.2.4 defaults to application v3.2.3, whereas the reviewed upstream release is v3.2.7. Existing standalone charts through 3.0.2 need a new 3.1.0+ installation and verified data migration. Railway uses a moving edge image, paid Buckets and a persistent staging volume. Disable optional usage statistics with P_SEND_ANONYMOUS_USAGE_DATA=false when required; this alone does not establish air-gapped operation.
License: AGPL-3.0 for the OSS project. Standalone and distributed OSS deployment guides are available; Enterprise software/support has separate terms.
Cloud evidence reviewed 2026-11-20. Read the full listing and sources →
- Parseable OSS on Railway ↗
Deployment evidence and qualifications
Self-hosted collaborative interface design and prototyping platform.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Website analytics tracker and dashboard available as a self-hosted Community Edition.
- Plausible Community Edition deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
This community template deploys the Plausible Community Edition image with PostgreSQL, ClickHouse and a mail service in a customer project. ClickHouse uses community configuration packaging. Review image versions, storage and outbound email, and create the initial owner promptly; this is distinct from paid Plausible Analytics hosting.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages tracker delivery, ingestion, databases, email configuration, TLS, backups and CE upgrades.
Scope: Use the CE feature list when evaluating functionality; managed-service funnels, revenue metrics, SSO and other features are not automatically available in the self-hosted edition. Plausible Community Edition v3.2.1 removes the /storybook endpoint after CVE-2026-8467 showed it could permit remote code execution when exposed to an untrusted network. Upgrade affected v3.0–v3.2 deployments to v3.2.1 or later; until upgraded, block /storybook at the reverse proxy or equivalent network layer.
License: AGPLv3 for Plausible Community Edition. Commercial/cloud-only features and branding have separate terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Plausible Community Edition deployment on Railway ↗
Deployment evidence and qualifications
Document processing and retrieval platform for building RAG and agentic knowledge applications.
- Community RAGFlow Railway application stack ↗
Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.27.1. Vendor support commitment: not assessed; confirm the selected release and contract.
This community template deploys the application, Elasticsearch, MySQL, Redis, a local embedding service and object storage into the customer Railway project. Its linked Dockerfile pins upstream RAGFlow v0.27.1 with a Railway startup/configuration wrapper. The template is not proof of 1.0 compatibility or upstream support; review migrations and the separately configured chat-model endpoint. Railway manages the underlying infrastructure.
- Railway deployment image source and release pin ↗
Community template · Reviewed 2026-11-12 · Scope: Community / upstream open-source; third-party distribution where noted · Version: 0.27.1. Vendor support commitment: not assessed; confirm the selected release and contract.
Source inspection confirms the v0.27.1 base image and the custom configuration, nginx and startup wrapper used by the linked Railway template. The upstream 1.0 release changes the architecture and requires its documented migration path; do not substitute a new image tag without reviewing the complete stack.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
Scope: Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.
License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Community RAGFlow Railway application stack ↗
Deployment evidence and qualifications
Self-hosted group scheduling polls and meeting coordination.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Rallly application, PostgreSQL, persistent storage and outbound email. Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery. This source is distinct from the Cloudron package.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Open-source on-premises file-sharing software with a community Railway deployment.
- Railway Template ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Safebucket application, PostgreSQL and MinIO-backed object storage. The template follows moving images. Activity and notifier defaults can use ephemeral filesystem storage; configure durable activity logging and outbound notification services before relying on audit records or external-sharing workflows.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The template follows moving images. Activity and notifier defaults can use ephemeral filesystem storage; configure durable activity logging and outbound notification services before relying on audit records or external-sharing workflows.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway Template ↗
Deployment evidence and qualifications
Self-hosted email marketing, subscriber and campaign management.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Laravel application, PostgreSQL, Redis, queues and scheduler on Railway. An external approved sending provider is required for real delivery; provider free credits are not a durable operating-cost estimate.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: An external approved sending provider is required for real delivery; provider free credits are not a durable operating-cost estimate.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Open-source, customer-operated CRM with marketing campaigns and configurable record workflows.
- SuiteCRM 8 community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe deploys SuiteCRM 8.10 with PHP/Apache, its scheduler and asynchronous worker, plus MariaDB and persistent application storage. The build downloads the upstream SuiteCRM release. Review current versions, initial administrator credentials, mail integration and backups; this does not include separately licensed extensions or vendor-hosted service.
- Source for the SuiteCRM Railway image ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected image downloads SuiteCRM-Core v8.10.2 from the upstream release repository and uses PHP 8.3. Confirm the compatibility matrix and update the release and database together when maintaining the deployment.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer configures and maintains the web/database stack, scheduled and background work, email transport, backups and software security updates.
Scope: Scope is the downloadable self-hosted CRM. Campaigns and workflow configuration are documented, but external email delivery and optional integrations need their own operational arrangements. Confirm compatibility requirements before upgrading; community extensions are separately scoped.
License: AGPL-3.0 application; separately selected extensions and services have their own terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- SuiteCRM 8 community deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.
- Self-host Supabase in a Railway project ↗
Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
Scope: 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.
License: Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0
Cloud evidence reviewed 2026-11-21. Read the full listing and sources →
- Self-host Supabase in a Railway project ↗
Deployment evidence and qualifications
Open-source agile project, issue and team planning application.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Taiga frontend, backend, database, task workers and persistent media. Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials. This source is distinct from the Cloudron package.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials.
License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted task, project and personal productivity application.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted visual conversation and form builder.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
License: FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted website and event analytics application with dashboards and PostgreSQL storage.
- Umami self-hosted deployment on Railway ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
Scope: Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.
License: MIT License for upstream Umami.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Umami self-hosted deployment on Railway ↗
Deployment evidence and qualifications
Self-hosted email campaign and transactional messaging application.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Community service desk for support tickets and customer communications.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
UVdesk application, MySQL, files and mail services in Railway. The template includes Mailpit; mail capture or testing is not a production outbound email service. Configure approved SMTP delivery and mailbox access.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The template includes Mailpit; mail capture or testing is not a production outbound email service. Configure approved SMTP delivery and mailbox access.
License: Open Software License 3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted enterprise wiki and structured knowledge application platform.
- Railway ↗
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
License: GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Railway ↗
Deployment evidence and qualifications
Self-hosted helpdesk and ticketing application for customer service and internal support teams.
- Zammad community deployment on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe deploys Zammad application roles with PostgreSQL, Redis, Memcached and Elasticsearch in a customer project. Its wrapper builds on the official Zammad image and adapts storage/bootstrap configuration for Railway. Review all image versions, object-storage settings, credentials, email integration and upgrades; this is not Zammad hosted service.
- Source for the Zammad Railway application wrapper ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected application wrapper derives from ghcr.io/zammad/zammad and supplies Railway-specific startup/bootstrap behavior. The tag is configurable; pin and review it together with the backing services rather than assuming that latest remains compatible.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer runs the application stack, database, backups and security updates; follow supported distribution and release requirements.
Scope: Scope is the self-hosted helpdesk core. The official repository supplies an AGPL-3.0 license, although the marketing open-source page labels it GPL v3; verify the license shipped with the selected release. Zammad 7.2.3 is a critical security release and self-hosted operators should upgrade immediately. Package installations using nginx or Apache must update the reverse-proxy configuration for the Remote-User header; Docker images include the change.
License: AGPL-3.0 repository license for the core application
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Zammad community deployment on Railway ↗
Deployment evidence and qualifications
Application identity platform that can run as a self-operated service with its own PostgreSQL database.
- ZITADEL community deployment template on Railway ↗
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template uses official ZITADEL server and login images with PostgreSQL in a customer Railway project. Review server/login version alignment, initial administrator credentials and the production checklist; Login V2 requires additional service-user configuration. This is separate from ZITADEL Cloud.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.
Scope: The Compose guide is a starting point for a homelab or semi-production installation. The current contribution guide states that engineering focus on next-generation work limits community PR review capacity for this codebase; evaluate the supported release roadmap. External identity and message providers remain separate. ZITADEL v4.20.4 enables PKCE by default for Google, GitHub, GitLab, and Azure AD identity providers and hardens SMS OTP and password history. Revalidate external IdP callbacks and authentication policy after upgrading. ZITADEL v4.20.5 fixes a Login V2 MFA bypass in which a first-factor-only session could add a new authenticator even when a second factor was already configured. Upgrade and verify authenticator-enrolment policy.
License: GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- ZITADEL community deployment template on Railway ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings