Skip to main content
Basaltic is a cloud platform. You create virtual machines, give them networks and storage, put a load balancer in front of them, and point a domain at the result. Around that sit the services those workloads need: object storage, DNS and certificates, secrets and encryption keys, and telemetry. Everything here is reachable three ways — the console, the CLI, and the HTTP API. They are the same API underneath; the console and the CLI are clients of it.

Quickstart

Create an account, get a set of credentials, and make your first authenticated call.

Authentication

How requests are signed, and how to get the access key that signs them.

Regions and endpoints

Which host to call. Some services are global, most are regional.

API reference

Every operation across the public APIs, generated from the specs the services are built against.

​
What runs where

A Basaltic account is global: one identity, one bill, one audit trail. The resources you create live in a region, and most APIs are addressed per-region. A few — identity, billing, quota, audit and DNS — are global and have a single endpoint. Today the platform serves one region, sa-saopaulo-1, in São Paulo, Brazil. Regions and endpoints has the full breakdown of which service is which.
These docs are being written alongside the platform. Product guides for individual services are still going up; the API reference is complete and generated from the specs the services are verified against.