
# ERP & CRM on Railway

Compare documented ERP & CRM deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/erp-crm/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




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


## Provider guidance

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


### Project networking

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

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

4 listings.


## ERPNext Supplier Management

Self-hosted supplier records, procurement documents, quotation attachments and supplier scorecards.

- Listing: https://launchinyourcloud.com/directory/erpnext-supplier-management/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-3.0; implementation and support separately arranged
- Licensing model: open-source
- Installation: Frappe installation scripts
- Architecture: Customer-operated ERP application and database
- Operations: Customer or implementation partner operates the application and maintains backups and upgrades.
- Product website: https://frappe.io/erpnext
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The listed supplier-management functionality is part of ERPNext, whose official repository uses GPLv3. Commercial hosting, implementation or support services do not convert that application code into an open-core offering.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- vendor-supplier-document-management: An adjacent procurement comparator covering supplier records, quotation attachments and recurring scorecards; turnkey supplier certification and insurance-expiry workflows were not verified.

- erp-crm: Supplier and procurement records within the ERPNext suite, connecting quotations, orders, receipts and invoices. This listing focuses on that ERP workflow.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/erpnext--erp-next (checked 2026-11-12). Source: https://github.com/gridalpha/erpnext-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- ERPNext self-hosted deployment on Railway (railway): https://railway.com/deploy/erpnext--erp-next
  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 type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the ERPNext Railway image (railway): https://github.com/gridalpha/erpnext-railway/blob/main/Dockerfile
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting and licensing: https://frappe.io/erpnext/pricing

- Supplier records and linked documents: https://docs.frappe.io/erpnext/supplier

- Supplier quotation attachments: https://docs.frappe.io/erpnext/supplier-quotation

- Supplier scorecards: https://docs.frappe.io/erpnext/supplier-scorecard

- Licensing and edition terms: https://raw.githubusercontent.com/frappe/erpnext/develop/license.txt

- Licensing and edition terms: https://docs.frappe.io/legal/others/license-and-trademark

- ERPNext Selling and Buying SQL-injection advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-cc74-rc2g-p7hw

- ERPNext v16.60.0 release: https://github.com/frappe/erpnext/releases/tag/v16.60.0

- ERPNext cross-scope data advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29

- ERPNext supplier invoice exposure advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8

### Licensing sources

- https://raw.githubusercontent.com/frappe/erpnext/develop/license.txt

- https://docs.frappe.io/legal/others/license-and-trademark

- https://frappe.io/erpnext/pricing

### Infrastructure sources

- https://frappe.io/erpnext/pricing


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Frappe documents OIDC-based social login between a Frappe identity-provider server and an application server. Configure the framework clients and review user-role mapping; this is not a supplier-module-specific identity guarantee. Scope: ERPNext/Frappe platform authentication; business-module authorization is separate. Source: https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: ERPNext advisories cover cross-scope business-data access and public supplier e-invoice exposure. Upgrade to a fixed or later supported ERPNext release and recheck supplier, invoice, and cross-company permissions. Scope: GHSA-m668-9q43-8g29 is fixed in 15.124.2 and 16.53.0; GHSA-9jrr-9pr6-7mv8 is fixed in 15.124.0 and 16.52.0.. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29 (reviewed 2026-11-18). Supporting source: Supplier e-invoice advisory — https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Frappe Docker provides a production Compose base and deployment overrides. Its pwd.yml is a disposable demo. Build/select the ERPNext image and matching configuration; this is platform packaging, not a separately versioned supplier-management appliance. Scope: ERPNext platform deployment; supplier-management configuration remains application-specific. Source: https://github.com/frappe/frappe_docker (reviewed 2026-11-14). Deployment artifact: https://github.com/frappe/frappe_docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The official Frappe Docker single-server ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD, with MariaDB, Redis and an HTTPS proxy on that host. This is a small single-bench recipe, not a validated supplier-management capacity or HA minimum for 100 users and 1 TB. Scope: Underlying ERPNext/Frappe single-server example; additional data, workers, backups and replicas require sizing. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20).

