Repository Structure - Phaseo Docs

Phaseo is a pnpm and Turborepo monorepo. Use this reference to find the files for a code or documentation change. For catalog record changes, open an issue.

Applications and packages

Path	Purpose
`apps/web`	Next.js 16 website, dashboard, and internal catalog editor.
`apps/web-api`	Public catalog reads and authenticated account and admin APIs.
`apps/api`	Gateway routing and provider execution on Cloudflare Workers.
`apps/docs`	Mintlify documentation; MDX pages are in `v1`, navigation in `docs.json`.
`packages/sdk`	TypeScript, Python, Go, C#, PHP, Ruby, Java, Rust, and C++ SDKs.
`supabase/migrations`	Database schema and permission migrations.
`scripts`	Validation, SDK generation, and automation utilities.
`.github/workflows`	CI, deployment, and catalog synchronization.
`.changeset`	Release metadata for versioned packages.

Catalog data

The database is the source of truth for models, providers, organisations, pricing, benchmarks, and supporting catalog settings. Admins manage records through Internal data. Public contributions are reviewed through GitHub issues.

The repository holds no catalog JSON. The legacy JSON-to-database importer is retired.

Schema and application changes still use migrations and pull requests. Generated SDK artifacts should be updated through their generation commands.

Catalog automation

Provider sync queues proposed prices for review in Provider updates. Benchmark and model lifecycle jobs use the database. Catalog-only records do not automatically enable Gateway routing. Route and price changes require the appropriate admin review.

Where to start

Last modified on October 29, 2026