Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Compute options

Choose between serverless capacity and compute managed through grids.

Choose compute for the organization’s workloads. Admins manage servers and grids; Developers deploy to accessible grids or use serverless capacity when enabled. Viewers inspect resources.

Option
How it works
Good starting point for

Serverless CPU

Kinesis places CPU workloads on managed capacity matching their requirements

Getting started without managing servers

Dedicated cloud servers

Provision machines and compose them into grids

Workloads needing selected machine types and capacity you control

Your infrastructure

Connect machines and use them through grids

Bringing existing compute into the same deployment workflow

Serverless capacity

Serverless GPUs are currently paused. Serverless placement is CPU-only; configure RAM, storage and region requirements. GPU apps must target a grid. The runtime selects eligible CPU capacity. Tight filters reduce the machines that can run the app; a valid configuration does not guarantee capacity is immediately available.

Serverless usage is metered at resource level. CPU activity, memory, storage and network usage can contribute separately to cost. An idle CPU does not imply every other resource is free. Organization admins use Cost and the current pricing calculator for your workload.

Admins can turn off serverless capacity for Developers under Organization → Settings → Compute. Existing running apps keep running, but Developers must target a grid for new starts, rebuilds and changes that need new serverless machines. Admins retain serverless access.

Dedicated servers and grids

A server is a machine. A grid is the logical group your app targets. A grid can hold several servers, and an app can target more than one grid.

As an organization admin, open Servers in the portal to provision or connect machines, then compose them into grids. Developers select an accessible grid in the app’s Resources step. Organization URLs include the slug, for example /dashboard/acme/my-servers; the sidebar label is Servers.

Dedicated compute is billed through the servers. Hibernation stops compute billing while retaining the disk and its storage cost. A stopped app does not, by itself, confirm that its server is hibernated; inspect the server state and the grid's configured lifecycle behavior.

GPU configurations need at least one grid ID. In the API, hardware.gpuCount > 0 with no grids.ids returns serverless_gpu_unavailable. Move an older serverless GPU app to a grid, or remove its GPU requirement, before saving changes.

Placement and scale

Hardware and location filters combine to restrict eligible machines. More instance capacity requires enough matching resources. Check placement errors and grid capacity when an app has a running target state but no running container.

Grid policies can also cap GPUs, apps and running containers per person, counted against the app’s creator, reclaim idle capacity or queue work fairly under contention. See Grids and shared capacity.

Marketplace capacity

The API and MCP catalog can browse spot capacity by hardware and location. Renting marketplace capacity is not exposed by the public operations documented here. Contributing hardware follows the separate provider guide.

Last updated

Was this helpful?