Open Weights Are a Layer, Not a Strategy: What Kimi K3, Tencent Hy3, and ByteDance Seed Actually Hand Over
Teams that treat model selection as an open-source purity test inherit responsibilities they never budgeted for. This framework replaces that test with a layered control map and a decision tree, making it possible to match a model's delivery structure to a team's actual operational capacity, compliance requirements, and exit strategy.
The open-vs-closed binary collapses under real procurement pressure. A nine-item control matrix — covering model assets, version pinning, deployment location, workflow operation, product distribution, feedback visibility, verification responsibility, switching cost, and undisclosed items — reveals that Kimi K3, Tencent Hy3, and ByteDance Seed hand control to adopting teams at fundamentally different layers. Kimi K3 delivers full weights and a custom license, granting strong exit rights but also transferring runtime, security, and legal review burdens. Tencent Hy3 pairs Apache 2.0 weights with cloud APIs, third-party platforms, and product integrations, shortening the distance from model to business entry point while keeping its feedback loop supplier-held. ByteDance Seed ships no weights but pushes control into the creative object itself: image selections, layers, materials, and audio character timelines.
Each layer of control gained comes with a matching responsibility. Model assets demand infrastructure and security ownership; workflow control demands prompt, tool, and asset maintenance; product distribution demands user data and content governance. A decision tree and five procurement questions — what you cannot lose, whether you can refuse an upgrade, whether official evals reproduce your harness, who fixes failures, and what assets migrate — reframe the selection from "who is more open" to "what control do we actually need and what are we willing to carry."
Calling a model 'open' because its weights are downloadable obscures that the heaviest production costs — verification, infrastructure, security patching, and legal review — land on the team that downloads them.
Tencent's simultaneous weight release and product integration challenges the assumption that open weights and vendor lock-in are opposites; the lock-in shifts from the model file to the product distribution channel.
ByteDance's Seed delivery inverts the usual control hierarchy: instead of controlling the model, teams control the creative object directly, which may matter more for design and media pipelines than weight access ever would.
The Kimi model card's admission that harness differences change benchmark scores is a rare piece of candor that should reset how every team reads public leaderboards — and it applies to all three vendors.
Feedback visibility is the sleeper control item: a supplier can truthfully claim a feedback loop exists while giving adopters zero visibility into what feedback matters or how it shapes the next model version.
Migration cost is not about export buttons; it is about whether prompts, evaluation sets, tool protocols, layer files, and audio tracks survive a vendor switch — and most teams discover this only when they try to leave.