Incident responseAEM as a Cloud Service
The outage that wasn’t our release
A commerce site’s publish tier went down right after we deployed a different site. Suspicion fell on our release. We traced the real root cause, one unguarded API call exhausting the thread pool, and proved it against every symptom.
4 / 4symptoms explained by one root cause
GovernanceJava / OSGi
Locking one component to one team
Per-component edit permissions AEM doesn’t offer out of the box, enforced on the server and designed so it can’t take a repository down.
3server-side enforcement points
DispatcherSecurity
Content Security Policy as code
Hand-edited security headers replaced by a small build step: readable source in, consistent Dispatcher config out.
0hand-edited header strings left
Code qualityAI-assisted
A 59-agent audit of an enterprise codebase
An AI-assisted architecture review, every finding verified by hand, turned into a remediation playbook the team now codes by.
87verified findings, 6 critical
AutomotiveCloud migration
From on-premise AEM to Cloud Manager
Architecting a global automaker’s multi-year move to the cloud: environments, CI/CD pipelines and deployment workflows for many brands.
Multi-brandmarketing platform modernized
Multi-languageDispatcher
One switcher, six locales
Country and language sites from one content tree, short public URLs, and a switcher that keeps visitors on the same page.
6locales from one content tree
U.S. NavyAdobe CQ
Naval History and Heritage Command
Technical lead and Adobe CQ expert for the Navy’s history archive: books, photographs, ship logs and articles, onsite and remote teams.
27,000photos and 300 books online