Comparison Recon and ASM

Crossfyre vs Trickest

Two takes on workflow-driven offensive recon, at very different price points.

Trickest is a commercial visual workflow platform for offensive security. Its public plans are a free Community tier (restricted to non-commercial use) and a custom-quoted Enterprise tier, with nothing self-serve in between. If you do paid work but aren't an enterprise buyer, you fall in the gap. Crossfyre is built for exactly that gap.

Feature by feature

Feature TrickestCrossfyre
Free tierCommunity, non-commercial onlyFree plan, commercial use allowed
Self-serve paid plan no yes
PricingQuote only, through salesFrom $29/mo, published
Workflow automationVisual builder.cfx playbooks
Who it is sold toEnterprise buyers on contractsAnyone doing paid offensive work

Every claim about the other tool is taken from its own documentation and pricing as of mid-2026. Re-check before quoting a number.

Standards

What it covers, and what it will not claim.

Pick a list. Every row that says yes names the class that does the work, and every row that says no says why, because a coverage matrix with no gaps in it is a brochure.

8 covered 1 partly 1 not claimed The list this engine was built against. Eight fully, one partly, and one that nothing on the outside can honestly report.

MITRE ATT&CK is deliberately not here. It describes what an adversary does across a whole intrusion, and almost all of a web scanner collapses into one technique in it. A six-row ATT&CK matrix would look impressive and tell you nothing, which is the opposite of what this section is for.

The honest take

Choose Trickest if you are an enterprise buyer ready for a contract. Choose Crossfyre if you do paid offensive work and want a real, commercial-use tool you can put on a card today.

Questions people ask

Can I start without talking to sales?

Yes. Crossfyre has a free plan and self-serve Pro and Reaper plans you can start on a card today. No contract or sales call required.

Does Crossfyre do workflow-style automation?

Yes. Workflows chain the engines into repeatable, schedulable runs, and .cfx playbooks (an early, expanding capability) let you compose custom pipelines.