Open weights vs closed models
What control do you gain, and what responsibility comes with it? · updated 2026-09-07
Downloadable weights enable local operation and modification. They do not automatically provide training data, unrestricted permissions, affordable hardware or a secure application. Hosted models trade some control for managed infrastructure; the comparison starts with your requirements.
The concern
Released weights can be copied and modified beyond the provider's control. Application safeguards matter, but a provider cannot revoke every local copy after finding a problem. Evaluation should examine the extra harmful capability access adds over existing alternatives.
The counter-view
Independent access supports reproducibility, adaptation, competition and use without a model API. These benefits can matter even when a hosted competitor scores higher. Openness aids scrutiny, but the license and released components determine what is possible.
Compare the release, license, hardware and deployment. A closed API can be practical; an open release can be valuable without leading on every task.