Origin vs kulono — data sovereignty
Cursor Origin is a cloud git forge for the agentic era. kulono is a Principal-bound Home: code, models, and data under your TC-ID — with optional Resident provenance. Same trend, opposite trust model.
不训练 · 不出域 · 可迁移
binding kulono-20260723
invite-only
Cursor Origin
Cloud promise
- Hosted inside Cursor / SpaceXAI cloud
- No self-host product
- “Privacy Mode” style commitments
- Agent runs in vendor cloud
- AI tracking can be stripped by git hooks
kulono Home
Physical / tenant fact
- Self-hosted artifact Home (git · models · data)
- TC-ID Principal is the only tenant key
- No independent password store; handoff body-only
- Writes optionally annotate Resident agent_id
- Append-only provenance receipts on Home
| Dimension | Origin | kulono |
|---|---|---|
| Deployment | Cloud-only | Self-hosted Home |
| Data leaves your perimeter | Yes (vendor cloud) | No by default (tenant Home) |
| Identity | Cursor account | ticalcode TC-ID + optional Resident |
| Open registration | Cursor paid plans | Invite-only (sovereignty gate) |
| Agent provenance | Enterprise / peelable | Home receipts (append-only v0) |
| Models + data plane | Not the product | Same Home as git |
| Competes as | GitHub-class cloud forge | Rule-layer artifact Home |
What “better” means here
- Not more stars, more merge throughput, or a bigger public marketplace.
- Yes default place agents write under a revocable Principal, with identity + provenance Origin cannot physically promise.
Facts about Origin (early Beta, GitHub sync as source of truth, no self-host) tracked in research note CURSOR_ORIGIN_VS_KULONO_2026-08-18. This page is a product contrast, not legal advice.