How the project started
TimeyKit is run by Paul J. and Matt A.—ex-SRE and ops leads who were tired of chasing overlap windows on incident bridges, translating fixtures for pubs, and explaining DST for the hundredth time. The first tool was a weekend triage project; we still keep the stack boring on purpose and only ship what we’d rely on at 02:00.
Every new feature starts with a real outage, rehearsal, or travel mess. If it burns us twice, we build a tool, test it on our own crews, and publish it so the next team doesn’t burn time on guesswork.
What TimeyKit is today
A toolkit of browser utilities—timezone overlap planners, DST helpers, wallboards, UTC clocks, date math—built from the same checklists we use at work. Everything runs client-side and never asks for an account; your inputs stay in your browser. Optional analytics and advertising slots may load per the privacy policy, so consent prompts or cookies can still appear even though the tools themselves stay local. The goal is to load fast, answer the question, and let you get back to the call. We’re not trying to become a bloated collaboration suite or a dashboard you have to train people on.
Who builds TimeyKit
Paul (SRE/infra) and Matt (operations lead) ship every release. We’ve spent years running production systems, event ops, and remote teams, so the tone here comes from “why is this still painful?” moments, not a content calendar. TimeyKit operates under Useful Nonsense LTD—our small company that exists so we can keep the tools independent, maintained, and accountable.
Who we build for
- Remote teams handing off production systems across continents.
- SREs, support crews, and newsroom coordinators who need overlap windows.
- Sailors, travelers, and aviation nerds who live on UTC but report locally.
- Project managers who want date math answers without mega spreadsheets.
- Pubs and venues that need honest wallboards for live events.
Our approach
Fast, reliable, simple. The stack lives on Cloudflare Pages with lightweight HTML/CSS/JS and versioned shared chrome; no backend dependencies, no user accounts, no dark patterns. AI helps with scaffolding, but the humans who need these tools in production test them before they ship. We publish changelog and roadmap updates so you can see what’s coming.
The WC26 story
The WC26 tools started because we wanted to show fixtures in local time without juggling spreadsheets in a noisy pub. A napkin sketch became a wallboard, friends asked for copies, and the same playbook now powers every event board we publish.
Philosophy & commitments
- No accounts or paywalls—tool inputs persist locally while analytics/ads only run the way the privacy policy and your consent choices allow.
- If a tool breaks for us, the fix ships to everyone else.
- Changelog + roadmap stay public so you can see what changed and what’s next.
- Every tool links to a practical guide so you can learn it and deploy it in minutes.
How we think about privacy
Minimal data collection keeps TimeyKit trustworthy. Expect a consent banner wherever analytics or ads need cookies; those scripts only run after you decide. Read the privacy policy for details on logs, optional analytics, and how advertising is handled if/when it’s enabled.
TimeyKit is still independent, maintained alongside our day jobs, and optimized for practical fixes over product fluff. If we wouldn’t rely on a feature during a 2 a.m. incident, it doesn’t ship.
Where to go next
Need tactics? Head to Learn. Want real workflows? See the use-cases. Ready to solve something right now? Open the Timezone planner, World Clock, or any tool that fits your situation. Feedback is always welcome via contact—it goes straight to us.