Regions

A region is the physical location your project's storage and compute run in. You pick it once, when you create the project; every branch and endpoint under that project inherits it. Region is a property of the project, not something you change later.

The region catalog

GET /v1/regions returns the regions you can create projects in. It is authenticated — the same bearer that lists your projects lists the catalog. The response is a single object:

{
  "regions": [
    {
      "region_id": "home-proxmox",
      "name": "Kisenon Home (Proxmox)",
      "default": true,
      "geo_lat": 0,
      "geo_long": 0
    }
  ]
}

Each region carries:

• region_id — the stable identifier you pass when creating a project.
• name — the human label shown in the console dropdown.
• default — whether this is the region used when you don't specify one.
• geo_lat / geo_long — coordinates for distance-based selection. They are 0 for the home cluster, which is bare metal rather than a public-cloud region.

Choosing a region at create time

In the web console, New project has a Region dropdown. It defaults to Auto (nearest), which leaves the choice to the control plane — today that always resolves to the single home region. To pin a specific region, select it from the list.

Over the API, pass the optional region field on POST /v1/projects:

{ "name": "my-app", "region": "home-proxmox" }

Omit region (or send null) for the same "auto" behaviour as the console default: the control plane assigns the default region.

The alpha runs a single region

During alpha, Kisenon runs one region: home-proxmox ("Kisenon Home (Proxmox)"), a US bare-metal cluster. It is the default, so every project lands there whether or not you set region. Multi-region is roadmap; the catalog and the region field are already in place so nothing changes on the client when more regions come online.

Related

• Projects — the container a region is chosen for.
• Branches — inherit their project's region.