CKCopilotKit Space Lab

Pricing

Pricing for CopilotKit readiness receipts

CopilotKit Space Lab pricing with monthly and yearly plans, NOWPayments hosted checkout, readiness receipts, and implementation handoff.

Pricing

Plans for adoption work that needs a saved receipt

Switch billing before checkout. Every checkout payload preserves plan, billing, period, and planId.

Starter

Solo builders validating one CopilotKit surface

$14.50/mo

Due today: $174 for one year. Annual billing is 50% less than monthly. No automatic renewal.

  • Browser readiness evaluator
  • Three saved integration receipts
  • React or Next.js setup notes
  • Email support for checkout and activation
Checkout Starter annual

Scale

Platform teams standardizing agentic UI adoption

$99.50/mo

Due today: $1,194 for one year. Annual billing is 50% less than monthly. No automatic renewal.

  • Multi-app portfolio readiness map
  • Runtime, package, and observability review notes
  • Private architecture intake and rollout scorecard
  • Priority setup for paid implementation handoff
Checkout Scale annual

Capabilities

Built around real CopilotKit adoption decisions

The evaluator packages SDK, AG-UI, shared state, runtime, and approval decisions into a commercial workflow instead of repeating an open-source README.

readiness-score

CopilotKit readiness score

Input: Framework, runtime endpoint, agent backend, state scope, UI pattern, and deployment target

Process: Checks whether the app can support CopilotKit provider wiring, AG-UI events, streaming, shared state, and user approval paths

Output: Adoption score, missing pieces, implementation notes, and paid receipt

framework-map

Framework adoption map

Input: React, Angular, Vue, React Native, or mixed surface requirements

Process: Maps the target surface to CopilotKit packages, provider placement, UI components, and runtime boundaries

Output: Framework-specific action map, package path, and handoff task list

agent-runtime

Agent runtime boundary review

Input: LangGraph, Python service, Node runtime, MCP tools, or custom agent backend

Process: Separates browser-side tools from server-side agent work and identifies where events, state, and approvals should flow

Output: Runtime boundary receipt with integration risks and next actions

upgrade-receipt

Package and upgrade receipt

Input: Current package versions, npm target, framework version, and migration concern

Process: Compares public CopilotKit package paths with the requested surface and flags upgrade or licensing blockers

Output: Version-aware adoption note, package list, and checkout-ready team export