devBox
The sandbox the job runs in.
Approved sources only. On-prem or cloud. Native mGateway policy. The analyst starts in Slack or the AI chat the desk already uses. 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 or 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 without giving the job a standing unsupervised identity.
Start here
Bring one decision.
A 2 to 4 week sprint on a live decision. You get the decision record, the verification trail, and the method your team can run next.