PulseAugur
EN
LIVE 09:10:17

Developer builds Kin middleware for centralized AI app control

A developer has created a middleware layer called Kin to manage AI application access and permissions, addressing concerns about AI labs controlling user accounts and data. This layer centralizes connections to various AI models and tools, allowing users to authenticate once and control AI actions with granular settings like approval workflows and blocking. Kin also centralizes logging and provides a master switch to pause all agents, offering a unified control point that can be switched between different AI applications. AI

IMPACT Provides a unified control layer for AI applications, enhancing user control over data access and permissions.

RANK_REASON The item describes a new middleware tool for managing AI applications.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Developer builds Kin middleware for centralized AI app control

How we ranked this

Signal score
3 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
The item describes a new middleware tool for managing AI applications.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Same-day
Cluster formed today. Ranking reflects the current source set at time of score.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Troy Fortin Jr ·

    Your AI apps should answer to you, not to their lab

    <p>I use models from four labs every week, and every one of them wanted my accounts connected inside its own app, with its own idea of what was allowed. I couldn't see what any of them did with that access, and there was no single switch to stop them.</p> <p>So I put one layer in…