
# Internal tools on Railway

Compare documented Internal tools deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/internal-tools/
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.

1 listing.


## NocoDB Self-Hosted

Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.

- Listing: https://launchinyourcloud.com/directory/nocodb/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- 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.
- Licensing model: source-available
- Installation: Run the official Docker image with persistent storage or use its documented Compose-based server installer.
- Architecture: Customer-operated application with persistent metadata/database services and optional connected databases
- Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
- Product website: https://nocodb.com/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Official Docker images run the NocoDB application on a customer-controlled host with persistent storage and a configured SQLite or PostgreSQL metadata backend; the server installer adds supporting services.


### Category fit

- no-code-databases: Spreadsheet-style database interface with linked records, views, forms and programmatic access.

- internal-tools: Interfaces build focused internal pages, dashboards and approval views on base data. The reviewed release limits Interfaces to licensed self-hosted Business plans and above.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 


### Cloud deployment evidence

- NocoDB community cloud installation methods (aws, gcp, digitalocean, railway): https://nocodb.com/docs/self-hosting/installation/community-methods
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

NocoDB's published adopter list names Accenture, Bosch and American Express. Its official GitHub discussion records actual exchanges between named users and maintainer o1lab about the 2026 license change, including critical feedback, while the release history shows continuing maintenance. These are adoption and participation signals; they do not establish which edition or hosting model any named organization uses.

Reviewed 2026-11-10.

- Vendor-published named organization adoption claims: https://nocodb.com/

- Observed user/maintainer discussion of the license change: https://github.com/nocodb/nocodb/discussions/12891

- Current maintenance releases: https://github.com/nocodb/nocodb/releases

### Sources

- Upstream project and capabilities: https://github.com/nocodb/nocodb

- Current upstream license: https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

- Internal Interfaces and self-hosted plan availability: https://nocodb.com/docs/changelog/2026.08.0

- Product functionality: https://nocodb.com/docs/product

- NocoDB 2026.10.2 release: https://github.com/nocodb/nocodb/releases/tag/2026.10.2

### Licensing sources

- https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

### Infrastructure sources

- https://github.com/nocodb/nocodb


### 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: Edition-dependent. The authentication guide documents SAML and OIDC providers and explicitly describes on-premises SSO configuration without Cloud DNS-domain verification. SSO is associated with paid self-hosted plans; optional password login alongside SSO has a separate on-premises setting. Scope: Paid self-hosted user federation; verify the selected Business/Scale/Enterprise entitlement rather than assuming Community includes SSO. Source: https://nocodb.com/docs/product-docs/account-settings/authentication (reviewed 2026-11-20). Supporting source: Self-hosted plans and licensing — https://nocodb.com/docs/self-hosting.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. NocoDB 2026.10.2 prevents shared views and dashboards from returning hidden fields, prevents forms from writing unrelated fields, hides workflow secrets from Editors and limits webhook request bodies. Upgrade and retest shares, forms, workflows and SSO. Scope: NocoDB self-hosted access controls documented in the 2026.10.2 release; no broader affected-version range was published. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream repository publishes an installer that generates a PostgreSQL/Redis/Traefik Compose stack. Re-running can upgrade the application; inspect the script, preserve secrets/data and control version changes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nocodb/nocodb (reviewed 2026-11-14). Deployment artifact: https://github.com/nocodb/nocodb/blob/develop/docker-compose/1_Auto_Upstall/noco.sh. Artifact reference: develop installer (moving).

- Minimum footprint / sizing: Documented. The self-hosting guide lists a minimum of 2 vCPU, 2 GB RAM and 10 GB disk, and a production recommendation of 4 vCPU, 8 GB RAM and 50 GB or more disk. Database, attachments, workload and replication require additional sizing. Scope: Single-server starting guidance; not a complete HA design or 1-TB storage allowance. Source: https://nocodb.com/docs/self-hosting (reviewed 2026-11-20).

- License pricing: Documented. The 2026.10.2 licence identifies the Sustainable Use License for the master/develop code: use and modification are limited to internal business, personal or non-commercial purposes, with restricted distribution. Commercial/self-hosted paid features require separate entitlements; this is not an unrestricted OSI open-source licence. Scope: Reviewed source-available terms; confirm commercial use and paid features for the intended deployment. Source: https://github.com/nocodb/nocodb/blob/2026.10.2/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. NocoDB 2026.10.2 was published November 19, 2026. It fixes shared-view, dashboard, form and workflow authorization boundaries, restores NC_SSO=oidc, changes SAML IdP-initiated RelayState handling and repairs air-gapped license refresh. Scope: Upstream NocoDB self-hosted release; paid-feature and license behavior remains edition-dependent. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/nocodb/nocodb/releases/tag/2026.10.1.




### Security and lifecycle reviews

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

- NocoDB 2026.10.2 access-control hardening (security-advisory): NocoDB 2026.10.2 prevents hidden-field disclosure in shares, unrelated form writes and workflow-secret disclosure to Editors, and caps webhook request bodies. Scope: NocoDB self-hosted behavior documented in the 2026.10.2 release; no universal affected-version range was published. Conditions: Public shares or dashboards, forms, Editor access to workflows, configured-key webhooks, OIDC or SAML determine exposure and upgrade impact. Action: Upgrade to 2026.10.2 or later and retest shares, forms, workflows, OIDC and SAML IdP-initiated login. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2; reviewed 2026-11-19.



