Fleet management for agencies is coming. Get on the list.
AI Launch Kit's Agency tier — fleet management, cross-site rollup, white-label, per-seat licensing — is 90+ days post-launch. The waitlist is open now. Pro handles per-site agency work in the meantime.
Fleet management for agencies is coming. Get on the list.
AI Launch Kit's Agency tier — fleet management, cross-site rollup, white-label, per-seat licensing — is 90+ days post-launch. The waitlist is open now.
Apache 2.0. Agent-ready. AEO-scored. Pro handles per-user agency work today — five seats covers a five-person team, thirty client deployments don't cost extra. Fleet management is post-launch. If fleet is a hard requirement, the waitlist is the right move.
Running a portfolio of client sites is a different problem
At one or two client sites, per-site setup is tolerable. Clone the repo, run the scaffolder, deploy the foundation, configure the schema, wire the Pro seat. Ninety minutes. Fine. At ten sites, the pattern costs structure you don't have. At twenty, it costs margin. At thirty, you're in a different business — operations — and operating with a single-site tool. The problems that emerge at portfolio scale are distinct from the problems a single-site agency faces. Schema configuration varies client to client. AEO gaps surface at different times across the portfolio. When a new AI search signal emerges — a new structured-data requirement, a new citation format, a new agent interaction pattern — applying it across thirty sites is a project, not a task. White-labeling the platform for a client who wants their own name on the dashboard isn't possible without tooling built for it. Per-seat licensing that reflects how agencies actually bill clients doesn't exist yet. These are not AILK bugs. They are the next tier's problem set. That tier is fleet management.
What ships in OSS and Pro, and what is deferred to the Agency tier
Today, on OSS and Pro: The full substrate ships in OSS — the typed schema registry of 45 page types, the first-class MCP server with CI-enforced parity to the human UI, the ailk audit CLI, and the agent-assisted scaffolding workflow. Pro and Pro Plus add operational capability: multi-locale workflows, priority support, the planned lead-routing pipeline. Pro is per-user — five agency seats at $249 per year. Client site deployments are not seats; thirty client sites don't cost extra at Pro. Pro Plus is $449 per user per month and adds Platform Services on top. What Pro does not have is fleet-level orchestration: centralized rollup, white-label, cross-site audit management, per-seat licensing structured for agency billing. That is the Agency tier. Deferred, waitlist now: Agency tier — fleet management, cross-site rollup, white-label, per-seat licensing — is 90+ days post-launch. There is no public timeline. Joining the waitlist signals demand, gets early access when the tier opens, and ensures you see it before it is announced broadly.
Four things fleet management has to do before it earns the name
The requirements are not Agency tier features on a roadmap. They are what any fleet-management system for a portfolio agency has to do. AILK builds toward them. The waitlist is how we calibrate the order.
Cross-site visibility in one place
Not tab-switching between thirty admin views. A rollup that shows AEO health, schema gaps, and citation status across the full portfolio at once. The gap surfaces where it exists, not where the agency happens to look next.
White-label without rebuilds
A portfolio agency billing under their own name needs a platform that presents under their name. White-label is a configuration, not a project. Clients who log into a dashboard should see the agency's brand, not the vendor's.
Per-seat licensing that matches agency billing
Agency engagements don't map onto per-user SaaS pricing. The agency seat and the client seat are different things. Fleet licensing has to reflect the engagement model — not force agencies to translate between their structure and the vendor's.
Schema propagation at portfolio scale
When a new structured-data requirement emerges, applying it across the portfolio should be a workflow, not thirty individual tasks. Changes to entity configuration, schema templates, or citation signals need to propagate from a fleet-level source of truth to every site that inherits from it.
Quick answers
What exactly does the Agency tier include?
Fleet management, cross-site AEO rollup, white-label configuration, and per-seat licensing structured for agency billing. The capability list is locked to what is documented — no features beyond those are confirmed. The complete capability boundary is enumerated at /platform.
Is there a timeline for the Agency tier?
No. Agency tier is 90+ days post-launch. There is no public ship date. If fleet management is a hard requirement for a current engagement, the waitlist is the honest path — it does not come with a date guarantee, but it ensures early access and early notice when the tier opens.
We run 20+ client sites. Should we use Pro in the meantime?
Yes. Pro handles per-user agency work today. Five seats at $249 per year covers a five-person team. Client site deployments are not seats — thirty client sites don't cost extra at Pro. The foundation ships on every client site: schema registry, MCP server, audit CLI, scaffolding. The citation work compounds on every engagement while the Agency tier is in development. The transition from Pro to Agency tier will be designed to carry over what is already deployed.
Join the waitlist
No timeline. Early access when the Agency tier opens. Pro handles per-site agency work in the meantime — the foundation is running on client sites today.