Product Guides

How to use this section

Product Guides are the user manual for the Kadryn dashboard. They explain each menu in the sidebar, the workflows it owns, the teams that should use it, and the handoffs between menus.

The goal is to make Kadryn predictable in production. A user should know where to investigate a signal, where to configure a control, where to connect systems, and where to manage subscription or workspace administration.

Dashboard menu map

• Overview gives a plan-aware readiness view of the workspace. Use it to see what is configured, what is missing, and what the current plan is designed to support.
• Command Center aggregates high-priority signals across Costs, Alerts, Guardrails, Optimizations, Billing, Integrations, Organization, Security, and Developers.
• Costs & Usage explains spend, usage, forecasts, allocation, data health, reports, dashboards, and unit economics.
• Alerts turns detections into cases, incidents, routing, noise control, runbooks, and operational analytics.
• Optimizations turns cost and usage opportunities into simulations, actions, measured savings, and executive summaries.
• Limits & Budgets owns budgets, caps, policies, budget owners, approvals, approval chains, exceptions, and audit.
• Security owns identity, access security, audit posture, compliance controls, SSO, SCIM, IP allowlists, MFA, and audit integrity.
• Provider Keys stores and tests provider credentials used by Kadryn-controlled workflows.
• Integrations connects Slack and activation workflows such as executive digests and product webhooks.
• Developer tools helps engineers integrate Kadryn Gateway, direct usage ingestion, webhooks, SDKs, logs, traces, and diagnostics.
• Organization manages members, teams, roles, projects, guests, and multi-workspace context.
• Billing manages Kadryn subscription plans, usage visibility, invoices, payment methods, and limits.
• Settings contains workspace-level configuration that does not belong to a specific operational workflow.
• Support is for help requests, incidents with Kadryn support, and product assistance.
• Help & Docs is this documentation area.

Recommended operating model

Start broad, then move to the owning menu.

1. Use Overview or Command Center to understand the current state.
2. Use Costs & Usage to investigate data, cost, forecast, allocation, and report questions.
3. Use Alerts to operate live signals and incidents.
4. Use Limits & Budgets to configure enforcement and governance.
5. Use Optimizations to turn findings into measured savings.
6. Use Developer tools when the root cause is ingestion, gateway, metadata, traces, or API behavior.
7. Use Integrations, Provider Keys, Security, Organization, Billing, and Settings for administration.

User roles

• Finance should focus on Overview, Costs, Optimizations, Billing, Reports, Allocation, Unit Economics, and Guardrails.
• Platform should focus on Command Center, Developers, Provider Keys, Integrations, Costs, Alerts, Guardrails, and Security.
• Security should focus on Security, Guardrails Audit, Organization Roles, Provider Keys, webhooks, and audit trails.
• Support and operations should focus on Alerts, incidents, routing, runbooks, Slack, and Support.
• Admins and owners should understand every administrative surface because plan limits and permissions shape what the rest of the team can do.

What good usage looks like

A mature workspace has usage flowing, metadata attached, provider keys tested, Slack healthy, alerts routed, reports scheduled, budget owners assigned, policies reviewed, and audit trails available for sensitive changes.

Kadryn should not force every team into the same setup. It should show the correct readiness for the plan you bought, then guide your team toward the next useful workflow.