About TimeyKit

Fast, reliable, simple time tools built by people who needed them first.

How the project started

TimeyKit was founded by two former SRE colleagues who kept tripping over the same scheduling headaches—coordinating on-call bridges, checking whether colleagues in Singapore were awake, and translating world cup fixtures into local times while they were relaxing having a drink in the pub. We built the first tool from scratch as a weekend sanity project, used AI to accelerate some boilerplate, and kept the human focus on engineering quality and predictable behavior.

Every new tool comes from a real incident or planning session. When we hit a time-related problem twice, we solve it properly and publish the result so the next team doesn’t have to guess.

What TimeyKit is today

A toolkit of web utilities: timezone overlap planners, DST-proof schedules, world clocks, date math helpers, and wallboards for events like WC26. Everything runs client-side in your browser—no logins, no accounts, no user-data collection. Tools load quickly, answer the question, and get out of your way. Similar tools existed, but they were overbuilt for what we needed on real incident bridges.

Who we build for

Our approach

Fast, reliable, simple. We run on Cloudflare Pages with lightweight HTML/CSS/JS, versioned shared chrome, and no backend dependencies. When we need help, we lean on AI for drafting copy or scaffolding, but every release is tested by the same engineers who will use it at work. We keep tools free, avoid nagging modals, and prefer boring solutions to fragile cleverness.

The WC26 story

The WC26 suite started as a pub conversation about mapping fixtures to local time without scrolling a spreadsheet. We sketched a wallboard on a napkin, built it that weekend, and realized other bars and living rooms wanted the same “set it and forget it” display. That DNA carries through every new wallboard we add.

Philosophy & commitments

How we think about privacy

Minimal data collection keeps TimeyKit trustworthy. Read the privacy policy for details on logs, optional analytics, and how advertising is handled if/when it’s enabled.

How to reach us

Questions, feature requests, or bug reports? Contact us. We reply as fast as our day jobs allow. You can also follow along via the changelog and roadmap.