Demo video

The vision for Norish is a shared recipe app, to be shared with friends to make one big recipe catalogue.

The name is derived of our dog named: Nora, and dish. As a coincidence this can also be pronounced as Nourish. If you look hard enough you can find a picture of Nora.

Norish was built solely because me and my girlfriend like to cook and keep track of our recipes. Sadly we could not get used to the aesthetic of Tandoor or Mealie. Both are great alternatives providing a more rich featureset than Norish. I have not tried tandoor or mealie enough to know their exact feature set but. I believe Noris is different in the sense that the instance is fully-realtime in theory.

This was one of the only requirements my girlfriend had as we do groceries together and this way we can keep track of who picked what grocery items.

Norish does not try to be Tandoor or Mealie it is minimalistic by nature, thus I am not sure yet if I will ever add complex cookbook structures, inventory tracking etc.

On my todolist are still in order of current priority:

• Mobile apps.
• Public shareable recipe links.

• Easy import of recipes via URL, with a fallback to AI if configured.
• Video recipe import from YouTube Shorts, Instagram Reels, TikTok, and more (requires OpenAI provider)
• Image recipe import import a recipe from any set of images containing a recipe (requires OpenAI provider)
• Nutritional information Calculate nutritional information for a recipe (requires OpenAI provider)
• Allergy warning show allergy warnings for planned recipes. Can auto detect allergies based on ingredients. (auto detection requires OpenAI provider)
• Unit conversion Convert units from metric to US or vice versa, note: AI has to be enabled and setup for this.
• Recurring groceries Groceries can be marked as recurring this can be done using NLP or the interface
  • Currently we support: daily, weekly on day, monthly, montly on day. Every x weeks on day.
• Real-time sync of recipes, grocery lists and meal plans
• Households Share grocery lists, and meal plan(calendar)
• CalDav sync Sync your recipes with any caldav provider(only tested with radicale)
• Mobile-first design for use in the kitchen
• Light & dark mode support
• SSO (OIDC/OAuth2) Norish supports login via OIDC/OAuth2. There are no plans to start supporting password login.
  • If no auth provider is configured email and password authentication will be enabled by default.
• Admin Settings UI for server owners to manage configuration without editing files
• Permission policies for controlling who can view/edit/delete recipes (everyone, household, or owner only)
  • Default view: Everyone
  • Defaul Edit: household
  • Default Remove: household
• Local AI In theory Norish supports local AI providers - however I have not tested this. Although I am looking to buy a machine that is capable.

Note: All AI related features seem to be rather slow for me using the OpenAI API. I am not sure why this is your results may vary.

services:
  norish:
    image: norishapp/norish:latest
    container_name: norish-app
    # user: "1000:1000"  # Match your host user's UID:GID (run `id` to check), only needed with bind mounts
    # The example uses named volume 'norish_data' which handles permissions automatically
    restart: always # Required for server restart functionality
    ports:
      - "3000:3000"
    user: "1000:1000"
    volumes:
      - norish_data:/app/uploads
    environment:
      # Core settings (required)
      AUTH_URL: http://norish.example.com
      DATABASE_URL: postgres://postgres:norish@db:5432/norish
      MASTER_KEY: <32-byte-base64-key> # Generate with: openssl rand -base64 32
      CHROME_WS_ENDPOINT: ws://chrome-headless:3000
      REDIS_URL: redis://redis:6379

      # OPTIONAL
      # NEXT_PUBLIC_LOG_LEVEL: info       # trace, debug, info, warn, error, fatal (default: info in prod, debug in dev)
      # TRUSTED_ORIGINS:http://192.168.1.100:3000,https://norish.example.com  # Additional trusted origins, comma separated. Useful when behind a proxy or using multiple domains.
      # YT_DLP_BIN_DIR: # Custom folder path for `yt-dlp` (default: /app/bin)

      # ─────────────────────────────────────────────────────────────────────────
      # FIRST USER SETUP
      # ─────────────────────────────────────────────────────────────────────────
      # On first startup, configure ONE auth provider below to create your admin account.
      # After first login, use Settings → Admin to configure additional providers,
      # AI settings, video parsing, and all other options.

      # Option 1= Password auth - basic auth with email/password
      # If not set defaults to disabled if OIDC or OAuth is configured.
      # Defaults to true if no other auth providers are configured.
      #PASSWORD_AUTH_ENABLED=false

      # Option 2: OIDC (Authentik, Keycloak, PocketID, etc.)
      # OIDC_NAME: NoraId
      # OIDC_ISSUER: https://nora.example.com
      # OIDC_CLIENT_ID: <client-id>
      # OIDC_CLIENT_SECRET: <client-secret>
      # OIDC_WELLKNOWN: https://auth.example.com/.well-known/openid-configuration
      # Wellknown is optional: By default the wellknown URL is derived from the issuer by appending /.well-known/openid-configuration

      # Option 3: GitHub OAuth (uncomment and remove OIDC above)
      # GITHUB_CLIENT_ID: <github-client-id>
      # GITHUB_CLIENT_SECRET: <github-client-secret>

      # Option 4: Google OAuth (uncomment and remove OIDC above)
      # GOOGLE_CLIENT_ID: <google-client-id>
      # GOOGLE_CLIENT_SECRET: <google-client-secret>
    depends_on:
      - db
      - redis

  db:
    image: postgres:17-alpine
    container_name: norish-db
    restart: unless-stopped
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: norish
      POSTGRES_DB: norish
    volumes:
      - db_data:/var/lib/postgresql/data

  # Chrome headless
  chrome-headless:
    image: zenika/alpine-chrome:latest
    container_name: chrome-headless
    restart: unless-stopped
    command:
      - "--no-sandbox"
      - "--disable-gpu"
      - "--disable-dev-shm-usage"
      - "--remote-debugging-address=0.0.0.0"
      - "--remote-debugging-port=3000"
      - "--headless"

  # Redis for real-time events and job queues
  redis:
    image: redis:8.4.0
    container_name: norish-redis
    restart: unless-stopped
    volumes:
      - redis_data:/data

