Why a permission layer?

Software used to wait for instructions. The current generation of AI doesn't: give a large language model tools and a goal, and it becomes an agent — it reads your systems, writes code, files tickets, sends messages, and spends money, in a loop, with limited supervision. Gartner projects that 40% of enterprise applications will embed task-specific AI agents by the end of 2026, up from under 5% in 2025.

That creates a new class of insider. Every agent is an identity that isn't a person, holding permissions somebody granted in a hurry, touching data nobody inventoried, running up a metered bill nobody reconciles. The tooling to see and control this — agent identity, permission enforcement, MCP security, spend governance — is being built right now, by startups and platform giants at once, faster than most teams can evaluate it. Standards bodies are formalizing the risks just as fast: OWASP now maintains a Top 10 for Agentic Applications.

The people responsible — security leaders, platform engineers, CTOs, and increasingly CFOs — are being asked to approve agent deployments faster than the tooling is maturing. Two questions decide most of it:

• Security: what may this agent touch, who said so, and how would we know if it did something else?
• Cost: what does it spend, on which models, and would the same work run at a tenth of the price?

The Permission Layer exists to keep those people current in five minutes a week: a curated briefing, one deep explainer, a maintained map of the vendor landscape, and a running signal on model and infrastructure pricing. Vendor-neutral, always — the editorial policy is public.