devBox
The sandbox the job actually runs in.
Approved sources only. On-prem or cloud. Native mGateway policy. The analyst starts in Slack or chat. The work happens here.
-
01
Native mGateway integration
Every model and tool call leaves through mGateway. Identity and allow-list are not optional.
-
02
On-prem or cloud
Same controls in the firm's boundary or in a hosted workspace. VPC / no-egress is a first-class posture.
-
03
Approved libraries only
Artifact and registry-style control so jobs cannot pull arbitrary packages. Only what IT allow-lists.
-
04
Locked environment
The job cannot see the open internet except through approved paths. No casual paste into a public model.
-
05
Secure file share
Controlled exchange between the user's machine and the workspace. Not an open mount.
-
06
Contained source control
git the workspace is allowed to use, not the firm's entire estate by default.
-
07
Scheduling when needed
Recurring or long-running jobs (frequent company research, data loads) without giving the job a standing unsupervised identity.
See a one-hour research run.
Book a working session. An analyst starts the job. You review the first deliverable.