Infrastructure API

Query available infrastructure options including server sizes, regions, and app instance configurations.

Endpoints for querying the catalogue of infrastructure options (sizes, regions, and one-click images) available to your project's create flows. Every catalogue response is cached for a few minutes and is identical for all customers.

Auth: Required for every endpoint on this page.

Server Sizes

GET /v1/catalog/servers/sizes

Returns available server sizes with pricing.

Server Regions

GET /v1/catalog/servers/regions

Returns available server regions.

One-Click Apps

GET /v1/catalog/servers/1-clicks

Returns available one-click applications for server provisioning.

App Instance Sizes

GET /v1/catalog/apps/sizes

Returns available app instance sizes with pricing.

App Regions

GET /v1/catalog/apps/regions

Returns available regions for app deployment.

List Plans

GET /v1/redis/plans

Returns every purchasable plan tier. priceMonthly is in whole currency units.

engine tells you what a tier runs. Valkey is the BSD-licensed fork of Redis 7.2 and is compatible with it at the protocol and command level, so existing clients and connection strings work against it unchanged.

Two performance fields exist and neither converts into the other. Read whichever is present rather than assuming a field:

cpuMilli is CPU reserved for the instance, in millicores. This is what currently sold tiers publish.
throughputOps is a rated operations-per-second ceiling, and is null on every tier sold today — nothing in the path throttles, so there is no ceiling to quote.

Response:

{
  "success": true,
  "data": [
    {
      "slug": "valkey-1gb",
      "name": "Valkey — 1 GB",
      "provider": "COSMONER",
      "engine": "VALKEY",
      "planType": "RAM",
      "memoryMb": 1024,
      "throughputOps": null,
      "cpuMilli": 250,
      "supportsReplication": false,
      "supportsPersistence": true,
      "priceMonthly": 9
    }
  ]
}

List Regions

GET /v1/redis/regions

Returns the regions a database can be deployed to. One region is sold today, but the list is not a formality — do not hard-code past it. Each entry carries:

providers — which backends sell into this region.
planTypes — which plan families are fully purchasable there.

Filter on both before offering a region against a chosen plan; creating a database in a region its plan is not sold in is rejected rather than quietly relocated.