Who is it for?
Teams exposing panels, APIs, WordPress, and PHP applications to the internet with an additional protection layer.
Security layer
Edge Security & WAF
A security approach that protects web applications at the edge with WAF, traffic policies, and TLS.
How does it work?
Traffic reaches the cdn.com.tr edge first; SSL, WAF, and cache policies are applied per domain.
Included services
Auto SSL, DNS routing, WAF visibility, cache, and purge controls work together.
Example scenario
WordPress admin and public traffic are handled with edge policies before requests reach origin.
Example scenarios
WordPress protection
Add edge controls against common attack patterns.
API security
Place container API traffic behind WAF.
Origin shielding
Publish without exposing the app server directly.
Frequently asked questions
Yes. The services described here are positioned around the same CDN account, domain, SSL, cache, and WAF layers.
Basic CDN and WordPress flows can be handled from the panel. Container, GitHub deploy, and custom migration scenarios are better planned with technical support.