volumes:
  db_data:
  norish_data:
  redis_data:

The first user to sign in becomes the Server Owner and Server Admin automatically. After the first user signs in:

• User registration is automatically disabled
• All server settings can be managed via Settings => Admin tab

Server owners and admins can configure the following via the Settings => Admin tab:

• Enable/disable new user registrations

• View Recipes - Who can see recipes (everyone, household members, or owner only)
• Edit Recipes - Who can modify recipes (everyone, household members, or owner only)
• Delete Recipes - Who can remove recipes (everyone, household members, or owner only)
• Server admins always have full access regardless of policy settings
• Groceries and calendar items follow household rules automatically (members can edit/delete each other's items)

• OIDC (Authentik, Keycloak, PocketID, etc.)
• GitHub OAuth
• Google OAuth
• Test providers before saving, reveal/hide secrets, delete providers
• Note: Auth provider changes require a server restart to take effect (use the Restart Server button)

• Units - Custom unit definitions for ingredient parsing
• Content Indicators - Schema and content indicators for recipe detection
• Recurrence Config - Locale-based recurrence patterns, used for natural language processing when adding recurring groceries.

• AI Configuration - Provider, endpoint, model, API key, temperature, max tokens
• Video Processing - Enable/disable, max video length, yt-dlp version
• Transcription - Provider, API key, model for video transcription

• Scheduler - Configure cleanup retention period (months)
• Restart Server - Apply changes that require a server restart

Only a few environment variables are required. All other settings are managed via the Admin UI.

Configure one auth provider via environment variables to create your first admin account:

After first login, manage all auth providers via Settings => Admin.

# Clone the repository
git clone https://github.com/mikeve97/norish.git
cd norish

# Install dependencies
pnpm install

# Create your environment file
cp .env.example .env.local

# Spin up a postgres and redis instance (e.g. via docker)
# docker run -d --name norish-db -e POSTGRES_PASSWORD=norish -e POSTGRES_DB=norish -p 5432:5432 postgres:17-alpine
# docker run -d --name norish-redis -p 6379:6379 redis:7-alpine

# Run the app
pnpm run dev

All development tooling configuration is centralized in the tooling/ folder:

tooling/
├── eslint/
│   └── eslint.config.mjs    # ESLint flat config with TypeScript, React, Prettier
├── tailwind/
│   ├── hero.ts              # HeroUI plugin export for Tailwind CSS v4
│   └── theme.css            # Custom theme colors (light/dark) using CSS variables
└── vitest/
    ├── vitest.config.ts     # Vitest configuration with React, jsdom
    └── setup.ts             # Test setup with jest-dom matchers

The root config files (eslint.config.mjs, vitest.config.ts) re-export from the tooling folder for tool compatibility.

• Next.js 16
• Tailwind CSS 4
• HeroUI
• Framer Motion
• Zustand – Not sure if I want to keep it, currently mostly unused in favor of the context API.
• TanStack Query

• Node.js - Custom server that embeds the Next server for WS/Redis support.
• tRPC
• Better Auth
• Pino
• Redis
• BullMQ - Job queue for background tasks (recipe import, AI processing, etc.)

• PostgreSQL
• Drizzle ORM
• Redis - Used for real-time pub/sub events and BullMQ job queues

• OpenAI SDK
• Puppeteer – Headless browser for web scraping (required).
• yt-dlp – Video downloading from YouTube, TikTok, etc.
• Sharp – To process the images to a uniform format.
• FFmpeg

• Vitest
• Testing Library
• jsdom

• TypeScript 5
• pnpm
• ESLint
• Prettier

Norish is licensed under AGPL-3.0.

Alternatives that I know of: Mealie Tandoor

Current documentation is limited, I will start working on better documentation, a contribution guide etc.

Last but not least a picture of our lovely dog Nora: