ClickStack Demo Day (2026-09-04) - Multiple ingestion keys

Ingestion used to run through a single default key. The API keys page now lets you create several ingestion keys, up to a cap of around 20, so you can scope access per team, per service or per environment rather than sharing one key everywhere. Each key can also be frozen or revoked. Freezing takes effect without deleting the key, which is what you want when you suspect a key is being misused but don't want to break the sender permanently. Neither action needs a collector restart. When you change a key, ClickStack pushes the new OTel collector configuration out to the collector, which picks it up within about a minute. In the demo a frozen key on staging starts having its ingest rejected while the call is still running, and then works again once it's unfrozen. Part of the ClickStack Demo Day series. See the full post at https://clickhouse.com/docs/use-cases/observability/clickstack/demo-days/2026/2026-09-04