RuleRadar AI

Monitors official EU product-safety and marketplace sources, detects meaningful wording changes, drafts source-grounded analyses with AI, routes every draft through human review, and delivers approved alerts to the sellers they apply to.

Informational monitoring, not legal advice. The product never determines compliance.

Stack

Next.js 16 (App Router, TypeScript) · Tailwind CSS 4 + shadcn/ui-pattern components · Supabase (Postgres, Auth, RLS) · OpenAI (Responses API, strict JSON schema) · Resend · Stripe · Sentry · Vitest · Playwright. Hosted on Vercel.

Repository map

Path	What it is
supabase/migrations/	8 SQL migrations: tenancy, monitoring, alerts, queue/audit/retention, security (RLS, grants, RPCs), reference data, service functions, contact
supabase/tests/	SQL test suite (RLS, tenant isolation, entitlements, queue, retention) + local Supabase shim
lib/core/	Pure engine: normalisation, diff, retrieval, AI schema + verification, prompts, cost, billing mapping
lib/pipeline/	Agents (with enforced permissions) and orchestrator
lib/server/	Supabase adapter, auth helpers, OpenAI/Resend/Stripe integrations, env validation
app/(site)	Public website · app/(auth) sign-in · app/onboarding · app/app customer app · app/admin staff console · app/api cron + Stripe webhook
scripts/	db-test.sh, test-all.sh, local-stack/ (Postgres + PostgREST + auth test double)
docs/	Audit, architecture, runbook, security and launch checklists, progress report

Local development

Prerequisites: Node 20.9+, PostgreSQL 15+ (superuser access), and the PostgREST binary for the local stack.

npm install
./scripts/local-stack/start.sh          # Postgres DB + PostgREST + gateway on http://localhost:54321
set -a; . ./.env.local.test; set +a     # local keys (generated, local only)
npm run dev                              # http://localhost:3000

Seeded local users (sign in by setting a session cookie; see tests/e2e/helpers.ts): [email protected] (platform admin), [email protected], [email protected]. The local auth gateway is a test double; it is never deployed.

Tests

./scripts/test-all.sh    # DB -> unit -> typecheck -> integration -> build -> E2E
npm test                 # unit + pipeline only (no database needed)
npm run test:db          # SQL suite only

Deploy

See docs/RUNBOOK.md. In short: create a Supabase project, apply supabase/migrations in order, create a Vercel project from this repo, set the variables in .env.example in Vercel's environment settings (never in code or chat), and grant yourself platform-admin with one SQL statement.