Beach.
A different shape for AI-enabled applications.
Seven-year-olds playing football.
Every new framework, every new protocol, the whole industry sprints towards it at the same time. MCP, A2A, A2UI, ACP — four protocols in eighteen months. Each arrival is treated as a reason to re-architect the application.
Something else will arrive next. And the whole team will run to the other side of the pitch.
What if the application
didn't have to move?
Beach is an application scaffold whose interior is protocol‑agnostic and whose edges are protocol plug‑ins.
Inbound and outbound protocols are interchangeable parts. The middle of the application doesn't see them. When the standards change — and they will — a new edge plug-in lands. The interior is untouched.
The opaque interior.
Inbound protocols on the top. Outbound on the bottom. The middle — router and manifest registry — sees neither.
The middle stays opaque.
-
01
Nothing in the middle sees protocols.
Routing and correlation work in events and manifests, not HTTP, not SSE, not MCP.
-
02
Nothing at the edges sees other edges.
An adapter knows its own protocol. It does not know what else is mounted.
-
03
New protocols arrive as edges, never as interior changes.
Domain logic, participants, routing rules, data — none of them move.
ESBs failed because the middle accumulated business logic. Beach's middle carries none. The rule is enforceable by inspection.
Not the centre.
"A fancy, probabilistic interface for querying frozen, compressed data and the conceptual relationships between it."
— a Fortune 500 architect, on the current generation of LLMs
Architectural consequence
An LLM is one kind of participant. So is a deterministic handler. So is a small fast classifier. So is a long-running process. So is whatever arrives next.
The same architecture absorbs all of them. Applications built around an LLM-at-the-centre will need rebuilding when the next thing arrives. Applications built around the router-and-manifest centre will not.
Your domain logic, your participants, your routing, your data — none of them move.
You are permanently at the edge of the standard.
The claim is structural, not aspirational. It is the consequence of the architectural insulation.
Removing the obvious mis-readings.
Not a runtime
Your application keeps running if Beach disappears.
Not a gateway
It sits inside the application, not between applications.
Not a framework
It tells you the shape of the interior, not how to fill it.
Not a garden
No vendor relationship, no subscription, no roadmap dependency.
Not a protocol
It adopts existing open protocols rather than competing with them.
Not a logic container
Domain logic never lives in the middle. The rule is enforceable by inspection.
A different category — not a competitor.
| Project | Category | Where Beach sits |
|---|---|---|
| Salesforce Agent Fabric | Enterprise control plane | Above Beach. Beach can be catalogued by it. |
| Google ADK | Agent framework | Adjacent. Beach mounts A2A/A2UI as edges. |
| Dapr Agents | Agent runtime | Adjacent. Beach has no runtime dependency. |
| Mastra | LLM framework | Complementary. Use Mastra inside Beach. |
| agentgateway | Inter-app proxy | Complementary. Run Beach behind it. |
| Beach | Application scaffold | Inside the application. Protocol-agnostic interior. |
Beach runs alongside most of these. The competitive question isn't "which one" — it's "why isn't there a Beach-shape between your interior and your protocol edges?"
Most of the industry is investing in canals.
Someone in the corner is building a steam locomotive.
That's all. We just thought you'd want to know.