Scheduling Across Time Zones Without Leaving the Browser

I spent the last few weeks building a tool I actually use myself. It started as a frustration with existing scheduling apps. They all feel heavy. They require accounts, they require integrations, and most importantly, they require your data to leave your device to be processed on a server. For a developer who cares about privacy and latency, that friction is unacceptable.

So I built TimeForge.

It’s a scheduling utility that helps you find the best meeting times across every timezone, but with a twist: it runs entirely in your browser using WebGPU. Nothing is uploaded. There is no backend server processing your calendar data. If you disconnect your internet after the page loads, the tool still works.

The Problem with Current Tools

When I need to schedule a meeting with a colleague in Tokyo and another in San Francisco, I usually end up with three tabs open: my calendar, a world clock widget, and a mental map of working hours. I have to manually calculate the overlap. It’s tedious.

Most online schedulers solve this by asking you to sign up and sync your Google or Outlook calendar. That’s fine for teams, but it’s overkill for a quick "when are you free?" check. Plus, you’re handing over your schedule data to a third party. I wanted a tool that respects the boundary between my local machine and the cloud.

How It Works

TimeForge is a single-page application. When you open it, you input your time zone and your working hours. You then add the time zones of the people you want to meet with. The interface renders a visual overlay of these time zones, highlighting the windows where everyone is technically "awake" or "working."

The magic happens in the rendering engine. Because it uses WebGPU, the heavy lifting of calculating and rendering these complex time overlays happens on your GPU. This means the UI remains buttery smooth even if you add a dozen time zones. There is no lag because there is no network request waiting for a server to respond.

Privacy by Design

The core philosophy here is data locality. Your time zone preferences and working hours never leave your browser. If you use the tool offline, you can still plan your week. If you use it online, you can share a link, but that link contains only the configuration parameters, not your personal calendar events unless you explicitly choose to export them.

This approach also makes the tool incredibly fast. There is no loading spinner while it "syncs." It just updates.

The Technical Stack

I built this with a focus on minimalism. The frontend is vanilla JavaScript with WebGPU for the rendering pipeline. This was a deliberate choice to avoid the bloat of heavy frameworks for a utility that doesn’t need complex state management. The UI is clean and functional, designed to be used in seconds, not minutes.

One of the challenges was handling daylight saving time transitions across different regions without a server-side library. I implemented a lightweight local algorithm that handles these edge cases, ensuring that the "working hour" overlays are accurate year-round.

Why It’s Paid

TimeForge is a paid tool, though it offers a 7-day trial so you can see if it fits your workflow. I chose a paid model because it allows me to keep the infrastructure lean and focused on quality rather than scaling for millions of free users. There are no ads, and no data mining. The cost supports ongoing development and maintenance of the tool.

Who Is This For?

If you are a developer, designer, or remote worker who frequently coordinates with people in different time zones, this tool might save you a few minutes per week. It’s not a calendar replacement. It’s a tactical utility for finding that elusive overlap when you’re planning a quick sync.

It’s particularly useful for:

• Remote teams with members in disparate time zones.
• Freelancers coordinating with clients across the globe.
• Anyone who values privacy and wants to avoid signing up for another SaaS platform.

Try It Out

You can see it in action at TimeForge.

I’m still iterating on the UI and adding small features based on how people actually use it. If you have thoughts on the design or the functionality, I’d appreciate hearing them. I’m always looking for ways to make remote coordination less painful.