Skip to content

SolutionsFor platforms

Give your users computers of their own

A sandbox or an instance for each of your customers, made through the API, with usage counted per customer.

Read about billing and usage

Python
from glac import Glac

glac = Glac()
for customer in ["acme", "globex"]:            # one sandbox each
    glac.sandboxes.create(metadata={"customer": customer})
month = glac.usage(start="2026-10-01T00:00:00Z",
                   end="2026-11-01T00:00:00Z",
                   group_by="metadata.customer")
# month["data"]: a group a customer; month["prices"]: each meter's

A wall, a meter and a limit

Running your customers’ code takes a wall around each, a meter and a limit. Here each is a microVM of its own, usage is counted by the hour under your labels, and a project or a sandbox can have a spend limit.

Choose the shape

One app for all your customers, an instance for each by a key in the request, or a sandbox for each that your product drives. Every one a microVM of its own, in the region you choose.

An app for your customers: shared instances, or one instance a customer by key, awake for requests and asleep after them.
A sandbox a customer: commands and files through the API, snapshots and forks.

What your platform gets

  • Kept apart: a microVM for each customer, and rules for what each may reach.

  • All through the API: REST, five SDKs and an MCP server.

  • Usage per customer: label what you make for each, and read it to bill them.

  • A spend limit per customer, monthly, on a project or a single sandbox.

  • A project per customer, if you like, with its own keys and limit.

  • Talk to us for larger limits, regions or terms.

Read the docs

Illustrative previews

Resell

You may sell Glac’s compute on to your own customers, inside your product and at your own prices. You answer for what they do with it, and they follow our Acceptable Use Policy, as you do.

  • Label each customer’sUp to 64 labels on a sandbox, such as customer: acme. An app’s instances carry the app’s labels, and a key’s instance its key.
  • Read usage by labelGET /v1/usage?group_by=day,metadata.customer gives each customer’s quantities by the day or the hour, with the prices to multiply them by. Labels count as they were when the usage happened.
  • Cap what each can spendA monthly limit in US dollars on a project or on one sandbox. At the limit its sandboxes sleep, and nothing new is made, until the limit is raised or the month ends.
  • What there is notSub-accounts for your customers, and a console under your own name. Your customers use your product; we see one account, yours, and bill it.

Measured, not promised

Medians on bare metal with nothing else running: a best case, and we say so. How we measure

to wake a customer’s sleeping sandbox1
3.5 ms
for the call that woke it, sent to answered1
6.7 ms
to put it to sleep, with its memory and processes1
2.3 ms

The products it uses

A month, worked out

Five hundred customers, each with a sandbox: about $1.10 a customer at the list prices, before your margin. Estimate your own

The use

  • 500 customers, each with a sandbox of 2 vCPUs and 4 GiB.
  • Each awake 40 hours in the month, its CPU busy 15% of that time, 2 GiB of its memory in use.
  • Asleep the rest of the month, each keeping about 1 GB.
  • 2 GB sent to the internet for each.

A month at the list prices

$550.00

  • CPU21.6 billion CPU-ms × $0.01 / M$216.00
  • Memory40,000 GiB-h × $0.008$320.00
  • Traffic out1,000 GB × $0.004$4.00
  • Kept asleep500 GB-months × $0.02$10.00

On Paid this month is $548.00: the $5 fee, and $543.00 past what its inclusions cover, from your balance at the same prices.

Build it into your product

A key, then a sandbox for your first customer. For volume, regions and terms, talk to us.

EnterpriseThe API reference