Three real DigitalOcean GenAI app-agents — telegrambot.ai, nutrients.tech, vibexgen.io — run in-process on ONE Mission SDK runtime. No mock, no sidecar approximation.
Unlike the other slices, the DigitalOcean differentiator is not a new agent framework. DO gives lean apps a great managed agent stack; the gap this series is about is that every app still rebuilds context, retry, replay, governance and telemetry. ReDevOps gives all the apps one runtime that provides that machinery once — with tenant isolation so no app reaches another's context, authority or cache.
Every access is scoped to the acting tenant. A cross-tenant read, or an action outside an app's grants, is denied by default — a naive shared runtime would run each — while each app's own in-scope work is admitted 3/3.
Context, retry, replay, governance and telemetry are provided once by the shared Runtime — five capabilities — instead of rebuilt in each of the three apps (fifteen re-implementations). Cache keys are tenant-scoped: no cross-tenant bleed.
A support reply, a nutrition tip and a reel caption — three real DO GenAI agents — run end-to-end on one runtime, each reading only its own namespace. A tenant's reel publish is governed with approval and 0 duplicates on replay.
The isolation and cache-key mechanics are deterministic — the value is the enforced boundary. The three app-agents are real; the shared Runtime keeps them isolated while sharing the machinery underneath.
// DigitalOcean GenAI (OpenAI-compatible) · Mission SDK 0.2.0 · Context Runtime 0.2.0 · local, no DO cloud · github.com/redevops-io/redevops-integrations