86 articles tagged with LLM.
A 1T-parameter MoE model with open weights coming doesn't make self-hosting the right call for most teams.
Haiku 5.5 is cheap enough to stop rationing subagent calls, but the 75% savings claim only holds if your prompts are short.
Nano Banana 2.1 is a routing update, not a new model to chase, and it mostly matters for batch and multi-reference image work.
Most moderation, routing, and triage calls aren't generation problems. Clef proves it by answering in 38.8 milliseconds instead of seconds.
Google shipped a 1M-token output ceiling and strong cyber-defense benchmarks, then handed the keys to almost nobody. Here is what that gating pattern tells you.
OpenAI priced GPT-6.1 Sol at a fifth of GPT-6 Astra and called it nearly as good at agentic coding. That claim is now a routing decision, not a headline.
Same sticker price, a real-world cost drop from speed and token efficiency. Here is who should move today and who can wait a sprint.
Most teams shipping retrieval do not need a dedicated vector database. Here is where Postgres runs out, and which specialist actually helps when it does.
ChatGPT, Claude, and Grok degraded together when Azure East US failed. Gemini stayed up. Multi-provider failover does not help when your providers share a substrate.
LLM and agent apps add a new attack surface on top of every classic one. The threats that are specific to AI, mapped to the OWASP lists, and the boundary controls that actually contain them.
You cannot prove an LLM app is safe by reading its prompt. Here is how to adversarially test it before attackers do.
A working security engineer's tour of the ten failure modes unique to LLM apps, each paired with a fix you can ship this sprint.
