Skip to content

CreativeOS

Brian's personal creative infrastructure platform — "the operating system of a full-stack creative's life"

Overview

CreativeOS is the main application layer that sits on top of rootphi-core's shared infrastructure. It's designed first as Brian's personal tool, with multi-tenancy baked in from day one so it can eventually be productized for other creative entrepreneurs.

Architecture (decided 2026-03-27 via 7-provider triangulation)

Stack: Postgres (via Supabase) + Next.js + Vercel + Cloudflare + tldraw + LangGraph + n8n Pattern: Modular monolith — clean module boundaries, but deployed as one unit until extraction is warranted Multi-tenancy: RLS (Row-Level Security) from day one, "first tenant" model — Brian is tenant #1 Auth: Supabase Auth for Phase 1, with option to migrate to Clerk/Auth0 later

Consensus Scores (from triangulation)

  • PostgreSQL: 7/7
  • Supabase: 6/7
  • Modular monolith: 6/7
  • n8n for automation: 6/7
  • API-first kernel: 6/7

Infrastructure

Resource Details
GitHub bwitlin/creativeos (private, username bwitlin)
Supabase Rootphi org, Pro plan ($25/mo), Micro compute, West US Oregon
Supabase URL https://ptpcjkhttglmdtdzuwtb.supabase.co
Env keys rootphi-core/creativeos-env-keys.json (anon + service_role)

Phase 1: Foundation (Weeks 1–4)

Spec: rootphi-core/creativeos-phase1-spec_2026-03-27.md

5-table schema: tenants, profiles, projects, assets, activity_log — all with RLS policies. API routes for CRUD. Next.js scaffold with Supabase Auth. Week-by-week build plan with acceptance criteria.

Status: Spec complete, infrastructure provisioned, ready for Week 1 build.

Roadmap (6 phases)

  1. Foundation — Schema, auth, CRUD, deploy pipeline (Weeks 1–4) ← CURRENT
  2. Intelligence — LangGraph agents, vector search, semantic tagging
  3. Automation — n8n workflows, event-driven pipelines
  4. Creative Tools — tldraw canvas, media pipelines, collaboration
  5. Polish — Performance, monitoring, UX refinement
  6. Extend — App concepts (Creative Data Room, Moment Maker, Patent Engine, Deep Research)

Key Decisions

  • REST for Phase 1 (not tRPC) — universality over type safety at this stage
  • Mono-repo — single creativeos repo matching modular monolith philosophy
  • Supabase Auth — keep everything in one platform during foundation phase

Source Chats