GrepfoxGrepfox
BLOG · AI & AGENTS

Choosing an LLM stack: OpenAI, Claude or self-host

Provider choice is an engineering decision, not a brand preference. The trade-offs that actually matter when picking a model stack.

Macro shot of a printed circuit board

Clients rarely ask "which model is best?" anymore. They ask which stack they can build on for two years without regret. Different question, better question.

The dimensions that matter

  • Task fit: long-context reasoning, tool use, multilingual support — benchmark on YOUR tasks, not leaderboards.
  • Data boundaries: what may leave your infrastructure, and under which agreement.
  • Cost shape: per-token pricing vs fixed GPU spend, and how your traffic actually looks.
  • Operational maturity: evals, fallbacks and rate-limit behaviour under load.

Our default answer

We build provider-agnostic by default — OpenAI, Claude or self-host behind one interface — so the model is a config value, not an architecture.

What that looks like in practice

Treat the model id as configuration: swapping provider: openai for provider: claude should be a one-line change, not a migration project.

The stack that wins is the one you can swap out.
RELATED READING
ALL POSTS →
Dark code editor with dense source listing
AI & AGENTS

Shipping AI agents to production: what actually breaks

Demos are easy; production is where agents meet ambiguity, rate limits and angry edge cases. A field checklist from the last year of deployments.

JUN 2, 20261 MIN READ
Analytics dashboard with charts on a screen
AI & AGENTS

Evals before vibes: measuring agent quality

You cannot improve what you do not measure, and "it feels smarter" is not a metric. How we build eval suites that catch regressions before users do.

MAY 18, 20261 MIN READ
Tidy developer workspace with monitor and notes
AUTOMATION

The boring automation that pays for itself

The highest-ROI automation we ship is rarely glamorous: report generation, data syncs, handoffs between tools. Boring is a feature.

MAY 5, 20261 MIN READ