Be the case study instead of reading one.

Three to five founding deployments, using their own data, hardware and analysts. You shape the roadmap; your objections become the product. No fabricated testimonials — you'd be the first real ones.

3–5 slots ≈50% of Core, locked 12 months Founder-direct

§ 01THE COHORT

A small room, on purpose.

Deliberately tiny so each partner gets founder attention. 4 general slots open · 1 MSSP slot reserved.

Slot 01 · GeneralOPEN
Slot 02 · GeneralOPEN
Slot 03 · GeneralOPEN
Slot 04 · GeneralOPEN
Slot 05 · MSSPRESERVEDwaitlist until multi-tenant hardening is real

§ 02THE DEAL, BOTH WAYS

What you get. What you give.

↙ What you get
  • ≈50% of Core pricing, locked 12 monthsThe founding-partner rate, held for a full year.
  • Founder-direct supportThe person answering is the person who built it.
  • Roadmap inputReal influence on what ships next — your gaps get prioritized.
  • The whole platformUnlimited analysts, no usage meters, English and Arabic.
  • Structured onboardingDeployment assistance sized to your environment.
↗ What you give
  • Honest deployment feedbackOn what works and — more usefully — what doesn't.
  • A quantified case studyReal numbers from a real deployment, built together.
  • Contractual reference rightsPublication always requires your written permission. Nothing goes public without a yes.
  • A real production deploymentYour own data, hardware and analysts — not a sandbox.

§ 03WHO WE'RE LOOKING FOR

A tight fit beats a big logo.

3–20

Small security team

Three to twenty people carrying a jurisdiction far bigger than the headcount.

§

Regulated sector

Government, defense, finance, healthcare, telecom or critical infrastructure — where sovereignty is a mandate.

Moving off open-source

Teams outgrowing MISP or OpenCTI and ready for relevance, exposure management and detection in one place.

§ 04APPLY

Take a slot before it's a story.

A few honest questions. The builder reads every one personally and replies within a day.

DESIGN CONCEPT — this form logs locally and sends nothing. In the live product it reaches the builder's inbox directly.

Application logged locally.

In the live product, the builder reads this within a day and replies personally. Nothing left your machine.

REQUEST 14-DAY POC // NO CARD
DESIGN CONCEPT — NOTHING IS ACTUALLY SENT

Request logged locally.

Fitting, no? In the real product this is where the builder emails you back within a day. This is a design concept — nothing left your machine.

ESC

THE TRACE · LOCAL INFERENCE · REASONING SHOWN STEP-BY-STEP

Try: “which of our vendors were hit by qilin” · “fortios exposure” · “what changed on our perimeter this week”