Saved entities
Typed results stay aligned across browsing, findings, reports, sources and the relationship map.
Product
Answer public-intelligence questions without losing the source.
Start with a focused question, prepare a compatible investigation plan and keep every saved result connected to its source and relationships.
Target
Confirm the starting clue
Public clueexample.orgReserved example
Detected typeDomainReviewable
AuthorizationRequiredConfirm scope
ActionNonePlanning only
Plan before running
Know what can run, what cannot and what it may cost.
Target type shapes compatibility. Coverage shapes breadth. Planning stays separate from execution.
Target-aware plan
What do you want to investigate?
Enter one authorized public clue. Tigess detects its type and prepares a compatible investigation plan.
example.orgDomain
Prepared plan84 compatible data sources
Credit estimate26–42 credits
Previewing a plan does not contact data sources, start a research run or consume credits.
How planning maps to the engine
A prepared plan persists the engine-authored module selection, dependency closure, safety modes, provider configuration gaps and credit estimate. Execution uses that reviewed plan rather than rebuilding a hidden alternative.
Questions answered
What did we find, how is it connected and why should we trust it?
The result is useful because its meaning, confidence and source remain available after collection.
Confidence and uncertainty
Direct observations, candidates and contradictions remain visibly different instead of becoming invented certainty.
Original sources
Each normalized result can point back to saved source material, provenance and any explicit collection limit.
Reports and exports
Build evidence-backed handoffs without losing the identity of the result, relationship or supporting source.
Relationship map
Move from separate results to explainable connections.
Directly observed context stays close to the starting clue. Candidate, inferred or contradictory context remains visible for review.
Workspace
Review, govern and deliver from one place.
Keep the operational context around the investigation—not just the final rows.
Workspaces and permissions
Keep membership, access, billing context and saved investigations inside explicit account and workspace boundaries.
API keys and automation
Use workspace-owned keys and scoped permissions for bounded, repeatable developer workflows.
Assisted evidence review
Summarize saved sources and propose next steps while keeping execution behind a separate confirmation.
Research-run status
See unavailable data sources, useful negative results, errors, limits and progress without hiding partial coverage.
Assisted review
Use AI without giving it execution control.
Assistance retrieves saved context for the question and distinguishes observed sources from inference.
- Source-grounded summaries and comparisons
- Clear separation of observation and inference
- Proposed paid or active work requires confirmation
- Manual investigation planning remains available
Why does the mail-policy finding need review?
Observed source
A DMARC policy was collected directly, while the candidate mail relationship has only one corroborating source.
Inference
The organization may be transitioning policy, but the available sources do not establish intent.
Start with a target
Turn public signals into explainable evidence.
Create an account to plan your first evidence-backed investigation, or talk to us about team and workflow requirements.