Skip to main content
Two jars showing stones placed before sand and sand placed before stones

1. Quality

We are here to outdo LiteLLM, and quality is how we get there. An AI gateway does not have to be written in Python. Go was chosen because runtime behavior, deployment shape, and long-term maintainability matter. The jar is a useful reminder: if you fill it with sand first, the larger stones will not fit later. In GoModel, the big stones are experience, programming language and architecture. The sand is the smaller work: features, functions, tests, and fixes. Big stones come first.
We still respect LiteLLM and people behind it. They got there first, helped a lot of builders ship fast, and proved the category mattered.

2. Efficiency

That applies to the runtime and to how we work. We use tools that help us move faster and keep quality high, including Claude Code, Codex, CodeRabbit, and GitHub Copilot.

3. Transparency

GoModel is open source, and we want to keep it sustainable. That may eventually mean charging large enterprises so the project can keep shipping.