- License pricing: Documented. ERPNext is free open-source software under GPLv3. Self-hosting does not require a per-user software subscription; hosting, implementation and support are separate costs. Frappe Cloud prices are managed-hosting prices, not self-hosted licence fees. Scope: ERPNext core, including supplier-management functionality; third-party apps and services have separate terms. Source: https://frappe.io/erpnext/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. ERPNext v16.60.0 was published November 17, 2026. It adds supplier and customer dashboards, RFQ and account-dimension changes, and portal and permission hardening; validate custom workflows and installed Frappe compatibility. Scope: Upstream ERPNext v16 release. Source: https://github.com/frappe/erpnext/releases/tag/v16.60.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- ERPNext Selling and Buying SQL injection (security-advisory): GHSA-cc74-rc2g-p7hw permits database and active-session disclosure, with possible administrator account takeover. Scope: ERPNext Selling/Buying: fixed in 15.121.6 and 16.37.0. This is a platform-module issue, not a separately versioned supplier appliance. Conditions: An authenticated account, including a portal account without assigned roles, can reach the vulnerable endpoint; no victim interaction is required. Action: Install a fixed or later supported patch for the deployed branch. The advisory provides no workaround. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-cc74-rc2g-p7hw; reviewed 2026-11-17.

- ERPNext supplier and business-data access-control fixes (security-advisory): ERPNext advisories cover cross-scope business-data access and public supplier e-invoice exposure. Scope: GHSA-m668-9q43-8g29 is fixed in 15.124.2 and 16.53.0; GHSA-9jrr-9pr6-7mv8 is fixed in 15.124.0 and 16.52.0. Conditions: The first issue requires a low-privilege authenticated user. The invoice issue concerns affected public portal behavior. Action: Upgrade to a fixed or later supported ERPNext release and recheck supplier, invoice, and cross-company permissions. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29; reviewed 2026-11-18. Supporting source: Supplier e-invoice advisory — https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8.




## EspoCRM Self-Hosted

Self-hosted CRM with sales records, customer-service features and email campaign management.

- Listing: https://launchinyourcloud.com/directory/espocrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; commercial extensions use separate restricted terms
- Licensing model: open-source
- Installation: Official Docker, installation script or manual PHP server installation
- Architecture: Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services.
- Operations: Customer maintains application/database containers or servers, scheduled work, email services, backups, upgrades and selected extension compatibility.
- Product website: https://www.espocrm.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

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.

The downloadable core is GNU AGPL version 3. Advanced Pack and other commercial extensions use a separate license restricting redistribution and limiting installation/use. The directory groups open-source and open-core offerings under one filter.

Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services. EspoCRM 10.1 drops support for MariaDB 10.3–10.5, so upgrades require a supported database version.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, leads and sales opportunities; broader ERP functions are not established for the base application.

- marketing-automation: Segmented campaign email, target lists and campaign tracking; workflow/BPM automation is separately offered in Advanced Pack.

### Deployment boundaries


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


### Cloud deployment evidence

- EspoCRM self-hosted deployment on Railway (railway): https://railway.com/deploy/espocrm
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release feed publishes EspoCRM 10.1.2 dated November 16, 2026. The vendor documents named Red Cross implementations, including the Armenian Red Cross Society and Slovak Red Cross, with links to institutional sources. Those implementations demonstrate adoption without establishing one common hosting model or extension set.

Reviewed 2026-11-16.

- Current maintained download and release: https://www.espocrm.com/download/

- Named institutional adoption examples: https://www.espocrm.com/blog/nonprofits-espocrm/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Sources

- Self-hosted installation, current release and core license: https://www.espocrm.com/download/

- Core and extension feature boundaries: https://www.espocrm.com/features/

- Campaign configuration and email delivery: https://docs.espocrm.com/user-guide/campaigns/

- Open-source application license: https://www.espocrm.com/espocrm-open-source-license/

- Commercial extension restrictions: https://www.espocrm.com/extension-license-agreement/

- Named nonprofit implementations: https://www.espocrm.com/blog/nonprofits-espocrm/

- Application architecture and database requirements: https://github.com/espocrm/espocrm

- EspoCRM 10.1 compatibility changes: https://www.espocrm.com/blog/espocrm-v10-1-released/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Licensing sources

- https://www.espocrm.com/espocrm-open-source-license/

- https://www.espocrm.com/extension-license-agreement/

- https://www.espocrm.com/features/

### Infrastructure sources

- https://www.espocrm.com/download/

- https://github.com/espocrm/espocrm

