> ## Documentation Index
> Fetch the complete documentation index at: https://docs.basaltic.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> A cloud platform you can run production workloads on — compute, networking, storage, and the services around them.

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: managed databases, object
storage, a container registry, secrets and encryption keys, queues, email, and
telemetry.

Everything here is reachable three ways — the [console](https://console.basaltic.sh),
the [CLI](/cli), and the [HTTP API](/api-reference/introduction). They are the same
API underneath; the console and the CLI are clients of it.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create an account, get a set of credentials, and make your first
    authenticated call.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    How requests are signed, and how the console's browser session differs from
    an access key.
  </Card>

  <Card title="Regions and endpoints" icon="globe" href="/regions">
    Which host to call. Some services are global, most are regional.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/introduction">
    Every operation across the eighteen public APIs, generated from the specs
    the services are built against.
  </Card>
</CardGroup>

## 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](/regions) has the full breakdown of which service is
which.

<Note>
  These docs are being written alongside the platform. Product guides for
  individual services are still going up; the [API reference](/api-reference/introduction)
  is complete and generated from the specs the services are verified against.
</Note>