OpenScaler documentation
How a dedicated Workstation works, where it runs, and what the first release is planned to include.
P0 is a single-region architecture pilot in Singapore. Public access, trial applications, and signed macOS downloads are not open. This guide describes the V2.4 architecture and staged rollout.
What is OpenScaler Runtime?
OpenScaler Runtime is the core cloud execution environment. In CLI mode, it runs coding agents on the Workstation’s dedicated Ubuntu server, where project files and development tools are stored.
OpenScaler Desktop is the client where you send tasks, approve actions, and review changes. The first release covers CLI workstations across Lite, Pro and Max.
The intended first-run workflow
- Install the signed macOS client when it is released and sign in.
- Choose an agent, its account region, an eligible Workstation Region, a plan, and a sleep policy. Confirm the instance region, network egress, and regional quote before creating the Workstation.
- Authorize the supported agent using its official flow or your own API credentials.
- Import a project through Git or file upload, then start an agent task in the project directory.
- Review task events and diffs, handle approvals, then commit or export your code.
Supported environments & scope
| Area | V2.4 release plan |
|---|---|
| Local client | Native macOS only at launch. OS versions and architectures will be announced with the installer. |
| Cloud environment | Dedicated Ubuntu EC2 instance in a private AWS network. |
| Persistent storage | 30 GB EBS system volume and a separate data volume of 100, 200, or 400 GB, depending on the plan. |
| Initial projects | Web, backend services, scripts, and general software projects. |
| Later phases | Evaluate Windows graphical workstations. |
Global access & Workstation Region
A Workstation is bound to a fixed AWS Region and Cell when provisioned. Reconnecting after changing networks or failing over to a gateway replica returns to the same Workstation. A move across regions requires explicit approval and a new eligibility and pricing check.
The planned unified entry point, connect.openscaler.ai, is part of the P2 routing rollout. Cloudflare Anycast handles edge access and Load Balancing handles entry-point health and failover. OpenScaler checks Workstation access, looks up the fixed Region and Cell, then routes to its gateway and the private EC2 instance. Reconnect can resume the event stream from the last confirmed sequence.
Singapore (ap-southeast-1) is the only P0 pilot region. P2 targets multi-region validation in Northern Virginia (us-east-1) and Singapore. Tokyo (ap-northeast-1) is a P5 candidate. A pilot does not indicate public availability.
P4 · Hong Kong optimized access
cn-connect.openscaler.ai is a candidate entry point for a separate P4 pilot to evaluate routes for China Telecom, China Unicom, and China Mobile through Hong Kong. Any public offering depends on line performance, cost, and operational requirements.
The access path, Workstation Region, and agent network egress are separate. Changing how you connect keeps the instance, projects, and persistent volumes in the original region. The Singapore P0 pilot continues to use its approved access path. Provider eligibility is checked separately.
Dedicated ISP egress and candidate pricing
The planned feature would reserve a static ISP IP for each eligible Workstation subscription. The proof of concept (PoC) covers requests from managed official agent processes to approved official endpoints. Shell commands, Git, browsers, and other VM traffic are outside this scope.
The feature is pending PoC validation. Default availability depends on written authorization, regional inventory, procurement terms including IP retention, and test results. Eligible users, regions, and endpoints must meet the applicable provider requirements. The Singapore P0 pilot keeps its existing approved access path.
| Plan | Monthly base fee | Per running minute |
|---|---|---|
| Lite | US$19.99 | US$0.003 |
| Pro | US$34.99 | US$0.006 |
| Max | US$64.99 | US$0.012 |
Agents, authentication & billing
P0 targets official Codex CLI and App Server, plus Claude Code through the official Agent SDK first or a structured official CLI adapter when needed. The supported capabilities, authentication paths, and regional eligibility must be validated before public release.
Use your own eligible agent account or API credentials. Regional and account eligibility is checked before provisioning. Your model provider bills model usage separately. The planned prepaid Workstation balance covers the regional base fee and running minutes.
Data, persistence & task lifecycle
Both EBS volumes are retained when the EC2 instance stops. Stopping ends running processes. Restarting restores access to persisted data and configuration.
Continuing eligible tasks after a client disconnect is a development goal, subject to approvals, budgets, and runtime limits. Git, file transfer, and project export are planned for the first release. Two-way Cloud Drive sync and mounting are planned for later.
P0–P5 rollout roadmap
- P0 · Singapore architecture pilot
Validate the native macOS client, dedicated EC2 and VM Agent, Codex and Claude adapters, authorization, approvals, diffs, and reconnecting to the original Workstation in one Region. - P1 · Runtime MVP
Provision EC2 and dual EBS volumes, validate prepaid Wallet and per-minute billing, and add Auto-Sleep and low-balance protection. - P2 · Regional rollout
Introduce the Global Control Plane, Regional Cells, and Cloudflare Load Balancing for US/Singapore routing and failover, while preserving the Workspace’s Region and Cell. - P3 · Cloud Drive
Add a separate HTTPS Sync Gateway and validate two-way sync, conflict handling, snapshots, and recovery. - P4 · Hong Kong network optimization
Evaluate the optional Hong Kong path and route selection in a separate pilot. - P5 · Expansion
Evaluate Tokyo and other regions, along with a Bare Metal KVM infrastructure adapter.
Windows is the first graphical workstation under evaluation. Availability and pricing will be announced after validation.
Release & pilot status
The Singapore P0 architecture pilot is not open to the public. We will publish the signed macOS installer, system requirements, available regions, and trial details here when ready.
View release statusUpdated November 20, 2026 · OpenScaler product specification V2.4