
# HR & employee records management on Railway

Compare documented HR & employee records management deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/hr-employee-records-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.


## Ever Gauzy

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

- Listing: https://launchinyourcloud.com/directory/ever-gauzy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, fly, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Ever Gauzy application/API, database and required workers using provider-specific deployment recipes.
- 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://gauzy.co
- 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 supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.

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

Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

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

- hr-employee-records-management: Open-source business operations platform for people, projects, time and financial records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/azure-deployment/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/gcp-deployment/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/ (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/heroku-deployment/ (checked 2026-11-19). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/flyio-deployment/ (checked 2026-11-19). 

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

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/render-deployment/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guide (aws): https://docs.gauzy.co/deployment/cloud/aws-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.gauzy.co/deployment/cloud/azure-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.gauzy.co/deployment/cloud/gcp-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Guide (digitalocean): https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Heroku Guide (heroku): https://docs.gauzy.co/deployment/cloud/heroku-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Fly.io Guide (fly): https://docs.gauzy.co/deployment/cloud/flyio-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

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

- Render Guide (render): https://docs.gauzy.co/deployment/cloud/render-deployment/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes evereq, rahul-rocket, adkif, 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/ever-co/ever-gauzy/graphs/contributors

- Upstream project: https://github.com/ever-co/ever-gauzy

### Sources

- AWS Guide: https://docs.gauzy.co/deployment/cloud/aws-deployment/

- Azure Guide: https://docs.gauzy.co/deployment/cloud/azure-deployment/

- GCP Guide: https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- DO Guide: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- Heroku Guide: https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- Fly.io Guide: https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- Railway: https://railway.com/deploy/ever-gauzy

- Render Guide: https://docs.gauzy.co/deployment/cloud/render-deployment/

- AGPL-3.0 LICENSE: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

- Releases v111.250.0: https://github.com/ever-co/ever-gauzy/releases

### Licensing sources

- https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

### Infrastructure sources

- https://docs.gauzy.co/deployment/cloud/aws-deployment/

- https://docs.gauzy.co/deployment/cloud/azure-deployment/

- https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- https://railway.com/deploy/ever-gauzy

- https://docs.gauzy.co/deployment/cloud/render-deployment/


### 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. The vendor documents application-user OAuth login with Google, GitHub, Facebook, Twitter, LinkedIn and Microsoft, including registered clients and instance callback settings. Provider login and the application JWT session/API mechanism are distinct configuration layers. Scope: Upstream application-user social OAuth configuration; not proof of arbitrary enterprise SAML or SCIM support. Source: https://docs.gauzy.co/authentication/social-auth/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official AWS guide provides service architecture, CLI provisioning and ECS task configuration for the application, PostgreSQL, Redis and S3. Configure images, task resources, secrets, networking and persistence for production; the illustrative commands are not a supplied complete CloudFormation stack. Scope: Vendor-documented customer AWS deployment recipe; complete production configuration and version alignment require review. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The AWS guide illustrates two Fargate tasks at 1 vCPU/2 GB each, a db.t3.medium database with a 50-GB provisioning example and cache.t3.micro Redis. These are example service sizes from the guide, with file storage and load balancing additional; its advertised cost table is not a reference-workload quote. Scope: Published AWS example allocations, not a 100-user/1-TB HA minimum or current operating-cost estimate. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (reviewed 2026-11-21).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Ever Gauzy; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Frappe HR Self-Hosted

Self-hosted HR software covering employee records, onboarding, leave, payroll and employee lifecycle events.

- Listing: https://launchinyourcloud.com/directory/frappe-hr/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source; verify applicable component license and support terms
- Licensing model: open-source
- Installation: Frappe installation scripts; Bench and Docker development setups documented
- Architecture: Customer-operated Frappe application and database
- Operations: Customer or implementation partner maintains infrastructure, security, backups and software updates.
- Product website: https://frappe.io/hr
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The official Frappe HR repository contains a GPLv3 license. Its pricing page currently labels self-hosting AGPL-3.0; both are open-source licenses, so the model remains open source while the exact version-specific obligations should be checked against the chosen release.

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

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

### Deployment boundaries


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


### Cloud deployment evidence

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

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


### Sources

- Self-hosting options: https://frappe.io/hr/pricing

- Employee records: https://docs.frappe.io/hr/employee

- HR modules and lifecycle: https://docs.frappe.io/hr/introduction

- Official installation repository: https://github.com/frappe/hrms

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

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

- Frappe HR v16.60.0 release: https://github.com/frappe/hrms/releases/tag/v16.60.0

- Frappe HR SQL injection advisory: https://github.com/frappe/hrms/security/advisories/GHSA-jfmr-9jv9-mrw4

- Frappe HR cross-employee data advisory: https://github.com/frappe/hrms/security/advisories/GHSA-wfc6-cw72-cvhx

### Licensing sources

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

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

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

### Infrastructure sources

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

- https://github.com/frappe/hrms


### Buyer diligence


Research coverage: 7/12 fields (58%); 5 documented, 2 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 shared Frappe login system accepts external OAuth/OpenID logins configured with Social Login Key, including Google and Office 365. Configure the provider and permitted users for the installed Frappe version; this is framework login, not a separate application-specific SAML implementation. Scope: Self-hosted Frappe-based application login; provider configuration and matching framework/app versions required. Source: https://docs.frappe.io/framework/user/en/guides/integration/social_login_key (reviewed 2026-11-20). Supporting source: Frappe login handlers — https://github.com/frappe/frappe/blob/develop/frappe/integrations/oauth2_logins.py. Supporting source: Application framework dependency — https://github.com/frappe/hrms/blob/develop/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Frappe HR advisories cover an SQL injection issue and cross-employee HR data access. Upgrade to a fixed or later supported Frappe HR release and review employee-data permissions. Scope: The SQL issue is fixed in 14.38.2, 15.64.0, and 16.18.0. The cross-employee issue is fixed in 15.58.3 and 16.4.3.. Source: https://github.com/frappe/hrms/security/advisories/GHSA-jfmr-9jv9-mrw4 (reviewed 2026-11-18). Supporting source: Cross-employee data advisory — https://github.com/frappe/hrms/security/advisories/GHSA-wfc6-cw72-cvhx.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The HRMS repository provides a Docker development setup with example administrator credentials. Do not use that recipe as a production baseline; production packaging must include compatible Frappe/ERPNext/HRMS apps. Scope: HRMS development artifact; production deployment requires separate configuration. Source: https://github.com/frappe/hrms (reviewed 2026-11-14). Deployment artifact: https://github.com/frappe/hrms. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The underlying Frappe Docker ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD for a small single bench. It does not size this additional application or establish its whole-stack production/HA minimum; application jobs, database, attachments and replicas still require sizing. Scope: Platform recipe only, not an application-specific Frappe HR/Lending benchmark or Frappe Cloud hosting allocation. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20). Supporting source: Application dependencies — https://github.com/frappe/hrms/blob/develop/README.md.

- License pricing: Documented. The vendor states Frappe HR is free and open source for self-hosting. This does not include infrastructure, email, security, backups, implementation or ongoing operation. Scope: Self-hosted Frappe HR software; hosted-service plans and operating costs are separate. Source: https://frappe.io/hr/pricing (reviewed 2026-11-14).

- Operating cost estimate: Sources checked — unresolved. The pricing FAQ gives an illustrative VPS starting cost but explicitly adds email, security, backups and maintenance. It does not establish a workload/region-specific total operating estimate. Scope: Vendor illustration, not a complete infrastructure-plus-operations estimate. Source: https://frappe.io/hr/pricing (reviewed 2026-11-14).

- Release snapshot / cadence: Documented. Frappe HR v16.60.0 was published November 17, 2026. It requires Frappe v16.60 and identifies five breaking changes; validate custom employee, letter, and dashboard workflows. Scope: Upstream Frappe HR v16 release. Source: https://github.com/frappe/hrms/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.

- Frappe HR SQL injection and employee-data access fixes (security-advisory): Frappe HR advisories cover an SQL injection issue and cross-employee HR data access. Scope: The SQL issue is fixed in 14.38.2, 15.64.0, and 16.18.0. The cross-employee issue is fixed in 15.58.3 and 16.4.3. Conditions: Applicability depends on the affected feature, permissions, and installed branch. Action: Upgrade to a fixed or later supported Frappe HR release and review employee-data permissions. Source: https://github.com/frappe/hrms/security/advisories/GHSA-jfmr-9jv9-mrw4; reviewed 2026-11-18. Supporting source: Cross-employee data advisory — https://github.com/frappe/hrms/security/advisories/GHSA-wfc6-cw72-cvhx.



