A collaborative Progressive Web App for storing recipes, planning meals, and organizing shopping lists with automatic imports.
RecipeSage is a collaborative Progressive Web App that helps users store, organize, and share recipes, plan meals with a drag-and-drop calendar, and generate smart shopping lists. It solves the problem of fragmented meal management by centralizing recipe imports from websites, images, or documents, automating shopping list creation, and enabling real-time collaboration with others.
Households, families, and individuals who cook regularly and want a unified digital system for recipe collection, meal planning, and grocery shopping, especially those valuing self-hosting and data control.
Developers choose RecipeSage for its robust self-hosting capabilities, extensive import/export support, and collaborative features—offering a privacy-focused, customizable alternative to commercial meal planners with no vendor lock-in.
A Collaborative Recipe Keeper, Meal Planner, and Shopping List Organizer in PWA form.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically creates recipes from URLs, images, PDFs, or text, supporting formats like JSON-LD and Paprika, as shown in the GIFs and feature list.
Enables drag-and-drop scheduling and sharing of meal plans with others, facilitating real-time household coordination, highlighted in the meal plan GIF.
Automatically categorizes and combines items when adding recipes, reducing duplicates, which simplifies grocery management as described in the features.
Supports export in multiple formats for backups and allows self-hosting via Docker, giving users ownership over their recipe data.
Requires Docker, Node, and database migrations, with the README noting that own configurations may run into complications, making it less accessible for non-technical users.
Does not accept AI-assisted code contributions, which can limit community-driven development and slow innovation, as stated in the contributing section.
For commercial use, a custom license must be negotiated, adding uncertainty and potential costs compared to fully open-source alternatives with clear terms.