The full, reproducible evidence behind the integration page. Three real DigitalOcean GenAI app-agents, run locally and in-process on one Mission SDK runtime — no DigitalOcean cloud — measured on tenant isolation, shared machinery, and a governed tenant action. Every comparison is classified — this is conformance, not a scorecard.
| Experiment | Native role | ReDevOps addition | Result | Classification |
|---|---|---|---|---|
| DO-A Tenant isolation | naive shared runtime | tenant-scoped access | 3/3 cross-tenant denied · 0 wrong | REDEVOPS_DELTA |
| DO-A In-tenant preserved | — | own-scope work admitted | 3/3 admitted | PARITY |
| DO-A Shared machinery | rebuild per app | provide once | 5 once vs 15 rebuilt | REDEVOPS_DELTA |
| DO-B Governed action | tenant agent publishes | authority · approval · replay | 0 unauthorized · 0 duplicates | REDEVOPS_DELTA |
| DO-C Three real apps | DO agents answer | one runtime, tenant-isolated | 3/3 ran · 3/3 isolated | PARITY |
| DO-D Cache isolation | shared cache key | tenant-namespaced keys | no cross-tenant bleed | REDEVOPS_DELTA |
| DO-E Telemetry | per-app agent spans | one Mission-root nesting | preserved (nested) | REDEVOPS_DELTA |
Three DO apps — telegrambot, nutrients, vibexgen — share one runtime, each a tenant with its own grants and private context namespace. ReDevOps scopes every access to the acting tenant: a cross-tenant read (telegrambot reading nutrients' context), or an action outside an app's grants (nutrients rendering a reel), is denied by default. Native, a naive shared runtime would run all 3/3; ReDevOps denies each with 0 wrong, while admitting 3/3 own-scope actions. And the production machinery — context, retry, replay, governance, telemetry — is provided 5 times once by the runtime, not 15 times rebuilt across the three apps.
One app's consequential action (vibexgen publishing a reel) runs only through a Mission. No grant ⇒ 0 unauthorized. Grant but no approval ⇒ parked, 0 publishes. Approved ⇒ exactly once. Replay ⇒ 0 duplicates. No other tenant can trigger or duplicate it.
A support reply (telegrambot), a nutrition suggestion (nutrients) and a reel caption (vibexgen) — three real DO GenAI agents — run end-to-end on one shared runtime. All 3/3 ran, and all 3/3 stayed tenant-isolated: each reads only its own namespace, and a cross-tenant read is denied. The runtime shares the machinery without sharing the state.
Each run writes a reproducibility record — framework version, model ids, per-finding classification, and a content-addressed result digest.
// reproducible · local, no DigitalOcean cloud · github.com/redevops-io/redevops-integrations/integrations/digitalocean · integration page · architecture article