Stackwright Pro 🔐

Pro packages extend Stackwright into paid territory — third-party integrations, OpenAPI tooling, and enterprise features.

The OSS monorepo defines interfaces; Pro ships implementations. Clean separation by design.

What's in Pro?

OpenAPI Integration

Turn any OpenAPI spec into typed Zod schemas, CollectionProviders, and API clients. 'Here is an API spec' → 'Here is a working app' in hours.

CMS Backends

Contentful, Sanity, Shopify, Airtable, Notion — each as a CollectionProvider. Switching backends is a one-line change. No YAML changes needed.

Enterprise Ready

RBAC, secrets management, CSP headers, audit logging. Built for government and defense requirements.

Map Integrations

Cesium 3D globe for enterprise logistics. deck.gl for massive data volumes. MapLibre GL included in OSS.

OSS + Pro: Clean Separation

**Stackwright OSS** defines the interfaces, rendering engine, and file-backed implementations. It's the grammar — what you write.

**Stackwright Pro** ships implementations too specialized, too maintenance-intensive, or too commercially sensitive for open source. It's the dictionary — what things mean.

Your app never takes a hard dependency on Pro. Register a Pro provider the same way you register any Stackwright provider. Removing Pro degrades gracefully to OSS fallbacks.

bash
# One command to scaffold Pro app
npx launch-stackwright-pro my-app --spec ./api.yaml --yes
 
# Or add Pro to existing project
pnpm add @stackwright-pro/openapi @stackwright-pro/auth
 
# Register in your app
import { registerOpenAPIProvider } from '@stackwright-pro/openapi';
registerOpenAPIProvider({ spec: './api.yaml' });
Hackathon Teams
Stackwright Pro is built for your use case. Bring an OpenAPI spec, leave with a working app with RBAC, type-safe API clients, and mock auth for dev. See the Pro repo QUICKSTART.md for step-by-step.

Ready to build enterprise?

Get started with Pro today.