CodePlans gives engineering teams a shared view of what's changing, in which components, and why — from individual tasks up to cross-service migrations.
Built for engineering teams managing change across complex service-oriented and monorepo architectures.
Model your architecture as products containing typed assets — apps, services, libraries, datastores, and platforms. Track health and tech debt per component.
Coordinate related changes under a single plan with a clear lifecycle: Draft → Active → Completed. Assign target assets, set deadlines, and track progress at a glance.
Break plans into tasks with priorities, effort estimates, assignees, and asset scope. View work in a list table or a kanban board by status.
Dashboard metrics show active plans, completed tasks, tasks this week, and rolling velocity — so teams always know how fast they're moving.
Invite team members with role-based access — owner, admin, editor, or viewer. Products can be shared across an organisation or owned by an individual.
Run locally with SQLite (zero cloud setup) or connect to Supabase + Postgres for production. Auth works with a local password store or Supabase Auth.
Everything you need to understand the data model, architecture decisions, and current feature state.
Complete spec of the current app: schemas, views, query/mutation API, access rules, and wiring gaps.
Conceptual model, feature modules, and functional requirements for the full CodePlans platform.
Assets, dependencies, and team collaboration — the reasoning behind the current database schema.
Current database schema diagrams covering both SQLite and Postgres configurations.
Local SQLite mode requires no cloud account, no API keys, nothing external.
Open localhost:3000 and sign in with
admin@example.com / Password1!.
Change your password in Settings → Security after first login.
pnpm db:seed-demo after the initial seed to populate with products, assets, plans, and tasks.
All demo accounts use password Password1!.
AUTH_URL=https://your-server-domain (or http://ip:port) in .env.local.
Auth.js requires this in production to construct correct callback URLs — without it, login redirects will fail.
If running the dev server on a remote machine, also set ALLOWED_DEV_ORIGINS=your.server.ip.
Two independent knobs control how your instance behaves — the deployment model and who can register.
pnpm db:seed.
See .env.example for the full annotated configuration file.
No heavy abstractions. Readable Next.js App Router code with a clean DB layer you can fork and adapt.
Transparent about what's wired, what's in progress, and what's coming.