Redline · Pitch Deck
Cybersecurity
Redlineاختبار الاختراق
Continuous, threat-led penetration testing aligned to SAMA’s FEER programme.
neuriya.ai — Sovereign, Arabic-first enterprise AI
Problem
Penetration testing produces a PDF, then goes silent until next year
- Web, API, mobile, and network engagements are typically scoped and reported by different vendors, so findings live in scattered PDFs no one cross-references.
- Findings arrive without reproducible proof of concept, so remediation teams spend days just reproducing an issue before they can fix it.
- Critical and high findings have no enforced fix deadline, so severity drifts unnoticed between one engagement and the next.
- SAMA's FEER programme expects ethical red-team engagements reported on a defined cadence, but most firms still hand back a one-off report with no running register behind it.
Solution
A running findings register replaces the once-a-year pen-test report
Product
Redline in action
How it works
From first touch to outcome
Scope an engagement
Web, API, mobile, or network — scope and rules of engagement are logged up front.
Test
Testers log findings with proof of concept as they go, not in a report weeks later.
Remediate
Findings route to owning teams with a severity-based SLA clock.
Re-test and close
A fix triggers an automatic re-test before the finding is marked closed.
Market
Sizing the opportunity
- TAM — $1.1B. GCC penetration-testing & offensive-security services market
- SAM — $150M. Saudi continuous pen-testing & red-team platform market
- SOM — $9M. 3-year obtainable share via SAMA-regulated financial entities and NCA-regulated enterprises
SAMA's Financial Entities Ethical Red-teaming (FEER) programme and NCA's ECC-2 controls both require regular, evidenced offensive testing, and Vision 2030's financial-sector growth is expanding the number of licensed entities that must comply — turning point-in-time pen-testing into a recurring operational requirement rather than an annual checkbox.
Business model
How Redline makes money
Per-engagement subscription
Priced by the number of concurrent web, API, mobile, and network engagements tracked in the platform.
Findings-register seat license
Recurring per-seat pricing for security and remediation teams working findings in the register.
Engagement onboarding fee
One-time fee to scope the first engagement and configure FEER-aligned reporting.
Revenue streams
Where the revenue actually comes from
Competition
Where we win
Our edge
- Only findings-register platform purpose-built for SAMA's FEER reporting cadence, not a generic vulnerability tracker.
- Proof of concept is attached to every finding by default, cutting remediation time instead of adding a reporting step.
- Sovereign hosting for findings and exploit details — some of an organization's most sensitive data — as a default, not an add-on.
- Founding team combines Saudi enterprise delivery experience with hands-on offensive-security engineering.
Traction
Early validation, built for pilot readiness
- Full testing platform experience designed and built end-to-end: engagement scoping, findings register, remediation SLAs, and re-test workflow.
- Architecture pre-aligned to SAMA FEER, NCA ECC-2, and PDPL.
- Actively selecting design-partner security teams for a first pilot cohort.
Go-to-market
Land with one engagement type, expand to continuous coverage
- 1Land with 2-3 design-partner security teams, starting with their next scheduled web or API engagement.
- 2Prove time-to-fix and re-test turnaround gains over a pilot engagement cycle.
- 3Expand through SAMA FEER-regulated financial entities and NCA ECC-2-regulated enterprise networks.
Team
Built by operators, not just builders
The ask
Raising a seed round to reach first design-partner security teams
We're raising to fund FEER-aligned reporting tooling, integrations with common scanning and ticketing tools, and the core team through first-revenue pilot deployments.