CCJK Pricing & Cost Guide
The official site does not sell fictional SaaS tiers. CCJK itself is free and open source; real cost comes from your model provider, relay choice, and infrastructure.
CCJK CLI
The core product is free and open source, with the npm version synced from the official snapshot.
- โMIT licensed, official entry point is npx ccjk
- โCurrent npm latest 13.5.7 synced at March 14, 2026
- โCurrent public GitHub release v9.4.1
- โIncludes onboarding, memory, Agent Teams, remote, and presets
Model & Provider Cost
You pay your model provider or aggregator, not the CCJK official website.
- โRead the provider operating model before integrating
- โPrefer first-party access when possible
- โUse isolated keys, budgets, and environments for relays/aggregators
- โTreat configuration export and review cadence as risk controls
Team & Infrastructure
Team cost mostly comes from remote control, sync, self-hosting, and governance rather than software licensing.
- โremote, cloud, browser, and MCP costs depend on deployment
- โSelf-hosted storage and network controls add infra overhead
- โProduction setups should enforce HTTPS, CORS, secrets validation, and fail-fast config
- โTreat CCJK as an environment layer, not a SaaS seat product
How to judge cost
Confirm whether you are using a first-party provider, OpenAI-compatible endpoint, or aggregator/relay.
Confirm whether this is local individual use or a team setup with remote control, sync, and self-hosting.
Use provider-page recommendations before deciding to deploy. Do not reduce the decision to a price table.
FAQ
Is CCJK paid software?
No. The core CLI is free and open source, and the official website does not offer the fictional Pro/Team/Enterprise subscriptions that were previously shown here.
Why do I still have costs?
Costs usually come from model APIs, relays, storage, remote servers, and internal governance, not from CCJK licensing.
When should I use aggregators?
Only when they create clear value in price, reachability, model coverage, or resilience. Otherwise prefer first-party access and isolate any aggregator usage.
What should teams evaluate?
Look at official-source baseline, operating model, payment method, review cadence, freshness, and blocking factors on provider pages.
The official snapshot keeps npm version, public release, and README positioning current so this page stays aligned with upstream reality.