One division site, one product sub-site, five page families.

Everything CYRKIL Shield needs to sell. AEGIS gets its own host because it is a product with its own buyer, its own documentation and its own release cycle — the same test any other division would have to pass to earn a subdomain.

CYRKIL Shield

cyrguard.fr

The division site. Sells services and outcomes; routes product buyers to AEGIS.

/Division homeThe NIS2 argument, three ways in, the fifteen solutions.phase 1
/services/Service catalogueThe fifteen services, each with what it delivers and how it is priced.phase 1
/services/<slug>/Service detail ×15Scope, SLA numbers, deliverables, what is excluded.phase 1
/solutions/Solutions indexThe fifteen selected projects, with the need and competition evidence.phase 1
/solutions/<slug>/Solution detail ×15The problem, the regulation behind it, what we deliver, who it is for.phase 1
/compliance/<reg>/Regulation pages ×5NIS2 · DORA · CRA · GDPR · AI Act. Deadline, scope, obligations, our role.phase 1
/sectors/<slug>/Sector pages ×6Healthcare, energy, manufacturing/OT, finance, public sector, defence.phase 2
/incident/Under attack24/7 emergency intake. Reachable from the header on every page.phase 1
/resources/Threat intelligenceAdvisories and research — the link-earning surface.phase 2
/about/ · /contact/Team and contactNamed analysts and certifications. A security buyer checks.phase 1

AEGIS

aegis.cyrkil.fr

The product sub-site. A different buyer — technical, evaluating, and reading documentation before talking to anyone.

/Product homeWhat AEGIS is, the four threat classes, the compliance differentiator.phase 1
/how-it-works/ArchitectureThe six layers, explained for a technical evaluator.phase 1
/capabilities/Capability matrixThe fourteen platform services, mapped to what the customer receives.phase 1
/deployment/Deployment optionsEU cloud, on-premise, air-gapped. The sovereignty argument in detail.phase 1
/for-mssp/For MSSPsMulti-tenant console — the primary distribution channel.phase 1
/compliance-reporting/Automated reportingNIS2 24h/72h, GDPR, DORA drafts. The exclusive feature.phase 1
/docs/DocumentationIntegration guides, API reference, detection-as-code repository.phase 2
/trust/Trust centreSub-processors, data residency, platform self-defence, disclosure policy.phase 1
/console/Console (app)The authenticated product. Not marketing — the thing customers use.product
/pricing/PricingPer-endpoint or per-tenant bands. A mid-market buyer will not book a call to learn the price.phase 1

Why compliance pages exist

“NIS2”, “DORA”, “CRA deadline” are what a scoped company actually types into a search box. Each regulation gets its own page in all three languages — the highest-intent traffic Shield can win, currently won by consultancies.

Why /incident/ is not in the nav

It is a red button in the header on every page. Someone reaching for it is mid-breach and will not read a menu. One phone number, one form, no marketing — and it must work when the rest of the site does not.

Where the 57 projects live

Fifteen get a page. The rest stay in the internal guide until there is a team and a reference to put behind them. A solutions page listing capabilities you cannot staff is the fastest way to lose a technical buyer.