Review consequential OpenAPI contract changes before they reach users.
Founding build: OpenAPI Studio is not a finished editor or self-serve product. The public repository currently proves the delivery foundation, demand test, and proposed review workflow. Product capabilities are built only after design-partner evidence.
Brand preview with an illustrative product concept, not product UI.
View the live preview · Join design-partner research · Read the product roadmap
Raw OpenAPI diffs show which lines moved, but teams still have to determine what may break, who is affected, and whether the new contract should be published. OpenAPI Studio is testing a focused workflow that keeps the change, consequence, and team decision connected.
| Area | Current evidence |
|---|---|
| Design-partner research | Responsive landing page, qualified email path, explicit $29/workspace/month hypothesis |
| Delivery | Cloudflare Workers preview, locked Bun install, GitHub Actions validation |
| Quality | TypeScript, Oxlint, Oxfmt, Vitest, Playwright, axe accessibility checks |
| Data foundation | Drizzle schema, committed migration, local migration and database smoke checks |
| Operations | Request observability and identifier-free first-party conversion events |
| Product design | Labelled OpenAPI review prototype and evidence-gated roadmap |
- No production OpenAPI editor or account access
- No contract import, validation, diff engine, revision history, or publishing workflow
- No customers, usage claims, testimonials, checkout, or billing
- No production deployment or custom domain
The next product phase is intentionally gated on qualified conversations and pilot commitment. See PRODUCT.md, DESIGN.md, and the roadmap for the decisions behind that boundary.
This is a single-package modular monolith using TanStack Start with Solid, TypeScript, Cloudflare Workers, Bun, Turso/libSQL, Drizzle ORM, Valibot, Tailwind CSS, Oxlint, Oxfmt, Vitest, and Playwright. Feature code lives under src/features; platform boundaries live under src/platform; migrations live under drizzle; browser and unit tests live under tests and adjacent feature files.
Requires Bun 1.3.14 or a newer 1.x release.
bun install --frozen-lockfile
bun run devRun the same validation used by CI:
bun run checkDatabase access expects TURSO_DATABASE_URL and TURSO_AUTH_TOKEN. Copy .env.example to an ignored local environment file. Local development and CI do not require production credentials. bun run deploy:preview is human-gated; no production deployment command exists.
Read CONTRIBUTING.md before proposing a change. Do not report vulnerabilities in public issues; follow SECURITY.md. Never submit real API contracts, customer data, credentials, or confidential material.
The repository is public for transparency and technical evaluation, but it is not currently open source. No reuse rights are granted. See LICENSE.