
# Vendor & supplier document management on Railway

Compare documented Vendor & supplier document management deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/vendor-supplier-document-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




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


## Provider guidance

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


### Project networking

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

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

2 listings.


## CISO Assistant Community

Community GRC platform with supplier risk assessments, evidence documents and third-party records.

- Listing: https://launchinyourcloud.com/directory/ciso-assistant/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy on Railway.
- 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.
- Product website: https://intuitem.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence.

Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Community GRC platform with supplier risk assessments, evidence documents and third-party records.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/ciso-assistant
  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.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ab-smith, nas-tabchiche, Mohamed-Hacene, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/intuitem/ciso-assistant-community/graphs/contributors

- Upstream project: https://github.com/intuitem/ciso-assistant-community

### Sources

- Railway Template: https://railway.com/deploy/ciso-assistant

- TPRM Guide: https://github.com/intuitem/ciso-assistant-community/blob/main/product-docs/guides/tprm.md

- AGPL-3.0 LICENSE.md: https://github.com/intuitem/ciso-assistant-community/blob/main/LICENSE.md

- GitHub Releases: https://github.com/intuitem/ciso-assistant-community/releases

- Community vs Pro - Feature Comparison — intuitem: https://intuitem.com/compare

- CISO Assistant FAQ — intuitem: https://intuitem.com/faq

### Licensing sources

- https://github.com/intuitem/ciso-assistant-community/blob/main/LICENSE.md

### Infrastructure sources

- https://railway.com/deploy/ciso-assistant


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 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. Community includes SAML and OIDC single sign-on. Configure the provider, role mapping and recovery access for the selected deployment. Scope: CISO Assistant Community versus Pro; current vendor comparison and FAQ. Source: https://intuitem.com/faq (reviewed 2026-11-19). Supporting source: Community/Pro feature comparison — https://intuitem.com/compare.

- SCIM provisioning: Explicitly unsupported. The vendor specifies SCIM group-based provisioning as a Pro feature; it is not included in the selected Community edition. Scope: CISO Assistant Community versus Pro; current vendor comparison and FAQ. Source: https://intuitem.com/faq (reviewed 2026-11-19). Supporting source: Community/Pro feature comparison — https://intuitem.com/compare.

- Compliance attestations: Not researched.

- Security controls: Documented. The vendor documents TOTP and hardware-key MFA in Community; Pro-only audit and permission features are separate. Scope: CISO Assistant Community versus Pro; current vendor comparison and FAQ. Source: https://intuitem.com/faq (reviewed 2026-11-19). Supporting source: Community/Pro feature comparison — https://intuitem.com/compare.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Railway template defines the Community backend/frontend, database and supporting services. Pin compatible versions, keep secrets stable and validate durable attachments, queues and any AI service before production. Scope: CISO Assistant Community Railway deployment template, separate from Pro and the TPRM feature guide. Source: https://railway.com/deploy/ciso-assistant (reviewed 2026-11-19). Deployment artifact: https://railway.com/deploy/ciso-assistant. Artifact reference: Community Railway template; latest backend/frontend image tags are moving references.

- Minimum footprint / sizing: Documented. The v4.3.3 on-premises prerequisites specify four CPU cores, at least 16 GB RAM and 10 GB storage, with extra capacity for evidence files and lower specifications only for testing. Database choice, workers, concurrency, backups and HA remain deployment-specific. Scope: CISO Assistant v4.3.3 upstream on-premises baseline, not reference-workload HA sizing. Source: https://github.com/intuitem/ciso-assistant-community/blob/v4.3.3/product-docs/installation/prerequisites.md (reviewed 2026-11-21).

- License pricing: Edition-dependent. AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence. Scope: CISO Assistant Community; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/intuitem/ciso-assistant-community/blob/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v4.3.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: CISO Assistant Community upstream application; verify compatibility with the selected package. Source: https://github.com/intuitem/ciso-assistant-community/releases/tag/v4.3.3 (reviewed 2026-11-19).







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



