Security and Safety

Required boundaries

The backend is the only public API, MinIO credentials never reach the browser, sandbox networking defaults to none, and allowlists require explicit policy. Thread ownership must guard every thread, file, stream, and download operation.

Executor controls

JobExecutor enforces maximum timeout, CPU, and memory values before acquiring a runtime. Restricted execution preparation can block imports, and runtime images are selected from configured profiles rather than arbitrary user images. Session locks prevent concurrent mutations of one workspace.

Planned storage controls

Presigned URLs are minted only after authenticated ownership, content-type, size, and operation checks. Object keys are namespaced by thread. The executor remains an internal service with service credentials rather than a browser-facing storage API.

Risks

The visible frontend API client uses any for SSE data and the current checked-out product backend is absent, so authorization and payload validation cannot be verified end-to-end. Add malware scanning, content sniffing, quota enforcement, audit logs, and tenant isolation before untrusted deployment.