Compute infrastructure

MicroVMs

Your compute, consumption and credits. In one place.

Connect your projectUse your project ID and agent token to access its workspace.

Request microVM access or a higher quota

Enter your project and token above, then describe what you need. Limits apply to all your microVMs on this node. Allocate the minimum needed by your application.

Small footprint. Full control.

A workspace for your workloads.

Run native binaries or containers in an isolated microVM. Connect your project to manage execution and keep an eye on spending.

Rest when idle. Wake on demand.Serverless execution hibernates after 15 minutes of inbound inactivity.

Usage you can account for.Track compute, persistent storage and network against prepaid credits.

Your runtime. Your choice.Native applications, optional Docker and direct SSH access.

Machine status

—

Selected machine

Allocated resources

—

vCPU / RAM

Available credits

—

Prepaid project balance

Compute / ON hour

—

Credits · storage & network separate

Project machines

Selected microVM

No machine deployed

Your next workload starts here.

This project has no microVM yet. Create one here to run native applications or optional containers.

Serverless

Network & application access

Endpoints for this microVM

Network policy

—

Public address

—

Application URL

Not availableOff

Guest portSetup guide

Visitor access

The application URL is locked until you set visitor credentials.

Public TCP/UDP ports

Slot	Public port	Protocol	Guest port	Status

Choose a public slot, then the guest port your application listens on inside the VM. A guest port of 22 exposes SSH. Free a slot row to release it.

Custom domains

Serve this microVM on your own hostname, without GAP Basic Auth.

Execution preferences

On demand

Execution mode

Idle time · min

Serverless hibernates after inbound inactivity. Always-on keeps compute running and requires operator approval. Silent connections may need to reconnect after hibernation.

Spending budget

Execution limit

0 credits spentNo budget set

New budget · credits

Saving starts a new budget period. At the limit, execution stops; retained storage stays billable.

Project billing activity

Usage accumulates in one row per VM state period.

Activity	CPU · sec	RAM · GiB-sec	Disk · GiB-hours	Network · in / out	Credits

Usage checkpoints appear every few seconds while resources are allocated.

Resource pricing

Resource / billing unit	Credits per unit

CPU and RAM are billed during ON time. Stored data, including hibernation snapshots, remains billable while OFF. Zero credit starts a 72-hour storage retention period; recharge before deletion to preserve your data.