HR & employee records management on Railway

Employee files, onboarding documents and record lifecycle controls.

2 documented options on Railway. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Ever GauzyAWS, Azure, Google Cloud, DigitalOcean, Heroku, Fly.io, Railway, RenderCustomer-operated
Servers / containers
Open Source / Open Core

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Application platform deploymentCustomer 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 and evidence

The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.

  • AWS Guide — 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.

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

  • Azure Guide — 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.

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

  • GCP Guide — 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.

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

  • DO Guide — 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.

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

  • Heroku Guide — 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.

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

  • Fly.io Guide — 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.

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

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

    Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Render Guide — 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.

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

Cloud evidence reviewed 2026-11-19

Frappe HR Self-HostedRailwayCustomer-operated
Servers / containers
Open Source / Open Core

Open-source; verify applicable component license and support terms

Frappe installation scripts; Bench and Docker development setups documentedCustomer or implementation partner maintains infrastructure, security, backups and software updates.
Scope and evidence

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.

  • Frappe HR self-hosted deployment on Railway — 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.

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

  • Source for the Frappe HR Railway image — 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.

    Community template · 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

Ever Gauzy

Open-source business operations platform for people, projects, time and financial records.

The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.

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

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

Frappe HR Self-Hosted

Employee records, onboarding, leave, payroll and exit lifecycle are documented; legal hold, controlled disposition and jurisdiction-specific personnel-file retention were not established.

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.

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

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