Third-party API sandboxes are flaky, incomplete, and drift from production without warning. pikopod is an open-source Go CLI that simulates API sandboxes locally and detects drift, flagging when a real API stops matching what your integration expects, before users hit errors. Mocking tools fake responses; pikopod also checks them against the real API. Built from years of maintaining payment integrations. Apache-2.0, installable via Homebrew.
Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?
Maker
We use Vercel to host pikopod's website. As an open-source developer tool with a solo founder, I needed the site to cost almost no time to maintain. Git-based deploys mean every push to the site repo goes live in seconds, with no infrastructure to manage. That let me keep the website in step with each CLI release, so the landing page always reflects what pikopod actually does today, and spend my time on the drift engine instead of on hosting.
Report
Maker
๐
Hey Product Hunt ๐
I'm Tobe, a backend engineer who has spent years building payment integrations. The recurring nightmare: vendor sandboxes that are down, don't match production, or change with no changelog. Tests pass, prod breaks.
pikopod fixes that in two ways:
๐งช Local sandbox simulation: develop and test integrations without depending on a vendor's flaky sandbox
๐ Drift detection: get told when a real API stops behaving the way your integration expects, before your users find out
It's open source, written in Go, and pre-v1, so your feedback will genuinely shape it.
I'd love to hear:
- Which API has burned you the most with silent changes?
- What would make you adopt this in your CI?
I'll be here all day answering questions. A โญ on GitHub helps too!