Launching today
Chronock
Scheduling and calendar sync, all in one
43 followers
Scheduling and calendar sync, all in one
43 followers
Chronock combines scheduling and cross-calendar sync in one workspace. It checks availability across connected Google and Outlook calendars, turns open time into a booking page, and syncs events between work, personal, and project calendars to prevent double bookings. Guests see only bookable times, while you can review every connected event in one Integrated Calendar. Start free with no credit card.
Chronock
Hi Product Hunt 👋
I’m Takahiro Ikeuchi, a solo product engineer from Tokyo 🗼 and the maker of Chronock.
I started building Chronock after repeatedly running into the same problem in two different roles.
As a CTO, I spent a lot of time coordinating recruiting interviews. As a coach, I also needed to schedule meetings with people outside my organization. Native calendar features often felt too limited, while broader scheduling suites could be difficult to justify on price. At the same time, keeping my work, personal, and project calendars aligned often meant paying for and managing another tool.
That led me to a simple idea: scheduling and calendar sync are not really separate problems. They are both about keeping your availability trustworthy.
Chronock brings them together in one workspace:
- Create booking pages that check your Google and Outlook calendars
- Sync events between work, personal, and project calendars
- Review connected events in one Integrated Calendar
- Find and share open-time candidates when a booking link is not the right fit
As a Japanese maker, I also wanted multilingual support—including Japanese—to be part of the product from the beginning, rather than an afterthought.
I wanted to create a focused and accessible utility without treating quality as optional.
I’ve spent more than 10 years working as a full-stack engineer and now describe myself as a product engineer. I’m interested in the entire process, from UI design and frontend development to backend systems and cloud infrastructure.
Chronock is built AI-natively. I use coding agents such as Codex and Claude Code throughout development, but I don’t equate AI-native development with handing off engineering judgment. Architecture, design, security, testing, and the final quality bar still require deliberate care.
For me, the real value of AI is not only speed. It helps a very small team avoid unnecessary compromises and stay close to the people using the product.
Chronock is still at an early stage, and this launch is an opportunity to learn. There’s a free plan, and no credit card is required.
I’d especially love your feedback:
- What is the hardest part of managing multiple calendars today?
- Do you prefer sharing a booking link or proposing a few specific times?
- Is anything about Chronock’s setup or positioning unclear?
Thank you for taking a look. I’ll be here throughout the launch and would be happy to answer any questions.
Chronock
@tehreem_fatima5 Thank you — I really appreciate the thoughtful answer! That distinction between proposing a few times for high-touch conversations and sharing a booking link for quick team syncs is exactly why I believe both approaches matter.
Chronock currently supports English, Japanese, French, German, Traditional Chinese, and Korean. Multilingual support isn't an afterthought for me. I want people across different languages, cultures, and ways of working to feel equally considered, and I hope to keep expanding that thoughtfully rather than treating translation as a checkbox.
Thanks again for noticing and supporting that part of the vision! 🌏
honest answer to your question: the hardest part for me isn't double-booking, it's the placeholder events. I sync work -> personal so my partner sees when I'm busy, but the synced copy is just a blank "Busy" block with none of the context, so I still end up manually checking the original calendar half the time anyway. the sync solved discoverability, not usefulness. on the technical side, since you're syncing between work/personal/project calendars in both directions, how do you stop that from creating a loop - a busy-block synced from A to B that then gets picked up and re-synced back into A as a second, slightly-different event?