Out Of Office, Holiday Manager
OOOhm is a calm leave tracker for small teams. Ask for days in one sentence, approve them from your inbox, and see who's out at a glance. There's no HR suite attached.
Playing a few examples, counted Monday to Friday with US holidays. Change any part of the sentence to try your own.
The tour. A request, an approval and the calendar, recorded in the real app. 46 seconds, no sound.
How it works
01
Pick a type and two dates. OOOhm counts the working days as you go and tells you what you’ll have left, before you send anything.
02
Every request says who else is off on those days, or that nobody in the team is. Approve or decline in one click, with a reason if you want one. It’s on their dashboard straight away.
03
On the calendar, press on the first day and let go on the last. Weekends and company holidays are hatched, and they never count against anyone.
04
One list for the month, filtered by team. Your own year on one page. And if you live in your calendar app, subscribe and it stays up to date there.
Balances
Each person gets a yearly allowance per leave type, and it resets on January 1. Days are counted to one decimal, so a half day is 0.5. Nothing is rounded behind anyone’s back.
What happens to the days nobody took is up to you, per leave type. Carryover is off unless you turn it on.
PTO for 2026
6 days left of 15.
For managers
The request email carries everything you need to decide, and an Approve link signed for you alone. It stops working once the request is decided. Every decision, from anywhere, lands in the audit log with your name on it.
From OOOhm
Subject Lena Park asked for Dec 21 to Dec 23
Lena Park asked for PTO (Scheduled Time Off), Mon, Dec 21 to Wed, Dec 23, 2026: 3 days.
“Visiting my parents in Busan”
Aisha Khan is off then too.
Approved. Lena gets an email, and her calendar feed updates.
Audit log
Each row names a person, a person through an import or the email link, their API key, or a system job. Nothing is anonymous.
Quiet by design
Nobody signs up on their own. An admin invites people, and they sign in with an emailed link, or with Google if you turn it on.
Set your working days and company holidays once. Add a holiday later and every request on that date is recounted, and the people affected get an email.
Each decision and each balance change writes an audit row that names who made it. Export a person’s history as CSV before you ever delete them.
Each screen does one thing. Pick a look for the whole company from nine themes and five layouts, including one with larger text and 48 px targets.
Developers
OOOhm writes a domain event in the same transaction as every change, so nothing happens that your other tools can’t hear about. Webhooks are signed and retried; the REST API reads everything else.
Self-hosting
The database, the app, a background worker and a mail catcher, with migrations on start.
docker compose up
Your own server, Neon, Supabase or RDS. Pooled connections are detected for you. On Vercel, migrations run as part of the build.
pnpm db:migrate && pnpm build && pnpm start
Embedded Postgres in the same process, for a small team on a small box.
pnpm start:embedded
Moving from TimeOff.Management? One command brings over people, leave types, holidays and the whole history, and it only commits when every balance matches. How the import works
Where it’s at
We made OOOhm at Chykalophia because we wanted time off to feel like a two-minute job again. It runs our team first, and it’s ready for yours.
The code is source-available under the Functional Source License (FSL-1.1-ALv2). Read it, change it and run it for your company. Anything except offering a competing product is fine, and each release becomes Apache 2.0 two years after it ships.
No. It tracks time off, and nothing else. It sends events if you want your HR tools to know.
Small teams: one company per install, departments to group people, and one manager for each person.
An invite from an admin. Sign-in is a link by email, or Google if you set it up. There are no passwords to forget.
Yes, the morning or the afternoon of a single day. It counts as 0.5.
In the Postgres database you run it on, or in a folder on the machine in embedded mode. Nothing leaves your server except the emails people expect and the webhooks you add.