Free Tier — Included

1. Single-Folder Sandbox

Drop SRT-1 into any folder. It starts its own engine on a dedicated port, derived from the folder path. No config needed.

When you ask the AI to "fix the login flow," it only sees auth code. No bleed from payments. No confusion from frontend CSS. Pure, isolated intelligence.

── Your machine ──
auth-module/ → Engine on port 7483  · 12 files, 47 functions
payments/ → Engine on port 8192   · 8 files, 31 functions
frontend/ → Engine on port 9104   · 24 files, 89 functions
api-gateway/ → Engine on port 7821 · 6 files, 22 functions
admin-panel/ → Engine on port 8640 · 15 files, 53 functions
Each engine: independent process, independent manifest, independent dashboard.
Pro Tier — $9/month

2. Workspace Connector

Modules don't exist in a vacuum. Auth calls payments. The gateway routes to both. You need a bird's-eye view.

The Workspace Connector acts as a parent orchestrator. It doesn't re-read your code. Instead, it queries each running Sandbox engine on its port, collects their live manifests, and builds a unified cross-module dependency map.

── Workspace Connector ──
$ srt1-workspace --root ./my-platform
Discovered 5 running Sandbox engines
Collected 5 manifests (242 functions total)
Mapped 24 cross-module imports
Circular dependency: auth ↔ api-gateway
Zero re-indexing. The Connector reads what's already running.