Bizweave

Your business, woven online while you sleep.

Bizweave is a production-grade AI platform for existing businesses — liquor stores, retail shops, restaurants, and SaaS products. Connect your inventory, location, and brand. AI agents build your website, create marketing plans, set up support templates, and pass everything through a Safeguard last-bastion review before anything goes live.

The pipeline now includes a Trust Index in the Safeguard verdict so every run is explainable and reliability-scored before publish.

Bring Your Own Keys (BYOK) for OpenAI and Anthropic — your API keys are encrypted at rest with AES-256-GCM.

• 6-agent pipeline: Intake → Planner → Builder → Marketing → Support → Safeguard
• BYOK: OpenAI & Anthropic with connection testing
• Business onboarding: Multi-step wizard with CSV inventory import
• Generated sites: Mobile-first HTML/CSS preview
• Demo mode: Works without API keys using intelligent templates
• Design system: See DESIGN.md

# Start local stack (frontend + backend + Postgres)
make docker-up

Open http://localhost:3000.

If Docker image pulls are flaky in your network, use the no-Docker local path below.

If Docker Hub is timing out specifically for node:22-bookworm-slim, you can use a mirror image for the frontend build:

FRONTEND_NODE_IMAGE=public.ecr.aws/docker/library/node:22-bookworm-slim \
POSTGRES_IMAGE=public.ecr.aws/docker/library/postgres:16-alpine \
docker compose up --build

npm install
cp .env.example .env

# One-command local setup (Homebrew PostgreSQL + role/db bootstrap + Prisma push)
make local-setup

# Run the Next.js app
make dev

make local-setup does all of the following:

• Starts postgresql@16 via Homebrew services
• Ensures role postgres exists with password postgres
• Ensures database bizweave exists and is owned by postgres
• Pushes Prisma schema to DATABASE_URL

Optional backend setup (for the Python service):

make backend-sync
export BACKEND_DATABASE_URL="postgresql+psycopg://user:pass@host:5432/backend_db"
make backend-migrate

Backend Alembic commands are intentionally guarded and require backend-only opt-in + URL. See docs/orm-ownership-boundaries.md.

1. Sign up at /signup
2. Onboard a business at /onboarding
3. Add API keys (optional) at /dashboard/settings/keys
4. Run agents from the business dashboard

• Next.js 16 (App Router)
• TypeScript, Tailwind CSS 4
• Prisma 7 + PostgreSQL
• Python 3.12 backend service with uv + Alembic storage migrations
• Jose (JWT sessions), bcryptjs
• Framer Motion, Lucide icons

All agents share safety rules in prompts and strict JSON contracts. The Safeguard Agent reviews every artifact before status moves to live, emits a Trust Index (0-100), and blocks publish when reliability is too low. Without a valid BYOK key, the pipeline uses production-quality template fallbacks so the product works end-to-end in demo mode.

make test-unit
make test-integration
make test-e2e
make test-supabase
make test-supabase-db

Supabase tests come in two flavours:

1. Vitest integration tests (test:supabase) — Test Supabase client imports, environment configuration, and module shape. Run against the configured Supabase project using @supabase/supabase-js.

npm run test:supabase        # or: make test-supabase

2. Database contract tests (test:supabase:db) — pgTAP SQL files under supabase/tests/database that verify RLS policies, schema columns, indexes, and policy contracts are correct against the actual database.

# Ensure the pgTAP extension is installed in your database first:
#   Docker Compose: docker compose up -d db-test
#   Homebrew:       brew install pgtap && psql $DATABASE_URL -c "CREATE EXTENSION pgtap"
npm run test:supabase:db    # or: make test-supabase-db

The SQL files follow Supabase's pgTAP testing guide and are run via scripts/run-pgtap-tests.sh which connects using DATABASE_URL from .env.

make install
make local-setup
make local-dev
make db-local-stop
make db-push
make lint
make build
make docker-up
make docker-down

For backend storage migrations:

export BACKEND_DATABASE_URL="postgresql+psycopg://user:pass@host:5432/backend_db"
make backend-migrate
make backend-revision

For the Node/TypeScript frontend, pnpm is the best overall choice for speed, reliability, and workspace ergonomics. npm is the simplest and most compatible, but slower. bun is fast, but the ecosystem maturity is still weaker for a Prisma + Next.js production stack. I kept the existing npm lockfile for now so the current app remains stable, but pnpm would be the best next-step migration if you want to modernize the frontend toolchain.

MIT