last_updated: 2026-05-03
VeganStove is a plant-based test kitchen run from a small apartment in Portland, Oregon. Every recipe gets at least three test cooks before it goes online. No fluff. No copy-paste.
Who runs this
I’m Sage Bendly. She/her, based in Portland. Before VeganStove I spent six years inside Pacific Northwest food media, editing recipe development for plant-based publications. I shipped a lot of work I had not personally tested. That stopped feeling honest.
VeganStove is the answer. The beat is plant-based cooking: bowls, breakfasts, weeknight pastas, weekend desserts, air-fryer crispy proteins. The method is the headline. The cuisine is the soundtrack.
How a recipe gets published here
The rule is simple. Nothing publishes without:
- Three test cooks minimum. Variations on the same base count as one. Real different conditions (different bean batch, different pan, different day) count as separate runs.
- Timing notes. Actual stopwatch numbers from my kitchen, at sea level, in a standard 4-quart pot or 4-quart air fryer unless stated otherwise.
- A sourced base. Reference values are pulled from named industry sources (USA Dry Pea & Lentil Council, Rancho Gordo, Bean Institute, USDA, peer-reviewed cookbooks). Personal opinions are flagged as opinions.
- At least one annotated mistake. What went wrong on test run 1 or 2, and the change that fixed it on test run 3. The mistake is part of the story.
- A version number. Recipes get stamped (v1.0, v1.1) so corrections are traceable. When a reader catches a flaw, I update the recipe and bump the version. The change is logged at the bottom.
What you will not find here
- Stock-photo recipes I did not cook.
- 1,200-word introductions about my grandmother before the ingredient list.
- Affiliate links to tools I have never used. (See the affiliate disclosure for the full rule.)
- Filler keywords. If the recipe is “vegan tofu scramble,” the headline is “vegan tofu scramble,” not “the easiest, creamiest, most delicious tofu scramble of your life.”
The lab tools
Beyond the recipes, there are interactive tools built from real kitchen data:
- Beans & Lentils Cooking Time Calculator. Twenty legumes, three soak states, three cooking methods. Base values from reference consensus, soak and method offsets tested in this kitchen. The full protocol is on the cooking time methodology page.
More tools are in the queue. The criterion is the same: it ships when the data is real.
Where the recipes come from
Six core categories, picked because they are what plant-based cooks actually search for, and because they are what I cook:
- Vegan Bowls: protein-grain-veg combos for everyday eating.
- Vegan Breakfast: tofu scrambles, overnight oats, weekend brunch.
- Vegan Burgers: patties engineered to not fall apart.
- Vegan Pasta: cashew-cream sauces that actually coat.
- Vegan Air Fryer: maximum crisp, minimum oil.
- Vegan Desserts: fudgy, chewy, crackly, with egg replacers tested.
About AI and writing
The recipes, the timings, the mistake notes, the editorial decisions: all of that is mine. AI is used at the same level a spell-checker is. It does not pick what to cook, it does not invent timing data, it does not write the experience of standing over a pan. The full position is on the editorial guidelines page.
Get in touch
Recipe corrections, partnership questions, sourcing tips, press: head to the contact page. I reply within 48 hours on weekdays.
For the weekly Friday memo (what I tested, what won, what flopped, plus the weekend recipe), the newsletter is the place.
Sage Bendly
Editor & lead test cook, VeganStove
Portland, OR