Building a World Where Everyone Can Eat With Confidence

Allergy Tree started with a restaurant, a binder, and a bad night. Every allergy request meant pulling a three-ring binder from the back office, flipping to a page that may or may not have been updated since the last supplier change, and hoping nothing had shifted since the last print. It worked, mostly, until the one night it didn't.

That's the problem with a manual system: it only takes one missed update, one rushed shift, one substitution nobody wrote down. And on the other side of the table, the guest has no way to know any of that. They're trusting a stranger with something that, for them, isn't optional.

We built Allergy Tree to close that gap. Restaurants keep one living menu instead of a binder that goes stale the moment it's printed. Guests get a straight answer: what's safe, what isn't, and why, before they've even ordered. And because the ratings come from people managing the same allergies, the trust actually means something.

None of that works without accountability on both sides. Restaurants are responsible for keeping their menu data accurate. We're responsible for surfacing it clearly and pulling down anything that's gone stale. And for anything life-threatening, we still tell diners to say it out loud to staff. A scan is a strong first answer, not a replacement for the conversation.

We're starting where we started: in our own restaurant, replacing our own binder. From there, one scan at a time.