One payment. The whole product.

240+ components (150+ web, 85+ native) — 109 documented one by one in the gallery — plus design tokens with 17 theme definitions and the full source code. Free and open source, no sign-up required.

The SDK is the free component library — the building blocks. Paid templates include app kits ($99) with different capabilities: SaaS Dashboard and Fitness include a backend and authentication, while Arcade is client-side with a local demo session by default. Booking is a Live kit with Supabase Auth and a database. Marketplace is a Live kit with Better Auth, a database, and buyer and seller sides. Landing templates ($9) are standalone single-page marketing sites, frontend-only, that deploy as static.

20 premium single-page marketing-site templates — travel, luxury product, fragrance, skincare, SaaS, audio, aerospace, plus five sites that sell an app built on each kit. Each is a standalone, polished marketing site with an animated hero, light and dark themes, real imagery, and AI configs baked in. $9 each, or all 20 in the bundle — click any live preview before you buy.

The SaaS Dashboard and the AI Agent SaaS Kit are React and TypeScript web apps with a backend API, a Postgres database and authentication. Fitness, Booking and Marketplace are Expo apps for iOS, Android and web, with a backend API, a database and authentication. Arcade is a client-side game showcase with a local demo session and no backend sign-in by default. The exact stack is in each kit's docs. Landing templates are static sites with no backend. All TypeScript, zero lock-in; every provider adapter is one file.

Yes. Every kit ships a Cloudflare Workers deploy script (scripts/deploy-worker.sh), a Dockerfile for any container host such as Fly, Render, Railway or a VPS, and a deployment guide; the four mobile kits (Fitness, Arcade, Booking and Marketplace) also include eas.json. The Worker script can attach a custom domain on a Cloudflare zone you already own; the kits do not register domains for you. Landing templates build to static output with `bun run build` and can be deployed to Cloudflare Pages or another static host.

Deployment time depends on your hosting provider, project configuration, and the steps you need to complete. Every kit includes a Cloudflare Workers deploy script, a Dockerfile for any container host and a deployment guide; the four mobile kits also include eas.json. The guides describe the setup, but we have not measured a buyer deployment time.

Claude Code, Cursor and Codex. Every kit ships CLAUDE.md, AGENTS.md, .cursorrules and task prompts. AI tools guide

Check the license file for the specific kit or template before using it for client work. Paid licenses are per developer; the product license defines permitted use, seat limits, and redistribution restrictions.

Paid kit licenses are per developer and allow the licensed developer to use, modify, and ship the kit code in personal or commercial products. You may not resell or redistribute the kit source as a template or starter. Each kit has its own LICENSE-KIT.md, which controls its exact terms.

Paid kits include 12 months of free updates. After checkout, OTF sends the license email; use its repo-access link to provide your GitHub username and receive an invitation to the private kit repository, where the source and updates are available.

The Booking Kit includes an Expo app with Supabase Auth, PostgreSQL row-level security, and Supabase Realtime. It is a Live kit at $99. Before production, verify redirect and deep-link configuration on each target platform, row-level security policies for the data you expose, and session handling in the app.

The bundle is $149. 6 delivered kits + all 20 landing templates. Save $625 vs buying separate ($774). It includes 12 months of free updates.

No — paid products include full source code, so all sales are final except where required by law. After purchase, use the link in your license email to claim private GitHub repo access. Click through the live demos, browse the components, and read the docs before buying.

No. Everything is designed in code — every color, spacing, radius, and shadow is a token in @otfdashkit/tokens, so the design system is the source of truth, not a separate Figma file. Override one variable and the change ripples across every screen.