This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
ChronoShield API
A REST API that catches timezone bugs before they ship
REST API that validates, resolves, and converts datetimes with all the DST and IANA edge cases handled. Catches the bugs that silently corrupt data — spring-forward gaps, fall-back overlaps, +5:45 offsets, stale tzdata. SDKs on npm and PyPI. Free tier.
Hey Product Hunt 👋
Solo dev here. I built ChronoShield because I kept hitting the same class of bug in every project: code that "works" all year then silently breaks for an hour on DST transition day.
What it does — four endpoints:
• /validate — is this local datetime real in this zone? (catches DST gaps)
• /resolve — given an ambiguous or invalid datetime, what UTC instant does it map to? (configurable policy)
• /convert — UTC → any target zone
• /version — which IANA tzdata release am I serving? (surprisingly useful)
Handles the fun stuff: spring-forward gaps, fall-back overlaps, non-whole-hour offsets (Kathmandu +5:45, Chatham +12:45), 30-minute DST shifts (Lord Howe), historical zone rules, and recent legislative changes (BC's permanent-DST law is live in our data as of IANA 2026b).
What I'm proudest of (technically): I just shipped a refactor that decouples tzdata from the Node.js runtime version. Most APIs in this space are stuck on whatever tzdata their runtime ships with. ChronoShield can ship new IANA releases the same week they drop — no Node bump needed.
SDKs published yesterday:
• npm install chronoshield
• pip install chronoshield
Pricing:
• Free: 1k req/mo (no card)
• Pro: $19/mo for 100k req
• Enterprise: custom
I built this entirely solo, on nights and weekends. Today's launch is the start, not the finish — would genuinely love feedback on what's missing, what's confusing, or what you'd want next.
Happy to answer anything about the stack (Fastify/TS/Postgres/Railway), the tzdb decouple architecture, the parity test harness (~30k zone×timestamp checks gate every deploy), or the weirdest DST rules I've found.
→ chronoshieldapi.com
About ChronoShield API on Product Hunt
“A REST API that catches timezone bugs before they ship”
ChronoShield API was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #89 on the daily leaderboard. REST API that validates, resolves, and converts datetimes with all the DST and IANA edge cases handled. Catches the bugs that silently corrupt data — spring-forward gaps, fall-back overlaps, +5:45 offsets, stale tzdata. SDKs on npm and PyPI. Free tier.
On the analytics side, ChronoShield API competes within API, Open Source, Developer Tools and GitHub — topics that collectively have 719.4k followers on Product Hunt. The dashboard above tracks how ChronoShield API performed against the three products that launched closest to it on the same day.
Who hunted ChronoShield API?
ChronoShield API was hunted by Mike Mait. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of ChronoShield API including community comment highlights and product details, visit the product overview.
Mike Mait