Support
How to reach us, what to include so we can help quickly, and what response to expect on each tier. During early access, support email goes to the engineers who build the product.
Channels
| Topic | Channel |
|---|---|
| Technical support, product questions, bug reports | sales@temper.codes with a subject starting Support: |
| Billing, invoices, license delivery, refunds | sales@temper.codes — most billing tasks are also self-serve at temper.codes/manage |
| Security vulnerabilities | security@temper.codes — see the disclosure policy; please do not use the general address for vulnerabilities |
| Enterprise, air-gap, procurement | sales@temper.codes |
Response expectations
| Tier | Target | Notes |
|---|---|---|
| Community | Best effort | We read everything; production-impacting reports are prioritized regardless of tier. |
| Pro | 1 business day first response | Include your organization name (as it appears in your license file) so we can match your subscription. |
| Enterprise | Contractual SLA | Named engineers and response times per your agreement, including an out-of-band escalation path. |
What to include in a technical report
The product is self-hosted and sends us nothing, so everything we know about your cluster is what you attach. The fastest reports include:
- Versions — chart version, agent image tag, and Kubernetes version
(
helm list -n temper,kubectl version). - Platform — cloud and node OS/kernel (for example GKE COS-129, EKS AL2023), per the platform matrix.
- Agent state — the node’s
temper.codes/agent-statusannotation and agent logs from the affected node (kubectl -n temper logs ds/temper-agent --tail=200, or the pod log view in the dashboard). - What you expected vs. what happened — with timestamps, so we can line them up against the logs.
- If scheduling behavior is the issue: the generated layer config
(
temper-cli show-config, or the scx config tab in the dashboard) and, if available, a/observesnapshot from the affected node.
If a node is misbehaving right now, put it in safe mode first — that returns it to the stock scheduler immediately — and debug from the logs afterwards. You do not need our permission or our availability to roll back.
Feature requests and roadmap
Send them to the same address. During early access, design partners get direct input on platform targets and the kernel support matrix — if a missing platform or capability is blocking your adoption, say so; that information moves priorities.