Blog · one trend at a time
One new AI trend at a time, taken apart properly: how it works, where it breaks, and whether you should use it.
No. 033 · Orchestration
As teams wire apps and agents to dozens of model providers, the sprawl of point-to-point connections becomes the real risk. An AI gateway turns that sprawl into one governed chokepoint for cost, security and routing.
· 13 min read
No. 031 · Orchestration
Instead of training one model that sees, hears and reads, you can wire together specialists that already do each job well — and a controller that decides who answers what.
· 13 min read
No. 025 · Orchestration
Dumping the whole conversation into the model every time is not reliability, it's waste. The 2026 systems that win budget what the model sees, step by step.
· 13 min read
No. 023 · Orchestration
Instead of building one model that understands text, images, audio and video at once, teams are wiring together specialists through a controller that decides who does what. It's cheaper, and sometimes better.
· 15 min read
No. 014 · Orchestration
Instead of training one giant model to see, hear and speak, the newest systems route each task to a specialist and stitch the results together with a language model playing traffic controller.
· 13 min read
No. 010 · Orchestration
A centralised system can tell hundreds of sites what to do without ever moving their data or losing control when the line drops.
· 14 min read
No. 007 · Orchestration
Long-running agents chain dozens of LLM calls and tool actions together. Without saving progress after each step, one crash or one paused approval means paying for and repeating all of it.
· 13 min read
No. 006 · Orchestration
Docker Agent and 10xScale Agentflow treat the model, tools, memory and routing logic as separate slots you can swap, not one script you rewrite. Here is how the config actually holds it together.
· 14 min read
No. 003 · Orchestration
Agents that remember where they stopped can pause for approval, survive a crash and pick up exactly where they left off. Here is the machinery that makes that possible, and when it is not worth building.
· 13 min read
No. 002 · Orchestration
As companies go from a dozen AI agents to tens of thousands, a new governance layer is emerging to watch and stop agents nobody on the risk team built.
· 13 min read
No. 001 · Orchestration
Chaining agents and tools into one pipeline sounds like the obvious next step after single-shot AI. The gap between benchmark quality and executable output is where it breaks.
· 13 min read
A new explainer lands most mornings. The feed carries each one the moment it publishes.
Subscribe by RSS