What AI Launch Kit does — and what it does not do yet
Thirteen capabilities. Ten Installed. Three Platform Services. Status is honest — shipped, building, scaffolded, or planned. The roster is the source of truth.
What AI Launch Kit does — and what it does not do yet
Thirteen capabilities. Ten Installed. Three Platform Services. Status is honest — shipped, building, scaffolded, or planned. The roster is the source of truth.
The /platform page exists for one reason. A serious evaluator should not have to read between the lines. Every capability below names what ships today and what does not. No aspirational copy. No vague benefit claims. If something is planned, it says planned.
How the roster is organized
AILK's 13 capabilities split into two groups. Installed — customers clone, configure, and deploy. Lives in apps/* and @ailk/*. The codebase ships the capability; the customer operates it on their own infrastructure. Competes against templates, frameworks, and libraries. Platform Services — AILK operates on api.ailaunchkit.ai. OSS client SDKs keep the protocol open. Competes against managed SaaS. Status taxonomy: shipped means customer-observable end-to-end in main. building means active in-flight work — the surface exists but is not complete. scaffolded means types and contracts are in place but no end-to-end user-observable surface yet. planned means roadmap commitment exists; no active work today.
Installed capabilities (10) — ships with the repo
Clone the repo and all ten Installed capabilities are in your codebase. Eight are fully shipped. Two are building.
1. Discoverability — shipped
The structural layer that makes AILK sites findable and citable across SEO, AEO, and GEO. Ships the 45-entry schema registry with per-type Zod validation. Typed JSON-LD builders compiled from frontmatter. Site-identity emission (Organization, Person, LocalBusiness). ailk audit CLI that runs pre-launch and in CI. /llms.txt and raw-MDX URLs. Hosted schema-pack delivery, per-site trend measurement, and Layer 3 referral aggregation from GA4, Search Console, and Vercel logs are planned Pro-tier additions, not yet shipped.
2. AX (Agent Experience) — shipped
The capability that lets agents — and any non-browser caller — find, understand, and operate AILK sites through the same typed substrate that powers the human UI. Ships the MCP server with stdio and HTTP transports. 14-tool catalog (9 read, 3 conversion-write, 2 dev tools). HTTP API with CI-enforced 1:1 parity to the MCP surface. .well-known/mcp.json and .well-known/ai-plugin.json discovery. Versioned API routes at /v1/. The agent-context provenance primitive — the durable record of which agent made which edit — is building.
3. Content Pipeline — shipped
The end-to-end path from content source to validated, queryable content the rest of the system consumes. Ships the content-adapter contract. MDX adapter via @ailk/cda-filesystem. Per-page-type frontmatter Zod validation. Build-time content projection for edge runtime. Structured-data extraction feeding the JSON-LD pipeline. Sanity and Payload adapters are planned — both OSS, both tracked as open issues.
4. Integration — scaffolded
The bidirectional transport layer connecting AILK to external systems. Ships first-party @ailk/api-client, paid client SDKs (billing-client, marketing-api-client), BYO-credentials pattern via @ailk/env, and Stripe webhook signature-verification primitives. What does not ship yet: outbound webhook delivery with signing and retries, OAuth ingestion from GA4 and Search Console, API-token ingestion from Vercel logs, and OpenAPI generation from Zod schemas. Integration is substrate present; no end-to-end integration surface today.
5. Customer Memory — building
Lead capture, subscriber management, and callback requests — persisted as durable customer records. Ships Lead, Subscriber, and Callback models with database persistence. Form, HTTP, and MCP capture parity. Operator notification email. Per-site rate limiting at capture. What is planned, not shipped: Pro routing pipeline — firmographic enrichment, deduplication, routing rules, auto-responder emails, and webhook fan-out to CRM, Slack, and custom URLs. The Pro pipeline depends on Integration's outbound webhook mechanism, which is also planned.
6. Theme & Component System — shipped
The runtime look-and-feel substrate — design tokens, components, sections registry — that determines how AILK sites render and how customization happens. Ships @ailk/theme design tokens, @ailk/ui React component library covering layout, navigation, content blocks, and forms, typed sections registry (name to Zod for validated MDX composition), and RTL logical-CSS support with html dir wiring. White-label branding suppression via @ailk-paid/branding is planned for the Agency tier.
7. AI App Substrate — shipped
The opt-in streaming-AI surface that lets the customer's site host its own AI features — chat, content generation, recommendations. BYO Anthropic key. Zero overhead when unused. Ships @ailk/ai Anthropic provider wrapper, streaming response API without server-side buffering, dynamic-import zero-overhead pattern, and BYO Anthropic key enforcement via ANTHROPIC_API_KEY. Content-pipeline RAG integration is planned — content adapters exist but the RAG orchestration layer does not.
8. Scaffolding & Authoring — building
The workflow from "I want a site" to "deployed, edited, evolving site" — with agent assistance throughout. Ships create-ailk scaffolder (pnpm create ailk@latest), three-peer-app project skeleton with project.yaml, .claude/ directory bundle with 8 skills (extract-design-from-reference, suggest-site-pages, scaffold-page, add-schema, audit-site, scaffold-auth, scaffold-commerce, provision-config), brand_assets/ and screenshots/ contracts, and one-command Vercel deploy from templates. @ailk/cli operator commands are scaffolded with stubs only. The first-site walkthrough on ailaunchkit.ai is the active resource plan. Cursor, Lovable, and Bolt starters are planned.
9. Localization — shipped
Multi-locale infrastructure across content authoring, page routing, schema emission, and agent-driven editing. Ships [locale] route segments, defaultLocale and supportedLocales site-config schema, inLanguage frontmatter to JSON-LD propagation, hreflang link tag emission on multilingual pages, per-locale audit coverage, parallel locale corpora under content/ (content/en/, content/es/), and RTL support. Agent-driven translation MCP tool — orchestrating content rewrites, locale routing, and per-locale schema enrichment — is v2 roadmap, not shipped.
10. Auth & Identity — shipped
Who is acting — operators editing their site, programmatic clients calling APIs, and agents operating tools. Ships Better Auth integration with User, Session, Account, and Verification models. API tokens and refresh tokens with scopes. OAuth provider surface. Operator dashboard sign-in (Google, GitHub, magic-link). Locale-aware auth middleware. Agent identity (Phase 3 credential issuance) and Enterprise SSO, SAML, and SCIM are planned.
Platform Services (3) — operated by AILK on api.ailaunchkit.ai
Platform Services are hosted and operated by AILK, not self-deployed by the customer. Two are building or scaffolded. One is fully planned.
11. License & Billing Infrastructure — building
The signed-JWT issuer plus checkout, subscription lifecycle, customer portal, and the hosted operator dashboard. JWT tiers claims enforce the paid boundary at runtime — upgrades are JWT re-issues, not redeploys. Ships license-issuer JWT service with asymmetric-key signing, license-client verification (static, service, hybrid modes), license manifest with tier vocabulary, Stripe Checkout and subscription billing, and seat-billing honor-system with opt-in telemetry. What is building: the Customer Operator Dashboard — the unified billing-portal and per-site management surface. Routes are scaffolded; the billing-portal views and per-site management screens are open work.
12. Fleet Management — planned
The Agency-tier capability for operating multiple AILK sites as a portfolio — cross-site analytics rollup, fleet-wide configuration, and the agency-operator surface. What ships today: the agency tier entry in commercial.tiers and the fleet-management feature claim reserved in the license manifest. What does not ship yet: no @ailk-paid/analytics-rollup package, no agency-operator dashboard routes, no multi-site license consumption patterns. Fleet Management is 90+ days post-OSS launch. Join the /agency-waitlist if fleet management is a requirement today.
13. Explainability & Audit — scaffolded
The durable trace of every agent action on every site — the trust substrate that unblocks Phase 3 agent identity and transactional MCP tools. Ships observability substrate (Pino + OpenTelemetry), server-side telemetry events (lead-captured, purchase-completed), and Stripe webhook event capture. What does not ship yet: MCP-tool invocation tracing with correlation IDs, before/after diffs on high-stakes writes, customer-facing review surface for agent actions, and tamper-evident append-only storage. The explainability story is substrate present; the durable agent-action trace is not yet customer-observable.
Frequently asked questions
How do I know which tier I need?
The OSS substrate is complete — every schema, the MCP server, the AEO CLI, all eight scaffolding skills. Pro and Pro Plus add operational capability: the planned lead-routing pipeline, support, and multi-locale workflows. If you are evaluating whether to install OSS at all, the foundation is complete. If you need the Pro routing pipeline or fleet management, read /pricing.
The Agency tier is listed as planned. What does that mean exactly?
Planned means a roadmap commitment exists — the tier name is reserved, the feature claim is in the license manifest — but no implementation is active today. 90+ days post-OSS launch is the current target. Join the /agency-waitlist to get notified when it ships.
Integration looks thin. Is the BYO-credentials pattern really all that ships?
Client SDKs ship, Stripe webhook signature verification ships, BYO credentials via @ailk/env ships. What does not ship yet is outbound webhook delivery, OAuth ingestion from GA4 and Search Console, and OpenAPI generation. Those are planned. The Integration status is honest — substrate present, no end-to-end surface yet.
Can I deploy today and rely on the planned capabilities shipping later?
Yes for the OSS core. Discoverability, AX, Content Pipeline, Theme, AI App Substrate, Localization, Auth, and the scaffolding workflow are all shipped. The gaps are additive — Pro-tier capabilities that add to a working foundation, not holes in the foundation itself.
Two decisions from here
Clone the OSS and build on a complete foundation today. Or book a Launch Service call and have it deployed in two weeks.