- https://www.espocrm.com/blog/espocrm-v10-1-released/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. EspoCRM supports external OpenID Connect providers from version 7.3, with optional user creation and team mapping. Portal OIDC is documented from 7.4. Provider MFA and supported client-authentication methods must be checked separately. Scope: Self-hosted EspoCRM; version-specific OIDC and portal configuration. Source: https://docs.espocrm.com/administration/oidc/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor Docker repository distinguishes a production prebuilt image from development builds and includes database, daemon and websocket configuration. Replace example database credentials and retain persistent volumes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/espocrm/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/espocrm/docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The server guide specifies supported PHP/database versions and recommends a VPS or dedicated server for production. It does not establish a quantitative whole-host CPU/RAM/storage minimum or an HA profile for the proposed workload. Scope: EspoCRM application, database and scheduled/background work; shared-hosting capability is not a capacity guarantee. Source: https://docs.espocrm.com/administration/server-configuration/ (reviewed 2026-11-20).

- License pricing: Documented. EspoCRM core is distributed under AGPLv3. That licence does not include separately sold extensions, hosting or professional support, and it should not be treated as a quote for those services. Scope: Reviewed open-source core; commercial extensions and services are separate. Source: https://www.espocrm.com/espocrm-open-source-license/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is 10.1.2, published 2026-11-16. 10.1.2 adds OAuth/2FA and administrator-scope fixes; check the 10.1 database compatibility requirements before upgrading. This is a dated release snapshot, not a support or future-cadence promise. Scope: Upstream espocrm/espocrm release record; commercial editions and deployment packages may differ. Source: https://github.com/espocrm/espocrm/releases/tag/10.1.2 (reviewed 2026-11-16).







## Odoo On-Premise

Self-hosted ERP and CRM applications for sales pipelines, business records and operational workflows.

- Listing: https://launchinyourcloud.com/directory/odoo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Community LGPLv3; Enterprise uses the Odoo Enterprise Edition License; individual add-ons may have other licenses
- Licensing model: open-source
- Installation: Linux packages or source installation with PostgreSQL
- Architecture: Customer-operated Odoo application server and PostgreSQL database
- Operations: Customer or implementation partner hosts the application, secures it, manages backups and applies updates.
- Product website: https://www.odoo.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The listed on-premise offering spans LGPLv3 Community and the separately licensed Enterprise edition. Enterprise and certain app code use restrictive commercial licenses; the fact that some source is accessible does not make all editions LGPL.

Official packages install Odoo as a persistent Linux service and require PostgreSQL. Windows packages are documented for testing/local instances, with production deployment discouraged.


### Category fit

- erp-crm: Modular business applications spanning CRM, sales, accounting, inventory and operations; applications and entitlements vary between Community and Enterprise.

### Deployment boundaries


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


### Cloud deployment evidence

- Odoo Community 19 deployment on Railway (railway): https://railway.com/deploy/odoo-crm-erp
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official packaged installation documentation source: https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst

- Community and Enterprise licenses: https://raw.githubusercontent.com/odoo/documentation/19.0/content/legal/licenses.rst

- Business application scope: https://raw.githubusercontent.com/odoo/odoo/19.0/README.md

- On-premise registration and validation: https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise.rst

- CRM workflow: https://raw.githubusercontent.com/odoo/documentation/19.0/content/applications/sales/crm.rst

### Licensing sources

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/legal/licenses.rst

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst

### Infrastructure sources

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Odoo 19 documents Google account sign-in using the OAuth Authentication module and a configured Google OAuth client. This establishes Google OAuth login; it does not establish arbitrary SAML providers or automatic enterprise user provisioning. Scope: Odoo 19 Google sign-in; configure both the external provider and the Odoo database. Source: https://www.odoo.com/documentation/19.0/applications/general/users/google.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Odoo 19 documentation identifies official Community nightly packages and Community/Enterprise downloads for supported operating systems. Enterprise downloads require a paying on-premise customer or partner account; packages also require PostgreSQL and other dependencies. Scope: Odoo 19 packaged installers; not an IaC template or Odoo Online entitlement. Source: https://www.odoo.com/documentation/19.0/administration/on_premise/packages.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. Odoo 19 provides production worker-sizing guidance: approximately six concurrent users per worker, a CPU rule of (cores × 2) + 1, and RAM estimates for light versus heavy workers. Add cron workers, PostgreSQL, storage and replicas; these are sizing rules, not a fixed 100-user HA minimum. Scope: Odoo 19 Linux multiprocess deployment; named users differ from concurrent users. Source: https://www.odoo.com/documentation/19.0/administration/on_premise/deploy.html (reviewed 2026-11-20).

