Govern AI delivery into commercial-grade apps and websites
The public layer contains the basic workflow and documentation. Pro delivery uses two independent gates: the private GitHub invitation authorizes release downloads, while the trusted signed license authorizes the compiled CTKF Pro runtime. Neither gate replaces the other.
Customer flow
Select a plan, enter the destination GitHub username, complete payment, accept the private repository invitation, checksum the compiled release, activate the license, and confirm the runtime reports ACTIVE.
Dual-gate delivery
The GitHub invitation permits download of the private customer release. The trusted, expiring license permits that release to run Pro commands. An invitation alone cannot run Pro, and a key alone cannot download private updates.
Source boundary
CTKF is not fully open source. Customers receive a compiled runtime and approved paid assets, not the main engineering repository, Git history, merchant credentials, signing keys, or operator ledgers.
Manual fallback
If automatic checkout is blocked by WeChat account review, scan the QR code or add WeChat gsq_weifeng, send your GitHub username, choose monthly or yearly Pro, and wait for manual operator approval before access is issued.

Term and renewal
Licenses expire at the plan boundary. Daily authenticated maintenance removes expired GitHub access unless a newer active entitlement protects the same customer.
Operator use
The owner manages secrets through a DPAPI vault and Vercel, keeps Pro assets private, reviews payment and provisioning evidence, and never grants commercial access from personal donations.
Need product details? Read the public overview at CTKF AI site. Never publish your private access receipt or license key.