Question 1

What is TicketMan AI?

Accepted Answer

TicketMan AI is a self-hosted software support engine. A drop-in SDK sends errors, crashes and their diagnostic context into the system, where AI groups them and connects each incident to its history, your knowledge and the customer it happened to. From there your support team, an engineer, or an agentic dev server can resolve it, all on your own infrastructure.

Question 2

How does the self-healing support loop work?

Accepted Answer

The Diagnostics SDK captures an error and forwards it to TicketMan AI, which groups and pre-categorizes it into a ticket. On the optional Dev Server plan the ticket is handed to an agentic coding model such as Claude Code or Codex, which proposes a fix and opens a pull request. A human engineer reviews it, or it auto-approves, and your CI/CD ships the update. The loop closes.

Question 3

Is TicketMan AI self-hosted?

Accepted Answer

Yes. TicketMan AI is fully self-hostable and runs on your own servers or private cloud. Your database, your tenant, your keys. Point the AI at a local Ollama model and no ticket content ever leaves your network.

Question 4

Can the AI run offline?

Accepted Answer

Yes. You can bring your own model provider (OpenAI, Azure, Anthropic, Grok) or run a fully local model with Ollama, so the AI can work entirely inside your own walls.

Question 5

How much does TicketMan AI cost?

Accepted Answer

Individuals and open-source contributors are free forever. Companies under 200 employees whose supported apps have fewer than 50,000 users pay one flat 149 dollars per month. Larger and regulated organizations get a custom enterprise quote.

Question 6

What is the Diagnostics SDK?

Accepted Answer

TicketMan Diagnostics is a drop-in package for .NET, Node.js and Python applications. Install it, set two environment variables, and unhandled crashes and errors are reported to your TicketMan AI suite for grouping and AI root-cause analysis. Without a configured endpoint it is completely inert, with zero overhead.

Variable	Default	Description
`TICKETMAN_DIAG_ENDPOINT`	unset (SDK inert)	Full HTTPS URL of the TicketMan ingest endpoint.
`TICKETMAN_DIAG_API_KEY`	empty	API key, sent as `X-TicketMan-Key`.
`TICKETMAN_DIAG_ENVIRONMENT`	`DOTNET_ENVIRONMENT` or `ASPNETCORE_ENVIRONMENT`, else `Production`	Environment name reported with the incident.
`TICKETMAN_DIAG_APP_NAME`	entry assembly name	Application name.
`TICKETMAN_DIAG_APP_VERSION`	assembly informational version	Application version.
`TICKETMAN_DIAG_BUILD_ID`	empty	CI build identifier.
`TICKETMAN_DIAG_GIT_COMMIT`	commit suffix of the version	Git commit hash.
`TICKETMAN_DIAG_TIMEOUT_SECONDS`	`10`	HTTP timeout per send attempt.
`TICKETMAN_DIAG_DEBUG`	`false`	Self-log internal decisions and errors to stderr and `Trace`.

Variable	Default	Description
`TICKETMAN_DIAG_CAPTURE_USER`	`false`	Opt-in: include user id, username, tenant and roles from claims.
`TICKETMAN_DIAG_CAPTURE_REQUEST_BODY`	`false`	Opt-in: include the masked, size-capped HTTP request body.
`TICKETMAN_DIAG_MAX_REQUEST_BODY_BYTES`	`16384`	Request body cap; longer bodies are truncated and flagged.
`TICKETMAN_DIAG_HTTP_STATUS_RANGES`	`500-599`	Status codes or ranges that trigger a report with no exception, e.g. `500-599,429`.
`TICKETMAN_DIAG_ENABLE_DUMPS`	`false`	Capture a minidump (stacks and modules, no full heap) on fatal crashes. .NET only.
`TICKETMAN_DIAG_MAX_ATTACHMENT_SIZE_MB`	`10`	Attachments larger than this are dropped.
`TICKETMAN_DIAG_BREADCRUMB_BUFFER_SIZE`	`100`	Ring-buffer size for log breadcrumbs. `0` disables breadcrumbs.
`TICKETMAN_DIAG_CAPTURE_LOG_LEVEL`	`Critical` (.NET) / `fatal` (Node)	Minimum log level at which a logged exception is captured as an `error` report; `None`/`none` disables. Set it to `Error`/`error` to capture exceptions your code catches and logs, with no code changes.

Variable	Default	Description
`TICKETMAN_DIAG_SPOOL_DIR`	`<temp>/ticketman-diagnostics/<app-name>`	Local spool directory for pending reports. Must be writable.
`TICKETMAN_DIAG_SPOOL_MAX_MB`	`50`	Spool size cap; oldest reports are evicted first.
`TICKETMAN_DIAG_RATE_LIMIT`	`10/5m`	Per-fingerprint client-side limit, `N/window` with `s`, `m` or `h`.

Variable	Default	Description
`TICKETMAN_DIAG_MASK_EXTRA_KEYS`	empty	Extra key names the masker treats as secrets.
`TICKETMAN_DIAG_USER_CLAIM_ID`	`sub`, `oid`, `nameidentifier`	Claim type for the user id.
`TICKETMAN_DIAG_USER_CLAIM_NAME`	`preferred_username`, `name`	Claim type for the username.
`TICKETMAN_DIAG_USER_CLAIM_TENANT`	`tid`	Claim type for the tenant.
`TICKETMAN_DIAG_USER_CLAIM_ROLES`	`roles`, `role`	Claim type for roles.

Configuration reference

Configuration reference

Core

Capture options

Delivery and limits

Masking and claims

Per-SDK differences

Activation rules