- License pricing: Documented. Odoo 19 Community is LGPLv3; Enterprise has a separate proprietary licence. The per-user Custom subscription includes the on-premise option. Hosting, implementation, custom-code maintenance and in-app services can add costs; Odoo.sh hosting is excluded from the displayed subscription. Scope: Odoo Community versus Enterprise Custom on-premise; displayed currency and introductory discounts vary. Source: https://www.odoo.com/pricing-plan (reviewed 2026-11-20). Supporting source: Odoo 19 licences — https://www.odoo.com/documentation/19.0/legal/licenses.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SuiteCRM Self-Hosted

Open-source, customer-operated CRM with marketing campaigns and configurable record workflows.

- Listing: https://launchinyourcloud.com/directory/suitecrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 application; separately selected extensions and services have their own terms
- Licensing model: open-source
- Installation: Official prebuilt SuiteCRM 8 package and server installation guide
- Architecture: Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.
- Operations: Customer configures and maintains the web/database stack, scheduled and background work, email transport, backups and software security updates.
- Product website: https://suitecrm.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The downloadable application core is GNU AGPL version 3. Paid hosting, implementation and support do not change the listed core license; review any separate extension licenses.

Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, opportunities, quotes and service processes; this is CRM rather than a complete financial ERP.

- marketing-automation: Targeted email campaigns and configurable workflows around CRM records; campaign delivery requires configured email and background jobs.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/suitecrm (checked 2026-11-12). Source: https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- SuiteCRM 8 community deployment on Railway (railway): https://railway.com/deploy/suitecrm
  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 type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the SuiteCRM Railway image (railway): https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release notes document SuiteCRM 8.10.2 security and maintenance work released July 31, 2026, and credit community contributors. The vendor case study describes Humanetics Innovative Solutions using SuiteCRM for customer visibility, sales workflows and targeted campaigns; the study does not establish the hosting model of every adopter.

Reviewed 2026-11-10.

- Security maintenance and contributor acknowledgements: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Named customer implementation: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Sources

- SuiteCRM 8 installation: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/

- Self-hosting and paid service scope: https://suitecrm.com/pricing/

- Marketing campaigns: https://docs.suitecrm.com/8.x/user/marketing-outreach/campaigns-overview/

- Configurable workflows: https://docs.suitecrm.com/admin/administration-panel/workflow/

- Application license: https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- Current security and maintenance releases: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Humanetics implementation case study: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Licensing sources

- https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- https://suitecrm.com/pricing/

### Infrastructure sources

- https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The SuiteCRM 8.7.0+ guide documents SAML configuration and explicitly notes that IdP-initiated logout and POST binding to the logout service are unsupported. Review the stated session-timeout behavior and user mappings. Scope: SuiteCRM 8.7.0+ SAML; logout limitations do not imply login is unsupported. Source: https://docs.suitecrm.com/8.x/admin/configuration/saml/8.7.0-saml-configuration/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The SuiteCRM 8 guide documents downloading the prebuilt application package and completing server installation. Configure the compatible PHP/database stack, permissions and scheduled jobs for the selected release. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The SuiteCRM 8 installation and compatibility guides establish supported web/PHP/database combinations and recommend the pre-built installation package for production. They do not establish a quantitative whole-stack resource floor or an HA sizing profile. Scope: SuiteCRM 8 application, database and background processing; PHP limits are not whole-host memory requirements. Source: https://docs.suitecrm.com/8.x/admin/compatibility-matrix/ (reviewed 2026-11-20). Supporting source: Production installation package — https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/.

- License pricing: Documented. The vendor states there are no per-user software licence fees for SuiteCRM. Hosting, setup and support are paid services and must be budgeted separately from the open-source software. Scope: Self-hosted SuiteCRM core; managed hosting and optional services are not included. Source: https://suitecrm.com/pricing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v8.10.2, published 2026-07-31. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream SuiteCRM/SuiteCRM-Core release record; commercial editions and deployment packages may differ. Source: https://github.com/SuiteCRM/SuiteCRM-Core/releases/tag/v8.10.2 (reviewed 2026-11-14).






