Hirio

02 / Decisions

1. DEC-01 One database, with the tenant filter in one place

   Every new client company needed its own dashboard and landing page, without setup work for each one.

   ✕ Turned down

   A separate schema or database per client company

   ✓ Chose

   Kept all client companies in one database, separated by a tenant_id column. A middleware layer adds the tenant filter to every query, so no handler has to remember it.

   Cost

   Clients share tables. The middleware is the one place that keeps their data apart, so it must stay correct.

   Proof

   A new client company gets its own dashboard and landing page automatically, with no new database to create.

03 / What I did

1. 01

   Built Hirio, a multi-tenant applicant tracking system where each new client company gets its own dashboard and landing page automatically.

2. 02

   Covered job posting, applicant tracking, analytics, digital signatures, and email invitations, synced in real time with Privy apps.

04 / Stack

• Go
• Docker
• Redis
• Amazon S3
• Pub/Sub
• PostgreSQL

05 / Screenshots