Environments and keys

List, create, edit, rotate and delete Environments (formerly trace projects) and their keys, and what each action does to traces, online rules, alerts and running deployments.

After this page you can keep one key per deployment, rotate a leaked key without losing history, retire an Environment knowing what stops working, and read how much each Environment sends.

The Environments tab

One card per active Environment: name and label (development · staging · production), the key masked to its last four characters, Copy, Rotate, Delete, Install guide, the last trace time and traces in the last 24 hours, spans this month against the plan’s monthly allowance (no bar when the plan sets no cap), and a limit indicator (“2 of unlimited”, or “1 of 1” on a plan with one Environment, where New environment is locked). Usage figures come from the trace store on every load; when a read fails the card says unknown, not zero.

Create and edit

New environment takes a name, the label and a description and returns the key once in full — copy it then; afterwards only the last four characters are shown. Name, description, label and active state can be edited later; the tenant id and key do not change with an edit. Creating, rotating and deleting are allowed to the Environment’s creator and to organization Owners and Admins. The Install guide opens the quickstart with this key filled in — Install the SDK.

Rotate a key

Rotate issues a new tk_live_… key and keeps everything else: the tenant id is derived once at creation and never recomputed, so historic traces, the online rule and the alerts stay attached. The confirm states the consequence: the old key stops being accepted within about ten minutes — the receiver caches key lookups for that long — and there is no overlap window, so deployments still sending with it get 401. Deploy the new key first, then rotate. The install guide re-renders with the new key and waits for a trace signed with it; the card’s masked key updates. Which key sent a given trace is not recorded, and there is no organization-level audit trail of who rotated.

Delete

Delete is a soft delete: the key stops working immediately and the Environment leaves the switcher and every list; its traces stay readable until retention. The confirm lists the dependents — the online rule, alerts, auto-add rules and simulation runs that reference this Environment — because they lose their target; the delete is not blocked by them. Datasets and runs are project-scoped and are never affected by deleting an Environment. There is no restore for a deleted Environment.