Menu
Serverless microVMs · Pay as you go

Your runtime.Serverless.

Run your app in a Linux microVM. Scale to zero when idle, automatically resume on the next request, and pay for compute while it runs.

Deploy a microVM Serverless without a VM
Scale to zeroAuto-resume on requestBuilt-in AES-256
LINUX RUNTIME.
SERVERLESS LIFECYCLE.▤ MICROVMSƒ PAY AS YOU GO⌁ SCALE TO ZERO◈ STORAGE↗ AUTO-RESUME
01 / Serverless microVMs

Real Linux.
Zero idle compute.

Your runtime, billed by usage. Run native binaries, scripts or optional Docker containers with SSH, persistent disks and public ports. In serverless mode, GAP hibernates your microVM after 15 idle minutes and resumes it automatically when a request arrives. Compute billing pauses while hibernated; stored data and network usage remain billable.

01

Run. Pay for usage.

Choose the CPU and RAM your app needs. Pay for active compute at published rates, with a prepaid balance and visible consumption.

02

Idle. Scale to zero.

After 15 minutes without inbound activity, GAP hibernates the runtime. Memory state and persistent files are retained for resume. Compute usage stops; storage continues to be charged.

03

Request. Resume automatically.

Incoming traffic triggers a resume, so your application can serve requests again. Resume takes time: use always-on mode for workloads that need continuous availability, subject to operator approval.

THE SERVERLESS ENGINE
RUNTIME STATUSRunning.
COMPUTE USAGEActive

Your application serves requests. Compute is billed while it runs.

Illustration · time compressed · hibernation after 15 idle minutes.
Storage remains billable. Actual resume time varies.
02 / Serverless services · No VM to manage

Static sites. Functions. Data.
Without a VM.

Publish static sites, run serverless functions and store data with SQLite, KV and objects. Use the platform API directly, without creating or managing a microVM.

Illustrative previews · no live project data
SQLITE + KV + OBJECTS

Give your app a memory.

Structured data, fast key-value storage and files. Persistent, project-scoped and ready for your next idea.

▤   app.projectsSQLITE
idnamestatus
001my-next-idea● building
002something-great● ready
003your-turn—
Explore persistent data
SANDBOXED JAVASCRIPT

Ideas in. Functions out.

Deploy versioned logic directly and run it in a constrained sandbox. Your agent writes the code.

// A little logic. Real capability. const value = await gap.kv.get("visits"); return { visits: value };
✓ Reviewed releases↗ Controlled HTTP egress
Explore functions
WEBSOCKETS + REPLAY

Make it feel alive.

Chat rooms. Collaborative apps. Live dashboards. Connect people and agents with scoped realtime channels.

⌁   channel: your-next-appILLUSTRATION
Explore realtime
STATIC SITES + HTTPS

From localhost to the world.

Publish a site release. Connect your own domain with automatic HTTPS. Keep it private, or make it public.

⌑   your-app.example
Your idea lives here.BUILT BY YOUR AGENT. HOSTED BY GAP.
Explore site hosting Custom domains
And the work keeps running.
Scheduled functions for recurring tasks.
Room to experiment.
Eligible verified customers receive one $1 MicroVM trial per public network.
03 / Agent-native by design

Less configuration.
More creation.

A straightforward HTTP API. Explicit limits. Copyable examples. The kind of documentation your agent can actually use.

01

Give your agent the instructions.

One document describes the API, authentication, resource limits and security model.

02

Let it assemble your backend.

Verify your email, create an identity and project. Add data, functions and realtime as your app needs them.

03

Ship something people can use.

Publish the frontend, attach a domain and connect your application to its backend.

GAP CLOUD / QUICKSTARTHTTP
# Create your agent identity
# Follow /docs for email verification on this node.
curl "$NODE/v1/registration"

# Complete the /docs signup flow; save its token as $TOKEN.
# Create a project for your application.
curl -X POST "$NODE/v1/cloud/projects" \
  -H "Authorization: Bearer $TOKEN"

# Your project. Your application. Your next idea.
Use your node URL as $NODEFull reference ↗
04 / Freedom, with boundaries

Autonomous doesn't
mean unguarded.

Let your agent build ambitiously. Keep permissions and resource limits explicit.

Understand the security model

Project-scoped access

Owner credentials stay server-side. Browser clients use scoped tokens.

Sandboxed functions

Direct publication and constrained execution for agent-written code.

Controlled connections

Approved HTTP destinations, bounded responses and execution timeouts.

Built-in AES-256 encryption

Built-in encryption for microVM disks and saved hibernation memory, available on encryption-enabled GAP nodes. See encryption coverage.

Your next idea starts here

Stop at a prototype?
Not your agent.

Give it the instructions. Tell it what you want to build. GAP supplies the place to run it.

COPY THIS INTO YOUR AGENTRead https://gap.geta.team/agents.md and help me deploy my app on a serverless GAP microVM with usage-based compute and automatic resume. Use static sites, functions and data services without a VM where appropriate.

Prefer to explore first? Read the docs or self-host a node.