Qalaa · Pitch Deck
Cybersecurity
Qalaaقلعة
Zero-trust, CCC-aligned landing zones with key management built in.
neuriya.ai — Sovereign, Arabic-first enterprise AI
Problem
Cloud landing zones get built first, secured second
- Landing zones are typically provisioned first and mapped to NCA's Cloud Cybersecurity Controls (CCC) later, if at all, leaving a gap auditors find before the security team does.
- Encryption keys are tracked in spreadsheets or not tracked at all, so rotation schedules lapse without anyone noticing until an audit flags it.
- Workload-to-workload traffic inside a VPC is trusted by default, so a single compromised workload can move laterally with no continuous verification.
- Security teams running multiple landing zones and regions have no single view of posture, only a set of per-account dashboards that have to be checked one at a time.
Solution
Zero-trust, CCC-aligned landing zones from the first deployment
Product
Qalaa in action
How it works
From first touch to outcome
Provision a landing zone
New landing zones inherit CCC-aligned guardrails from the first deployment.
Register workloads
Every workload is inventoried with its encryption and exposure posture.
Enforce zero trust
Workload-to-workload traffic is verified against policy continuously.
Rotate and review
Key rotations and posture reviews are scheduled, tracked, and never silently skipped.
Market
Sizing the opportunity
- TAM — $1.9B. GCC cloud security posture & zero-trust management market
- SAM — $220M. Saudi sovereign-cloud landing-zone and workload-protection market
- SOM — $15M. 3-year obtainable share via regulated enterprises migrating to sovereign cloud
Vision 2030's push to migrate government and regulated-sector workloads into sovereign and hyperscaler-in-Kingdom cloud regions, combined with NCA's Cloud Cybersecurity Controls and NDMO data-classification requirements, is turning CCC-aligned landing-zone design from a specialist consulting engagement into a recurring platform need.
Business model
How Qalaa makes money
Per-landing-zone subscription
Priced by the number of landing zones under active management and their workload count.
Key-management add-on
Recurring add-on for centralized encryption-key tracking and rotation across landing zones.
Landing-zone provisioning fee
One-time fee to design and provision the first CCC-aligned landing zone.
Revenue streams
Where the revenue actually comes from
Competition
Where we win
Our edge
- CCC alignment is built into landing-zone provisioning itself, not a checklist run after the fact.
- Reference architectures designed for in-Kingdom hosting from the start, not a global cloud template retrofitted for sovereignty.
- A single risk-scored view across every landing zone and region, where competitors require per-account dashboards.
- Founding team combines Saudi enterprise delivery experience with hands-on cloud-security engineering.
Traction
Early validation, built for pilot readiness
- Full cloud-security platform experience designed and built end-to-end: landing-zone provisioning, key management, zero-trust enforcement, and workload risk scoring.
- Architecture pre-aligned to NCA CCC, PDPL, ISO 27001, and NDMO Classification.
- Actively selecting design-partner cloud teams for a first pilot cohort.
Go-to-market
Land on one landing zone, expand across regions
- 1Land with 2-3 design-partner cloud teams, starting with one landing zone and its existing workloads.
- 2Prove CCC-alignment and drift-detection gains over a pilot quarter, then expand to additional landing zones.
- 3Expand through systems-integrator and hyperscaler-in-Kingdom partnership channels.
Team
Built by operators, not just builders
The ask
Raising a seed round to reach first design-partner cloud teams
We're raising to fund CCC control-mapping tooling, multi-cloud integrations, and the core team through first-revenue pilot deployments.