Platform

Keys that are born to be rotated.

Create labeled API keys for Cloud SDK and embed integrations, see the secret exactly once, and revoke without a deploy. Programmatic access with grown-up hygiene.

Explore highlights

Sound familiar?

Keys in plaintext stores

A key that lives forever in a wiki page is a breach with a date on it. Secrets show once at creation, then only a hash remains.

The key nobody dares delete

Unknown keys linger because revocation might break something. Labeled keys with clean revoke dialogs make rotation routine.

Rebuild-the-wheel integrations

Your key unlocks the Cloud SDK and embeds, session creation, mounted maps, webhooks, instead of a raw API and a shrug.

Programmatic access, hygienic by default

01Labeled at creationEvery key names what it's for. Six months later you'll know what breaks if it's revoked.
02Shown onceThe plaintext secret appears exactly once. After that, the platform stores only its hash.
03Clean revocationA deliberate revoke dialog, no deploy, no downtime, effect on the next request.
04Built for the Cloud SDKKeys power constrained selection sessions and embeds, the documented integration path, not a backdoor.
05Workspace-scopedA key can only touch its own workspace's data, the same boundary as everything else.
06Audited usageCreation and revocation are admin actions. They land in the audit trail like everything sensitive.

Key hygiene in three steps

  1. 01Create & labelName the integration, create the key, copy the secret, once.
  2. 02Mount the SDKCreate a session, embed the map, subscribe to webhooks.
  3. 03Rotate on scheduleCreate the replacement, deploy it, revoke the old one, boring, as it should be.

Mint your first key

Create an API key in the demo workspace.