Built for the people around the meal, not just the recipe itself.

GetLadle came from a simple problem: recipes, meal planning, and group coordination were scattered everywhere. The fun part was the meal. The exhausting part was everything required to make it happen.

Recipes come in fast

Import from a link (TikTok, Instagram, Pinterest, YouTube), a photo, or your own notes without losing the shape of the dish.

Sharing stays private

Circles are for the people you actually cook for: family, friends, neighbours, and recurring groups.

Events stay free

Invites, RSVPs, and dish claiming are part of the growth loop, not a paywall.

Planning leads to cooking

Meal plan, shopping, and cook mode connect instead of ending in a dead list. Snap your fridge to stock the pantry, and turn what is on hand into a proper recipe.

Why it exists

Mel Schembri built GetLadle after running into the same friction repeatedly: recipes buried in chat threads, potluck coordination spread across too many messages, and weekly meal planning living in scraps and memory.

The point was never to create another personal recipe utility. The point was to make it easier to feed people, host well, remember what was cooked, and keep the social thread alive after the meal.

That is why GetLadle lives between recipe saving and social coordination. Recipes are the start. Circles, events, shopping, cook mode, and gallery are what give them somewhere meaningful to go.

What makes it different

• Private circles instead of public posting.
• Events and dish coordination built into the product.
• Meal planning that leads into shopping and cooking.
• A living gallery built from meals actually made.
• Premium that expands naturally rather than blocking core social use.