Launch checklist
Day-0 smoke test
Before inviting users, run the same narrow flow you expect them to use.1
Deploy or confirm the release
Deploy the agent, or confirm the intended release is active in the dashboard
or with
karta agent show.2
Send one production turn
Use
karta send "..." --json or your backend integration to send a safe,
representative turn. Confirm the response and session_id.3
Exercise the browser path
Open the hosted widget, verified widget, custom UI, or adapter client you
will actually ship. Confirm the browser never receives a
kt_live_... key.4
Check usage and limits
Confirm the turn appears in usage reporting, then verify the relevant hard
caps and threshold webhooks are configured.
5
Test rollback
Know which previous release you would roll back to and who is allowed to do
it. For launch-critical agents, perform a rollback rehearsal before go-live.
Operational runbook
Write down the answers before launch:- Who owns deploys, rollback, API keys, BYOK, budgets, webhook endpoints, and audit review?
- Where do operators check live platform status?
- Which customer-facing failures should show retry, limit-reached, or support messaging?
- Which logs or session transcripts can support access, and under what policy?
- Which webhook events wake your team or update your internal systems?
- What is the first action when a release fails, a model key is rejected, a budget is exhausted, or a webhook endpoint auto-disables?
Status and support
- Live platform status: status.karta.sh.
- Security and trust materials: karta.sh/trust.
- Product or account help:
[email protected]. - Vulnerability reports: follow the public security policy linked from the trust page.