Inbin was extracted from a real product after a year of running the same email pipeline in production. It exists because we got tired of writing it the fourth time.
We were building a real-estate app that ingested listing emails from a dozen different senders. Redfin, Zillow, MLS forwards, county sheriff notices. Each one arrived with a different HTML skeleton, a different date format, a different way of putting the price where the address should be. We wrote a Lambda. Then a parser. Then a prompt. Then a fixtures directory. Then a retry queue. Then a hallucination guard. Then a redelivery UI.
At some point we noticed the parser had more code than the product it fed. That’s when we started building Inbin on the side, quietly, then cut over.
Every serious product ends up parsing email. It’s the last unstructured data source with universal reach. No API to negotiate. No rate limit to fight. No OAuth flow. If a human can subscribe to it, your product can ingest it.
We think that’s a primitive, not a workaround. The same way Stripe made "accept money" a one-line dependency, Inbin wants "accept email as structured data" to be one line. Point an inbox at anything, declare a schema, get typed events on your webhook. Everything else is plumbing.
Private beta. The full ingest, extract, retry, dead-letter pipeline is live. So is the MCP server, so agents can read your parsed events directly. Our first customer is the product Inbin was extracted from. Second and third are on the way.
Billing is off. Every beta account is hand-onboarded. When we turn billing on, beta usage gets grandfathered.
Email is our first input. It’s the one every serious product ends up needing, so we started there. The same primitive (declare a schema, receive typed events on a webhook) works for RSS feeds, PDFs dropped in a bucket, forms scraped off a website, and CSV uploads. Those are next, in that order, when the email surface is boring.
The bet is simple. Every AI application needs context, and most valuable context is still trapped in unstructured inputs. Inbin is the layer that frees it.
Not a marketing sender. Not a transactional API. Not an email client. Not a lead-gen CRM. Not a full inbox with folders and threads. We only receive, and we only turn what we receive into JSON. Anything else is out of scope.
Solo, for now. Building in public. Reach us at hello@inbin.dev.