Allergen information, made clearer

Better information.
Better decisions.

Epipendly is exploring a clearer way for restaurants to manage and communicate allergen and cross-contact information - to both their staff and their guests.

Join the journey → See how it works
Currently in research, prototype testing, and restaurant discovery - not yet commercially launched.
The operational problem

Allergy information often travels through too many hands.

A guest asks a server. The server asks a manager. The manager checks with the kitchen. During a busy service, every handoff can add delay, inconsistency, or uncertainty.

A restaurant manager and chef reviewing menu information on a tablet
Designed for restaurant reality

Make important information easier to maintain - and easier to reach.

The direction we are testing is a structured source of restaurant-provided information that supports the people managing it and the people relying on it.

Structured at dish level Ingredients, reported allergens, cross-contact practices, modifications and uncertainty.
Maintained by the restaurant Restaurant-wide defaults can reduce repetition while dishes can still differ.
Available in context Staff and guests can access relevant information without relying only on memory.
Restaurant side · B2B

One place to manage what the restaurant knows.

The restaurant remains the source. Epipendly helps structure, maintain and communicate the information consistently.

01
Menu and dish records

Organize ingredients, allergens and sources around the way the menu actually works.

02
Cross-contact practices

Record observable operational facts, including honest unknowns and dish-specific differences.

03
Source and freshness

Show where information came from and when it was last reviewed.

One source, connected experiences

Different people. The same underlying evidence.

The product is being designed around three connected contexts - not three disconnected answers.

Restaurant management

Create, review and publish structured menu, allergen and cross-contact information.

Staff access

Look up a dish and communicate what is reported, uncertain or still needs confirmation.

Guest access

Scan a QR code and see restaurant-provided context without installing an application.

Evidence, not verdicts. The restaurant provides the information. Epipendly structures and communicates it. The diner makes the decision.
Where we are today

Built enough to test. Early enough to learn.

Restaurant UX architecture Designed
Clickable restaurant prototype Built
Restaurant usability and discovery Testing now
Live product and commercial launch Not yet
Yossi Povalaev holding an epinephrine auto-injector
Why I’m building Epipendly

“I don’t leave home without an injector. But I keep thinking about what we can improve before something goes wrong.”

I’m Yossi Povalaev, founder and product builder of Epipendly. I have a life-threatening mustard allergy. The project began from personal experience, but research made something else clear: restaurants also need a practical way to create, maintain and communicate reliable information.

Epipendly is my attempt to build that connection - with restaurants, staff and allergic diners involved in shaping it.

Join the journey

Help shape what Epipendly becomes.

The most useful input comes from people who experience the problem, manage it, or can help turn the concept into a tested product.

Restaurants

Share how allergy questions work during real service, test the prototype, or explore becoming a design partner.

People with food allergies

Tell us what information you need, what creates uncertainty, and how you make dining decisions.

Industry experts

Bring experience in hospitality, food safety, restaurant technology, accessibility or product.

Investors & supporters

Follow the validation journey and help us think clearly about the market and responsible growth.

Interested in contributing?

Tell Yossi which perspective you bring and why this problem matters to you.

Start a conversation →
Join the journey