Your recipes, without the site around them.

Paste your blog address below. We read the recipe markup your site already publishes for Google, and show you what a clean, ad-free app made of your own recipes would look like. It takes about a minute, you do not need an account, and nothing about your blog is changed.

Most bloggers should start with the free clean-recipe button: one snippet next to Jump to Recipe, a clean text version for the readers who want one, and a followed backlink to you on every page it serves. This page is the paid half, for when you want the whole thing as your own app. The two stack, and the button is live today.


The problem, stated plainly

The ads pay for the site, and the ads are why the site is unpleasant. You cannot fix that by tidying up, because the clutter is the income. Everyone involved knows this and nobody can do anything about it.

Underneath that sits the worse problem. The traffic is not yours. It comes from Google, or Pinterest, or increasingly from an AI answer that used your recipe and did not send anyone. Any of those can halve in a week, and none of them ask first. You have an audience you cannot contact and cannot count on.

And most of you have something to sell. A cookbook, an ebook, a set of meal plans. It sells through somebody else's checkout, to people who found you through somebody else's algorithm.

What this is

A second place your recipes live: an app on your name, your logo and a colour you choose, with no ads in it, for the small number of readers who cook from you every week. They can save, search, scale and cook from it. You can put your books in front of them. If you want, they can pay you a few dollars a month directly, and we take a small percentage rather than a rent.

It is not a replacement for your website. Keep the ad site. It serves the drive-by search traffic, and that is what it is good at. This is for the two percent who already know your name, which is the part of your audience the ad model has never paid you properly for.

What it will cost

$49 a month, plus 5% of what your readers pay you. Nothing else. No per-member fees, no tiers, no sales call. If your readers pay you nothing, you pay $49 and that is the whole bill.

Substack takes 10%. Patreon takes 10% from new creators. It is not open yet, and everyone on the waitlist gets early supporter pricing and first access when it is.

The pricing page has a calculator for your own numbers, and names the two cases where one of the others is the cheaper buy.

Not ready for your own app? Start with the free clean-recipe button.

What it does not do

Worth saying before you spend any more time. There is no meal-plan builder, no nutrition tracking, no grocery-checkout integration, and no migration team. Other people sell all of that and some of them sell it well. If those are what you need, you should buy one of those instead, and the comparisons say so in more detail.

Who this is for

A good fitYou have 50 or more recipes with schema markup, an audience that knows your name, and something you already sell or plan to.
A bad fitYour income is ad RPM and you have nothing else to sell. This adds a place for the loyal few to pay you. It does nothing for page views.
Too earlyYou are still building the library. Come back at fifty recipes; below that there is not enough to make an app worth opening.

How the reading works, since you are handing us your recipes