Skip to content

Cube

Run any OCI image as a Cube, a service at its own address (an app, in the API). Instances start when requests come and sleep when they stop; every deploy is a version you can roll back to.

업데이트

이 페이지는 아직 한국어로 번역되지 않아 영어로 보여 드립니다.

Cube runs an image as a service, called a Cube, and in the API an app. You give it an image and a port. It gets an address under glac.run, and it can have your own domains too. When a request comes, the platform starts an instance of it in milliseconds. When no requests come, the instances sleep and cost nothing but what they keep. Each deploy is a new version: it takes the traffic once it is ready, and you can send the traffic back to an earlier one.

The names

Cube is the product’s name, and each service it runs is a Cube. The API’s calls for it are /v1/apps: an app, its versions and its instances. The SDKs’ objects (App) and the command line’s options use the same word, and so do these pages.

The commands are glac cube …, and glac deploy for short. The SDKs’ namespace is glac.cube (client.Cube in Go, cube() in Rust and Java), the MCP server’s tools are cube_*, and the console’s page is Cube, under Compute. workers is another name for each of them (glac workers …, glac.workers, the tools worker_*), kept for code written with it; the SDKs mark it deprecated.

When to use Cube

  • A web service or an API that should answer at its own address and cost nothing while nobody calls it.
  • Many small services of one project that find each other on a private network, such as a web app, a background worker and a database. A Compose file can be imported as they are. See services and Compose.
  • One instance per user, session or tenant, picked by a key in the request, each with its own memory and disk. See keyed instances.

To run code that a program or an AI agent sends at run time, with commands, files and terminals, use Sandbox. Both run on the same machines, at the same prices.

How it works

  1. Deploy. glac deploy IMAGE (or POST /v1/apps) makes the app and its first version. The platform pulls the image, starts it once on the machines of each region the app runs in, waits until it is ready, and saves it as a template.
  2. Serve. A request at the app’s address goes to a machine in the region it comes in at. An instance that is awake answers it. Otherwise one is woken, or made from the template, which takes milliseconds because the service is already running in the template.
  3. Sleep. An instance sleeps a while after its last request ends: how long is picked from the app’s traffic, so that it stays awake through gaps a sleep would cost more than, and sleeps at once when requests are far apart (sleep_after_ms, three seconds unless you say, is the most). An instance that stays asleep for an hour is deleted; the next request makes a new one.

What it costs

Cube and Sandbox have the same prices. An instance pays for the CPU it uses and the memory it holds while it is awake. Asleep, it uses no CPU: one held paused in the machine’s memory still pays for that memory, and one whose memory is saved pays only for what it keeps, by the GB-month. An instance that is deleted keeps nothing.

과금 항목 가격 무료(하루 할당량) 유료(월 포함 사용량)
CPU(연산하는 동안) 100만 CPU-밀리초당 $0.01 100만 CPU-밀리초 6000만 CPU-밀리초
메모리(깨어 있거나 메모리에 일시 정지된 동안) GiB-시간당 $0.008 6 GiB-시간 250 GiB-시간
요청(큐브로, 그리고 샌드박스 링크를 거쳐 들어오는 요청) 100만 건당 $0.30 100,000 1000만
잠든 인스턴스가 보관하는 데이터(메모리와 고유 디스크) GB-월당 $0.02 스냅샷과 드라이브를 포함해 데이터 합계 15 GB 스냅샷과 드라이브를 포함해 데이터 20 GB-월
북미에서 인터넷으로 나가는 트래픽 GB당 $0.004 리전 구분 없이 3 GB 리전 구분 없이 1 TB
유럽에서 인터넷으로 나가는 트래픽 GB당 $0.004
아시아 태평양에서 인터넷으로 나가는 트래픽 GB당 $0.01
로그: 큐브가 출력해 보관되는 내용 GB-월당 $0.02 출력 200 MB 10 GB-월

On Free, what an instance uses comes out of the day’s quotas; Paid includes a quantity of each meter every month, and past it usage is paid from the balance at these prices. See pricing and plans.

Limits of each plan

무료 유료
최대 인스턴스 크기 2 vCPU, 4 GiB 8 vCPU, 16 GiB
큐브 10 500
앱 하나의 환경 변수와 시크릿 수 64 128
한 리전 안 앱 하나의 인스턴스 수: max_instances 미지정 시 / 최대 2 / 5 50 / 500
1시간에 만들 수 있는 큐브와 버전 수 10 500
엣지마다 큐브 하나에 허용하는 초당 요청 수 50 제한 없음
동시에 깨어 있는 인스턴스 수 5 500
깨어 있는 인스턴스의 vCPU 합계 10 500
깨어 있는 인스턴스의 메모리 합계 10 GiB 1,000 GiB

The awake instances, their vCPUs and their memory are counted for the whole account: sandboxes and instances of every project together. Every limit is on the limits page.

Next

  • Quickstart: deploy an image, change it, roll it back, with the command line, Python or the console.
  • Deploys and versions: what makes a version, what happens when one fails, rollbacks.
  • Instances and scaling: when instances start, sleep and are deleted, how many there are, regions.
  • Keyed instances: one instance per key, kept with its memory and disk.
  • Addresses and protocols: the default domain, your own domains, private apps, HTTP/2, gRPC and WebSockets.
  • Services and Compose: several services of one project, their private network, shared variables, a service with a Drive.
탐색 메뉴

검색어를 입력하세요…

↑↓ 이동↵ 선택Esc 닫기