Internal tools on Railway

Low-code applications, operational interfaces and internal business tools.

1 documented option on Railway. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
NocoDB Self-HostedAWS, Google Cloud, DigitalOcean, RailwayCustomer-operated
Servers / containers
Source Available

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.

Run the official Docker image with persistent storage or use its documented Compose-based server installer.Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
Scope and evidence

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.

  • NocoDB community cloud installation 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.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Deployment evidence and category fit

NocoDB Self-Hosted

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.

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.

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

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

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.

Plan this deployment

Account boundary: Railway workspace, project and environment; platform-managed infrastructure. Access: Workspace/project access and scoped deployment tokens. Network: Project/environment private networking with separately exposed public services.

Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings