Create an Application
Define the investigation boundary: the business Application, its services and the context the LLM needs to investigate correctly.
Create and manage investigation tools and Application assignments.
Run the real Tool executor without an Investigation or LLM call. Review the outputs yourself.
Choose multiple existing Application Tools. Ordinary operations use a single Tool.
A global topology workspace is coming soon. Application topologies remain available in Applications.
Define investigation scope, observability tools and dependencies.
From an empty workspace to automatic, cross-Application incident investigation.
Define the investigation boundary: the business Application, its services and the context the LLM needs to investigate correctly.
Connect Kubernetes, Elastic/OpenSearch, Prometheus, LLM providers and the other systems that hold investigation evidence.
Create a Tool once in Tools, assign it to one Application, then configure any Application-specific discovery before enabling it for investigations.
Create Application-owned Channels and Rules so the right team receives the investigation conclusion, evidence and recommended actions.
If you want automatic investigations, create an Inbound API Account and Trigger Source for the Application.
Declare downstream Application relationships. The platform can then hand the investigation to the correct Application when evidence crosses a boundary.
Set Sensitive Data policies so logs and evidence are sanitized before they are sent to the LLM.
Start manually first, review the timeline and manual verification steps, then enable automatic flows when the scope behaves as expected.
Track token use, cost and investigation runtime, and export reports when you need to share Investigation results.
Reusable provider connections with encrypted credentials.
Review automatic Investigations and start manual investigations when your role allows it.
Track model token consumption, estimated spend and investigation runtime over time.
Prompt/context tokens consumed by each model.
Visible generated output; reasoning/thinking is shown separately when the provider exposes it.
Provider-reported tokens that are not included in the visible input/output counters, such as Gemini thinking tokens.
Total usage reported by the model provider, including any provider-specific extra tokens.
Historical cost from immutable per-investigation pricing snapshots.
Average end-to-end duration for completed or failed investigations by model.
General preferences, security and investigation behavior for UTU Engine.
Prices are stored per 1,000,000 tokens. Thinking/reasoning is billed at the output rate. Every LLM step snapshots the active price, so changing prices does not rewrite historical Investigation costs.
All discovered models and their token prices. Changes affect new investigations.
Configure token prices per 1,000,000 tokens.
Manage platform users, roles and application access.