← all benchmarksIntegration page →
Benchmark · integrations · DigitalOcean GenAI

DigitalOcean GenAI × ReDevOps — evidence

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.

Frozen environment
framework DigitalOcean GenAI (OpenAI-compatible) — three real app-agents on one runtime runtime Mission SDK 0.2.0a0 · Context Runtime 0.2.0 — one shared runtime, in-process answer model gpt-4o-mini (OpenAI-compatible endpoint) — the agent loops run locally apps telegrambot.ai · nutrients.tech · vibexgen.io — three tenants, no DO account scoring cross-tenant accesses denied · shared machinery count · exactly-once governed publish

Results — DO-A through DO-E

ExperimentNative roleReDevOps additionResultClassification
DO-A Tenant isolationnaive shared runtimetenant-scoped access3/3 cross-tenant denied · 0 wrongREDEVOPS_DELTA
DO-A In-tenant preserved—own-scope work admitted3/3 admittedPARITY
DO-A Shared machineryrebuild per appprovide once5 once vs 15 rebuiltREDEVOPS_DELTA
DO-B Governed actiontenant agent publishesauthority · approval · replay0 unauthorized · 0 duplicatesREDEVOPS_DELTA
DO-C Three real appsDO agents answerone runtime, tenant-isolated3/3 ran · 3/3 isolatedPARITY
DO-D Cache isolationshared cache keytenant-namespaced keysno cross-tenant bleedREDEVOPS_DELTA
DO-E Telemetryper-app agent spansone Mission-root nestingpreserved (nested)REDEVOPS_DELTA
DO-A · tenant isolation across one shared Runtime (the flagship, no LLM)

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.

DO-B · governed tenant action

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.

DO-C · three real apps on one runtime

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.

Reproduce (local, no DigitalOcean cloud)

git clone https://github.com/redevops-io/redevops-integrations cd redevops-integrations/integrations/digitalocean ../../.venv/bin/python conformance.py # DO-A..E + classification tally ../../.venv/bin/python examples/shared_runtime.py # DO-A (no LLM; three tenants) ../../.venv/bin/python examples/governed_tenant.py # DO-B (a tenant publish governed as a Mission) ../../.venv/bin/python examples/three_apps.py # DO-C (three real DO agents, gpt-4o-mini, cached)

Acceptance bundles

Each run writes a reproducibility record — framework version, model ids, per-finding classification, and a content-addressed result digest.

results/do_a_shared_runtime.json DO GenAI · tenants result_digest sha256:00d656100dd50146 results/do_b_governed_tenant.json DO GenAI result_digest sha256:eec1d3e48a421b2a results/do_c_three_apps.json DO GenAI · gpt-4o-mini · 3 apps result_digest sha256:d62cff6afaf9cb2d adapter_commit d09736c · mission-sdk 0.2.0a0 · context-runtime 0.2.0
// conformance summary   DigitalOcean suite over all findings: 9 REDEVOPS_DELTA · 2 PARITY · 0 EXPECTED_IMPLEMENTATION_DIFFERENCE · 0 BUG. The PARITYs are in-tenant work admitted and the three apps' own outputs (unchanged). Neither is a win nor a bug.
Limitations. Runs entirely locally: the three app-agents are real OpenAI-compatible calls, but DigitalOcean GenAI identity and knowledge-base wiring are represented by tenant scopes rather than a live DO account. The tenant/isolation and cache-key mechanics are a deterministic fixture; the shared-machinery figure is a capability count, not a performance number. Reported straight; nothing averaged into a single headline.

// reproducible · local, no DigitalOcean cloud · github.com/redevops-io/redevops-integrations/integrations/digitalocean  ·  integration page  ·  architecture article

DigitalOcean is a trademark of DigitalOcean, LLC. Independent integration, not a DigitalOcean product or endorsement; uses no DigitalOcean services.