Kimi K3
These notes explain how the independent kimi3.org workspace handles access, deployment, context, source boundaries and comparison evidence.
Kimi K3 uses a same-domain pricing and PayPal checkout path before protected production model calls are enabled. The browser never receives provider credentials. The runtime endpoint reports whether checkout and model access are configured.
Google login is configured for the independent kimi3.org workspace. It creates a kimi3.org account session only and does not grant an official Kimi or Moonshot account. The browser is sent to Google for authorization, while the client secret and session-signing secret remain in Cloudflare Worker secrets.
For development, run the Node server locally and connect it to a compatible server-side model backend with environment variables or a local secure credential store. Production uses a Cloudflare Worker with static assets, runtime metadata, checkout entry and D1 analytics.
The workspace is designed for long-context tasks such as briefs, notes, code, website plans and research outlines. Attachments are summarized into the request payload, and the current conversation is kept local so users can continue the same working thread.
kimi3.org is an independent implementation with an original interface. It does not copy official private source code, account systems, protected artwork or billing flows. Public docs describe that boundary so users can evaluate the workspace honestly.
Comparisons should use reproducible journeys: first visit, mode switch, file attachment, prompt response, refresh restore, export, protected runtime gate and mobile layout. Benchmarks are useful only when the prompt, environment, model setting and pass criteria are recorded.