YOUR COMPUTE, ON DEMAND
A workspace.
A GPU. Your files.
Start a Colab runtime, connect from VS Code, and work with your selected Drive folder.
Open your workspace
Enter your controller token. Your Google credentials stay on the server.
Finish server setup
Runtime allocation stays disabled until these requirements are met.
GOOGLE ACCOUNTS
Connect your accounts
Connect through Google’s consent page. Credentials are stored privately on this controller.
Colab Pro+
Not connectedUse the Google account with your Pro+ subscription.
Open Google consent page ↗Google Drive
Not connectedDrive permission is broad on this trusted controller. The runtime receives access only to your selected folder.
One-time Google Drive app setup
- In Google Cloud Console, create or select a project and enable the Google Drive API.
- Configure Google Auth Platform for your private app. Add your Google account as a test user while testing.
- Create an OAuth client of type Web application. Add this exact Authorized redirect URI:
Download the client JSON and upload it below. It contains the app’s client secret; it stays on this controller.
Testing mode gives Drive refresh tokens a seven-day lifetime. Before regular CI use, follow Google’s publishing and verification requirements.
After approval, Google returns to this dashboard and saves Drive credentials automatically.
Select your configured Drive folder after signing in.
Sign-in links expire after ten minutes and work in this browser session. Account changes are disabled while a runtime is active.
NEW SESSION
Choose your compute
SELECTED SESSION
No runtimeReady when you are.
Each workspace has its own GPU runtime, connection and lifetime.
No activity yet.
Connect from VS Code
Append these public host keys to ~/.ssh/known_hosts, then append the SSH configuration to ~/.ssh/config. Change IdentityFile if your private key has another name.
In VS Code, choose Remote-SSH: Connect to Host and select . The gateway entry only forwards traffic. Open /workspace/project; your Drive folder is mounted at /workspace/data.
Use the API
Run these commands in your terminal or CI. Set WORKSPACE_API_TOKEN using the controller token from the administrator, or a GitHub Actions secret. This token can manage every workspace. A browser sign-in link is not an API token; Google credentials are not needed.
1. Configure your environment
The workspace ID follows your dashboard selection. After creating a new workspace, set WORKSPACE_ID to the ID returned by that request.
2. List workspaces
3. Start a workspace
Replace the example public key with your Ed25519 public key, then choose the GPU and maximum hours. A successful request returns HTTP 202 and an id. HTTP 409 means capacity is full or the request conflicts with the configured GPU or lifetime limits.
4. Check status and retrieve SSH details
Poll the status every few seconds until it becomes ready, then retrieve the SSH configuration and host keys. SSH details return HTTP 409 until the workspace is ready. A failed or stopped status ends the wait.
5. Destroy the selected workspace
This stops its programs and drains pending Drive uploads before releasing the GPU. The request returns HTTP 202; poll status until stopped. A workspace remains stopping while cleanup is incomplete.