PurePrep
Turns any recipe link into just the title, ingredients and steps — then gets out of the way while you cook. No ads, no ten-paragraph backstory, no pop-ups.
The recipe is the small part of the page
A modern recipe page is mostly not the recipe. There is a life story, a full-bleed hero photo, a newsletter wall, a cookie banner, and an advert that reflows the page every time you scroll. The six lines you actually need are somewhere near the bottom, and they dim to black the moment your hands are covered in flour.
PurePrep is the opposite bet. You paste a link, it keeps only the title, the ingredients and the steps, and it saves them to your phone. What’s left is a calm page you can cook from — and it stays lit while you do.
The parsing happens on a server you don’t trust
Pulling a clean recipe out of arbitrary HTML is the hard part, and it’s done server-side so the phone never has to. The backend fetches the page through an SSRF-guarded HTTP client — it walks the redirect chain itself and re-checks every hop, because following redirects automatically is the usual way past an allow-list — then hands the content to a language model for a title, ingredient list and steps.
Everything the model doesn’t need to touch is kept away from it. Your saved recipes live in a local SQLite database on the device with no account and no sign-in; the server only ever knows an anonymous per-device GUID and a Smart Credit balance. Purchases are verified against Google Play rather than trusted from the client, and abuse is contained with per-origin rate limits and salted IP hashes instead of stored addresses.
The waitlist behind the landing page is the same idea in miniature: one de-duplicated email, a tight rate limit, and a salted hash for triage — served same-origin so there’s no third-party form vendor in the loop.