DevBox
DevBox is an ECS instance preconfigured with common development environments, such as those for Python and Java. After creation, you can connect to it with a single click from your local IDE, such as VS Code or Qoder. This direct connection to the cloud environment simplifies configuration and lets you start developing immediately.
Key advantages
Advantage | Description |
Out-of-the-box | Offers three categories of preconfigured development environments: languages (Python, Java, Node.js, Go), frameworks (FastAPI, LangChain, Flask, Django, AgentScope), and AI coding assistants (Hermes Agent, Claude Code, Codex, OpenCode, QwenCode), reducing environment setup time from hours to minutes. |
Cost-effective | Lightweight instance types (2 vCPU / 2 GiB) start as low as 0.1 yuan/hour. DevBox supports on-demand start/stop and release. Billing for computing resources is paused when the instance is stopped. |
Frees up local storage | Code, dependencies, and build artifacts are stored in the cloud. Your local machine only runs the IDE UI, reducing the strain on your local disk. |
AI security sandbox | DevBox is fully isolated from your local system. All AI coding assistant operations run in the cloud, preventing accidental changes to your local files or data. |
Direct IDE connection | Supports one-click connections with popular IDEs like VS Code, Qoder, and Cursor, eliminating the need for complex SSH configuration. |
Instant deployment and verification | After development, you can deploy and validate your application directly in DevBox, bypassing traditional CI/CD pipelines and reducing verification time from minutes to seconds. |
Quick start
Go to ECS Console - App Management and click Create DevBox.
On the Create DevBox page, configure the following parameters:
Region: Select the region where you want to create the DevBox instance. Choose a region near you to reduce network latency.
Deployment Mode: Select New ECS Instance or Use Existing ECS Instance. If you have an idle ECS instance, you can configure it as a DevBox.
Billing Method: Select Pay-As-You-Go or Subscription. Pay-As-You-Go is suitable for short-term use and allows you to release the instance at any time.
Instance Type: Select the vCPU and memory specifications for the ECS instance. For lightweight development, we recommend the 2 vCPU / 2 GiB instance type (starting as low as 0.1 yuan/hour). For large-scale projects or AI model inference, choose a higher configuration.
Development Environment: Choose a pre-configured development environment image:
Language: Node.js, Python, Java, Go.
Framework: AgentScope, FastAPI, LangChain, Flask, Django, and more.
AI Coding Assistant: Hermes Agent, Claude Code, Codex, OpenCode, QwenCode, and more.
Click Next: Confirm Order. After confirming the configuration and costs, click Create Now.
After the instance is created, go to the DevBox details page and select your local IDE, such as Qoder, VS Code, or Cursor. Your browser automatically launches the selected tool and binds it to your cloud environment.
You can now run commands, install dependencies, generate code, and run tests directly from your local IDE, all while pair-programming with an AI.
Next steps
Stop and start your instance: You can stop your DevBox at the end of the workday to save on computing costs and restart it the next day to resume your work. When an instance is stopped, billing for computing resources (vCPU and memory) pauses, but charges for storage resources like the system disk and data disks continue.
Application release: To deploy code from your DevBox to a production environment, use application release management for continuous integration and deployment. For more information, see application release management.
Monitor and manage your instance: Go to the Service Instances page in the Compute Nest Console. Click the ID of your instance to go to the details page, where you can view the following information:
Overview: View the instance's running status, event statistics (scheduled O&M events, unexpected O&M events, instance billing events, instance security events), and associated resources.
Resources: View details of cloud resources associated with the DevBox, such as the ECS instance, VPC, and security group.
Monitoring: View real-time and historical monitoring metrics, such as CPU utilization, memory utilization, and disk I/O.
O&M: Perform operations and maintenance tasks, such as restarting or changing the configuration of the instance.
Cost analytics: View detailed cost breakdowns and trends for the instance.
Release the instance: If you no longer need the DevBox, you can release it at any time to stop all billing. Make sure to back up any important data before releasing the instance.
FAQ
Where are the files I edit and the code I generate in my local IDE saved? On my local machine or in the cloud?
All code and files are saved directly in your DevBox in the cloud. Your local IDE acts as a remote editor, connecting to the DevBox through an SSH tunnel to edit files stored on the instance.
What are the underlying cloud resources for a DevBox?
A DevBox is an ECS instance. It is preconfigured with common development environments and the necessary SSH files, allowing you to connect from your local IDE with a single click and bypass the manual environment setup process.
What common development environments are pre-configured in DevBox?
Currently, DevBox supports environments for the following: languages (Python, Java, Node.js, Go), frameworks (AgentScope, FastAPI, LangChain, Flask, Django), and AI assistants (Hermes Agent, Claude Code, Codex, OpenCode, QwenCode).
Can I stop a DevBox instance?
Yes. For example, you can stop your DevBox at the end of the workday. When the instance is stopped, billing for computing resources (vCPU and memory) pauses. You continue to be charged for resources like the system disk and data disks. You can restart the instance the next day to continue your work. For more information, see Economical Mode.
Can I use an existing ECS instance to create a DevBox?
Yes. On the creation page, you can choose to configure an existing ECS instance as your DevBox.
What should I do if my local IDE cannot connect to DevBox?
The initial connection can take 1 to 2 minutes, so be patient. If the connection fails, check if port 22 is open for inbound traffic in the security group of the ECS instance. If not, open the port and try again. For more information, see Use security groups.
Why is the price on the order confirmation page different from the reference price shown when I selected the instance type?
The "reference price" shown when you select an instance type is only for the computing resources (vCPU and memory). The final price on the order confirmation page is the total cost for all resources, which includes:
Instance type fee (vCPU + memory)
System disk fee (default: 40 GiB ESSD Entry cloud disk)
Public network traffic fees (billed separately based on actual usage and not included in the hourly rate). For more information, see Tiered Cumulative Billing.