Runs on Kynth.
Kynth runs its own company first. The back office behind this business — the invoices, the reminders, the API — is the product itself, in production, every day. These are the real numbers from that use, regenerated from the database. Last generated July 10, 2026.
The company's own receivables, managed in Kynth Invoices — the founder's production workspace, not a demo.
4 in the last 30 days. Every one went to a real client about a real invoice.
Scheduled follow-ups waiting to fire — the chase runs whether or not anyone is at the keyboard.
3,883 credits burned from Kynth's own wallets — the same metered credits customers buy.
Endpoints the company has hit running its own operations — dogfooding as continuous integration.
Every entry on /shipped is a real deploy. Latest: July 9, 2026.
Customer zero
Before Kynth asks anyone to run their business on it, it runs its own. The scope today is honest: the apps genuinely dogfooded are Kynth Invoices — where the company's real receivables live and real reminders go out — and the Kynth Core API, which the company consumes on the same credit meter it sells. As more of the back office moves onto more of the apps, the numbers here grow with it.
Nothing here is uptime theater either. The reliability claim is plain: these apps process the company's own money and own operations, so an outage hurts us before it hurts you. The deploy log is public, and the numbers on this page come straight from the production database.
What's deliberately missing
No revenue figures. No customer or user counts. This page publishes activity and reliability — what the product actually does in production — and nothing that could be dressed up. That restraint is the point: numbers you can't inflate are the only kind worth publishing.