Skip to content

Instantly share code, notes, and snippets.

@luisjunco

luisjunco/open-models-vs-closed-models.md

Last active July 30, 2026 09:30
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save luisjunco/65fe6907730b7e79ec4f2712d7ff690c to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save luisjunco/65fe6907730b7e79ec4f2712d7ff690c to your computer and use it in GitHub Desktop.
Download ZIP
Open Models vs. Closed Models
Raw
open-models-vs-closed-models.md

Open Models vs. Closed Models

Open-weight models (e.g. Kimi3, Llama, Mistral, Phi)

Advantages

  • Can fine-tune on your own data
  • More privacy and control (can run on your own infrastructure)
  • No per-token API costs (you pay for compute instead)
  • Can run offline or in air-gapped environments
  • Full control over model version and deployment

Disadvantages

  • Need to manage infrastructure and deployment
  • Higher engineering effort
  • Hardware costs (especially for larger models)
  • Often slightly less capable than the best closed models

Closed models (e.g. GPT, Claude, Gemini)

Advantages

  • Very easy to get started (API)
  • Often more capable
  • No infrastructure or maintenance required
  • Continuous improvements from the provider

Disadvantages

  • Pay per token/API usage
  • Limited customization compared to open-weight models
  • Less control over data handling and model updates
  • Vendor lock-in (dependent on the provider)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment