looking for architectural advice on integrating Dagger as the execution engine for an enterprise dev | Dagger | Page 1

We're building a Kubernetes-native developer platform where developers work inside per-user VS Code instances
(code-server pods). We want to give users the ability to run their dev/test workloads as OCI containers directly from their IDE terminal — mimicking local dev experience but leveraging the cluster.

What we're building:

A Rust microservice (oci-engine) that acts as our API layer — exposes GraphQL to our frontend and a CLI tool (devtest)
Arch. we are looking to do.
devtest CLI (Rust) → oci-engine (Rust, GraphQL) → Dagger Engine (DaemonSet)
we have few questions we look to get answered if possible ( really appreciate the hospitality)

haven't started yet sandboxing with dagger

One more question as well. Beyond one-shot test runs, we want users to keep services running for interactive development
(lets say docker compose up). Is Dagger designed for longer-lived workloads or primarily for ephemeral pipeline runs?

#looking for architectural advice on integrating Dagger as the execution engine for an enterprise dev