ChiefOnboarding

Self-hosted employee onboarding tasks, documents and workflows.

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Docker / Compose

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker / Compose
InfrastructureServers / containers
ChiefOnboarding application, database, persistent files and background jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The application documents OIDC provider configuration and role mapping through SSO_PROVIDERS and OIDC role settings, with separate Google login instructions. Verified-email handling, automatic account creation and administrator-role mappings require deliberate configuration.

Self-hosted application-user OIDC; role mapping is not evidence of SCIM provisioning · Source ↗ · Google user login and callback setup ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The v2.5.2 deployment guide supplies a published-image Compose example with PostgreSQL and an optional Caddy reverse proxy, persistent database storage and environment settings. Replace sample secrets and moving/old images. The repository-root Compose file uses a development build and local AWS emulation; it is a different workflow.

Versioned deployment-guide example, not the repository development stack · Deployment artifact ↗ (v2.5.2 documentation; example application/database latest tags require release selection) · Reviewed 2026-11-21

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The versioned deployment guide documents the application, PostgreSQL, proxy and persistent storage, but gives no quantitative production CPU/RAM or user-concurrency baseline. The development stack and its local AWS emulator are not a production capacity recommendation.

Deployment prerequisites confirmed; full production/HA sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

ChiefOnboarding; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v2.5.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

ChiefOnboarding upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Slack and mail integrations are external dependencies when enabled; onboarding workflows do not by themselves certify HR compliance.

Community & maintenance

The reviewed upstream contributor history includes GDay, matehsan, floschoepfer, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

HR & employee records management
Self-hosted employee onboarding tasks, documents and workflows.

Compare within HR & employee records management

  • Ever GauzyOpen-source business operations platform for people, projects, time and financial records.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Railway
    • Render
    • Heroku
    • Fly.io
    Customer-operated · Open Source / Open Core
  • FormKiQ HR and Employee Records Management Directory PublisherManage the governed document lifecycle for employee records with jurisdiction-specific retention, access controls, and audit trails.
    • AWS
    Customer-operated · Commercial Only
  • Frappe HR Self-HostedSelf-hosted HR software covering employee records, onboarding, leave, payroll and employee lifecycle events.
    • Railway
    Customer-operated · Open Source / Open Core
  • Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • IceHrm (Open Source)Customer-operated HR records, leave, attendance and people-management application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Laserfiche Self-HostedSelf-hosted document and records platform with forms and configurable business process automation.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • OpenCATSSource-available applicant tracking and recruiting records application.
    • Azure
    Customer-operated · Source Available
  • Oracle PeopleSoft HCM (BYOL)Licensed PeopleSoft human-capital and employee records applications in a customer OCI tenancy.
    • Oracle Cloud
    Customer-operated · Commercial Only

Showing 8 of 9 other listings in HR & employee records management. These products address related workflows; read their category-fit notes before comparing scope. See all of HR & employee records management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger ↗ · Hostinger

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

      ChiefOnboarding application, database, persistent files and background jobs. Slack and mail integrations are external dependencies when enabled; onboarding workflows do not by themselves certify HR compliance.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory