WORKSPACE

A computer in the cloud.
For you and your AI to work in.

Choose CPU, memory, and disk to develop your project in an isolated virtual machine. Set up dependencies, connect your coding AI, or work directly through the shell.

I want to use WorkspaceSee pricing and estimate usage ↗

Code and services
in the same Workspace.

Choose CPU, memory, and disk for your project. Dependencies and services run in the cloud, separate from your computer's configuration.

Compare configurations ↗

Available operating systems.

Choose Ubuntu, Debian, or Alpine based on your project's tools and dependencies.

Ubuntu

Debian

Alpine Linux

How to use your Workspace.

  1. 01

    Set up your project

    Choose the resources and operating system. Use the shell to clone the repository and install dependencies.

  2. 02

    Work with your AI or through the shell

    Connect an MCP-compatible client to work on the project. You can also run commands directly.

  3. 03

    Review the result

    Check commands and output in the shell. To test a web app, start the service and forward its port to your computer.

Access through the shell.
Manage it in the dashboard.

~/meu-projeto $ npm run dev

Preparing environment…

Application is running.

Port forwarded → your browser

$

Access through the virtual shell.

Run commands and monitor processes through the runvibe_ virtual shell. Review command history and results to see what you and your AI ran.

Access through the dashboard.

Create and manage Workspaces in the runvibe_ interface. Choose resources, check the environment status, and open the shell to work on the machine.

Forward ports to your application.

Start the application in the Workspace and forward its port to your computer. Open the local address in your browser to test changes.

Connect your AI tools.

Connect an MCP-compatible tool such as Codex, Claude Code, or Cursor to work in the Workspace.

CodexKiroGeminiChatGPTGrokDeepSeek

What you can do in a Workspace.

Build a feature

Ask AI to change the code and test the feature alongside the project's services.

Investigate an issue

Check logs and run commands to reproduce the behavior and understand its cause.

Try a project

Install the tools you need without changing your computer's local setup.

Run your services

Use Docker Compose to run application services inside the Workspace.

Create reusable images

Install project tools and dependencies, then save an image of the prepared environment. Use it to start other compatible Workspaces or Executions without repeating the setup each time.

Fork to experiment

Create an independent copy of the Workspace to test a change or investigate an issue while keeping the original environment intact.

Every Workspace has
its own kernel.

Each Workspace has its own kernel, separate from the server hosting the machine and from other Workspaces.

This separation keeps project processes inside the virtual machine and reduces the exposure of the server and other environments to running code.

Authenticated access to the Workspace.

Shell operations go through an authenticated interface and are routed to the corresponding Workspace. Internal communication with the machine stays private.

Review access permissions and credentials provided to code to control what it can access from the environment.

Explore access controls ↗

Credentials with Secrets.

Store credentials in Secrets and reference them in the application's environment variables. The process receives the values without requiring you to write them into code.

Usage based on resources
and runtime.

Your plan has a monthly subscription that includes a balance for platform usage. The Workspace uses this balance according to its configuration and runtime. Pausing stops execution charges; the subscription and image storage follow their own billing rules.

Pause and continue in the same Workspace.

When you pause, the Workspace saves the machine state, including files, memory, and processes. When you resume, that state is restored so you can continue in the same environment.

If you restart the machine, your files remain, but running processes are stopped.

Your dollar balance renews monthly and does not roll over. Add a top-up if you need more usage.

Estimate my usage ↗

Running

Resources in use · hourly billing

Paused due to inactivity

Execution charges stopped

Work resumed

Execution charges resumed

Frequently asked questions.

Am I charged while the Workspace is paused?

CPU, memory, and disk charges for the Workspace stop while it is paused. Separately created and stored images continue to incur storage charges.

How long will my balance last?

It depends on the selected configuration and resources used. Use the simulator to convert your balance into usage hours or calculate a task's cost in dollars. Estimate my usage ↗

Can I connect my AI? Is the tool included in the subscription?

You can connect an MCP-compatible AI tool to operate the Workspace through the shell. A runvibe_ subscription includes a dollar balance for platform usage; the AI tool is billed separately.

Can I use the Workspace without AI?

Yes. Use the virtual shell to install tools, run commands, and work directly on the project. Use the Workspace on your own or connect an AI tool whenever you need one.

When should I use an image or create a fork?

Use an image to reuse a prepared environment in new compatible Workspaces or Executions. Create a fork to experiment in an independent copy of the current Workspace. To simply pause and continue in the same environment, pause and resume the Workspace.

Can I use multiple Workspaces at the same time?

Yes. Workspaces share your dollar balance. Each machine consumes that balance based on its configuration and runtime.

When should I choose a Workspace or an Execution?

Choose a Workspace to develop and keep working on a project. Use an Execution for a task with a defined start and finish, such as running a script or processing files.

Keep exploring runvibe_.

Request access to work
in a Workspace.

View plans ↗