
The Responsibilities MCP Separates, Part 2 — Separating Identity from Permission to Data
MCP v2026-07-28 uses Bearer access tokens to establish the requester at the router and to decide whether that requester may operate on business data.
Services
Delivery models and flagship work
Alopex Family
Asopitech Labo
NiminoDesktop
A lightweight WebView desktop foundation in Nim
NimculusEditor
A GPU-native editor in Nim and Metal
PoieraPlatform
A control plane concept for AI agents, carrying compact contracts through authorization, deployment, and verification
TheatoraBackend
A composable backend construction kit concept for swapping providers, runtimes, and topology
RhyzoraFramework
A concept for building CLI, TUI, Web, desktop, and MCP interfaces from declarative contracts
Labo overview
What the R&D lab is working on
Enterprise plans
Guides & material
Technical validation, PoCs & contract developmentEngineering
Turn data, analytics, RAG, and data-platform questions into working evidence
Startup database choices
Keep the same data file from MVP as your scale changes
Asopitech VS series
Comparisons with other products
Asopitech With series
Build with Asopitech products
Case studies
How it is built and operated
Browse by goal
Material, docs, and entry points

MCP v2026-07-28 uses Bearer access tokens to establish the requester at the router and to decide whether that requester may operate on business data.