Managed Platforms turn CDN.com.tr from "a CDN in front of your server" into a place that runs your application for you. You can host a WordPress or PHP site, or deploy any Docker container — and the same global edge, automatic SSL and caching sit in front of it. Short answer to the common question: yes, you can use it as your hosting.
Traditional hosting hands you a server (or a slice of one) and you maintain the operating system, runtime, security patches and scaling yourself. "Managed" means the platform handles the infrastructure: you provide your application — a WordPress site, a PHP project, or a container image — and the platform runs, secures, renews certificates for, and serves it. You focus on your app, not on servers.
This is the most common question, so plainly: yes. You do not need a separate hosting provider. Point your domain here, choose WordPress, PHP, or a container app, and CDN.com.tr becomes where your site lives. Because it is built on the CDN, your site is automatically served through the global edge with caching and HTTPS — hosting and CDN in one place.
If you run a WordPress or PHP site, you do not need to know anything about containers. Choose the WordPress or PHP platform, pick your version, and deploy — the runtime, web server and TLS are handled for you. You can connect a custom domain, manage files, and turn on a managed Redis cache for speed, all from the panel.
If your app is not WordPress/PHP — say a Node/Express API, a Next.js site, a Go service, a worker, or a tool like Jenkins or RabbitMQ — you can run it as a Container App. You bring a Docker image (or import a docker-compose file) and the platform runs it, gives it a URL, and keeps it healthy. If "Docker" is unfamiliar, see the Docker guide — you often need less of it than you think.
Most apps need a database or a cache. Instead of running and securing those yourself, enable a managed add-on with one click: Redis, PostgreSQL, MySQL/MariaDB or NATS. The platform provisions it, keeps it running, and connects it to your app by an internal name — so your services talk to each other privately, without exposing anything to the internet.
Managed Platforms are not a VM or an SSH shell. You do not get OS-level package installs (no "apt install"), no Docker-in-Docker for building images inside a container, and no raw public TCP ports — public access is HTTP(S). It is also not a kubectl/SSH replacement. In exchange, you get a platform that runs and secures your app without server administration.
Managed WordPress with a custom domain, automatic HTTPS, a Redis cache and the CDN edge in front — no server to babysit.
Deploy your container app, enable a managed PostgreSQL or MySQL add-on, and connect them by internal name.
Import a docker-compose.yml: web, worker, database and cache come up together as managed apps and add-ons.