Running Temper

For someone standing up a deployment and keeping it healthy — your own instance, your own
identity provider, your own data.

What the architecture fixes versus what your deployment chooses is set out at
temperkb.io/operating. These pages are the runbooks.

Standing it up

Self-hosting Temper — the operator runbook: the Vercel
project, the database, the environment.

Bootstrapping an org — turning a fresh deployment into one
with people in it.

For a larger installation, Enterprise install — ground up
covers the same ground with the decisions an enterprise has to make called out.

Pick the one that matches your IdP:

Okta

A SAML IdP — the generic SAML path.

The trust boundary these configure — how a credential becomes a session, and where that is
enforced — is described in Temper auth & security.

@temper on Slack — end-to-end setup.

What the Slack integration actually does — identity,
credentials, and what is retained.

Provisioning a GitHub connection

A read-only GitHub credential via your own App

Cloud agents — the model for agents that run without a human
in the loop.

Deploying an Eve agent to Vercel

Delivering L0 kernel cogmap content

OpenTelemetry setup — getting traces and metrics out.

Drain operator queries — the TraceQL queries worth
having to hand when something looks wrong.