TFTHREATFADE
ProductDetectionHow it worksIntegrationsResearchSecurityDocsPlaygroundPricingEnterprise
GitHub
ProductDetectionHow it worksIntegrationsResearchSecurityDocsPlaygroundPricingEnterprise
HomePaid pilot · $7,500–$15,000

Prove the detection capability in your environment before scaling it.

A bounded 30–60 day technical pilot designed around your data, detection question and acceptance criteria—not an open-ended trial.

Pilot structure
Scope
One agreed environment or bounded deployment topology.
Duration
Typically 30–60 days.
Investment
$7,500–$15,000 based on scope and engineering requirements.
Commercial bridge
Where agreed, the pilot fee is credited toward the first annual Enterprise contract.
Success criteria

Representative telemetry and agreed detection scenarios are in scope.

Detection packs are deployed and their evidence output is reviewed.

False-positive behavior is characterized rather than hidden.

Evidence quality and analyst workflow are evaluated by the customer team.

Required integration and deployment boundaries are validated.

A written enterprise decision is made at the end of the pilot.

01

Define

Set objectives, data sources, baseline controls and the decision date.

02

Deploy

Deploy the agreed ThreatFade boundary and validate operational prerequisites.

03

Measure

Review detections, evidence, analyst workflow, latency and false-positive behavior.

04

Decide

Produce a quantified outcome and choose Enterprise, iterate, or stop.

Conversion path

Assessment → Pilot → Enterprise

The pilot is intentionally not a free proof-of-concept. It reserves engineering capacity, creates a shared acceptance framework and gives both sides an evidence-backed decision point.

Discuss a pilotEnterprise path

Technical intake

Start the pilot conversation

Minimal qualification only. Security telemetry, credentials and sensitive incident details are not requested here.

Use email instead
THREATFADE / TINLANCE LIMITEDSource on GitHub