Skip to content
Aureon

Developers

Build on a governed, evidence-first platform

A clear path from architecture to a working sandbox — with least-privilege credentials and honest production gates.

Architecture mapOpen the console

Quick start

Four steps to building

  1. 1

    Learn the architecture

    Start with the platform map and the layer-by-layer overview to understand identity, tokenization, and the chain.

    Open the architecture map →
  2. 2

    Review the API & auth model

    Aureon uses governed, role-scoped APIs with JWT authentication. Operators sign in through the console; the API verifies and authorizes every request.

    Open the console →
  3. 3

    Build against a sandbox

    Model projects, tokens, and RWA workflows in a governed sandbox. State is simulation-labelled — nothing is deployed on-chain.

    Open the wallet studio →
  4. 4

    Promote after the gates pass

    Production deployment is gated on custody, external audit, and approval. There is no production mainnet today; promotion is an explicit, evidence-backed step.

    See current status →

Credentials

Least-privilege by default

API credentials are issued through a governed workflow and scoped to the minimum a project needs. Examples in our documentation always use obvious placeholders — never a real secret.

Example (placeholders only)

curl https://api.aureon.example/v1/projects \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Project-Id: YOUR_PROJECT_ID"

Never commit a real key. Rotate credentials through the console.