KeyCDN Setup: Pull Zone, HTTPS, Caching & Integration

Static loading slow for European users? Origin server struggling under peak loads, TTFB climbing above 300 ms, and Core Web Vitals failing audits. For projects on Laravel, WordPress, or custom PHP, a typical issue is latency from remote infrastructure. We help set up KeyCDN—a European CDN with 35+ points of presence (PoPs), low latency, and pay-as-you-go pricing. After integration, TTFB drops to 30–50 ms, server load decreases by 85%, and cache hit rate reaches 98% with proper headers.

KeyCDN uses HTTP/2 and supports on-the-fly WebP conversion. We've connected it for 50+ sites—results are stable. Below we break down typical problems and the setup process.

Problems We Solve

• High TTFB—requests travel thousands of kilometers. KeyCDN brings content closer to users (PoPs in Frankfurt, Amsterdam, London), reducing latency by 3–5x.
• Origin overload—static files (CSS, JS, images) are served from the CDN, reducing server load by up to 80%.
• No WebP support—KeyCDN converts images to WebP on the fly, without changing URLs (via the format=webp parameter).
• Suboptimal caching—we set Cache-Control and Expires headers to maximize browser and CDN caching.

Pull Zone: How It Works

We use Pull Zones—KeyCDN fetches content from the origin on the first request. No rsync or FTP needed. For projects with already-uploaded files, Push Zones are suitable, but Pull is standard for dynamic sites.

Example of creating a Pull Zone via API:

curl -X POST \
    -u api_key: \
    -H "Content-Type: application/json" \
    -d '{
        "name": "example-assets",
        "type": "pull",
        "origins": [{"url": "https://example.ru"}],
        "ssl": true,
        "cors_headers": true,
        "cache_headers": true,
        "expire": 2592000,
        "custom_domains": ["cdn.example.ru"]
    }' \
    https://api.keycdn.com/zones.json

After creation, KeyCDN provides a CNAME (e.g., example-assets-1234.kxcdn.com). We add a CNAME record in DNS. SSL for the custom domain is issued automatically via Let's Encrypt.

For 90% of projects, we choose Pull—minimal manual work.

How to Set Up HTTPS for a Custom Domain?

After adding a custom domain to the zone, KeyCDN automatically issues a certificate via Let's Encrypt. Just point a CNAME to the provided CDN domain and wait 1–5 minutes. No manual CRL or CSR. Important: for HTTPS, make sure your origin server also serves static files over HTTPS to avoid mixed content.

Why Cache Invalidation Is Critical

Without it, after updating files (e.g., app.css?v2), users see the old version. Invalidation clears specific URLs or the entire zone. We implement it via API: call DELETE /zones/purgeurl/{zoneId}.json with a URL array. In Laravel, this is wrapped in a service provider (see below). Cache hit rate drops to 0% without invalidation—critical for updates.

Integration with Laravel

Simple static asset redirection via a service provider:

// config/cdn.php
return [
    'url' => env('CDN_URL', ''),
    'enabled' => env('CDN_ENABLED', false),
];

// AppServiceProvider: override URL for assets
public function boot(): void
{
    if (config('cdn.enabled') && $cdnUrl = config('cdn.url')) {
        URL::forceRootUrl($cdnUrl);
    }
}

In templates, just use asset():

{{-- In templates -- }}
<img src="{{ asset('images/logo.png') }}" alt="KeyCDN setup">
{{-- Outputs: https://cdn.example.ru/images/logo.png -- }}

Cache invalidation—wrapper via API:

use Illuminate\Support\Facades\Http;

class KeyCdnService
{
    private string $apiKey;
    private string $zoneId;

    public function purge(array $urls): void
    {
        Http::withBasicAuth($this->apiKey, '')
            ->delete("https://api.keycdn.com/zones/purgeurl/{$this->zoneId}.json", [
                'urls' => $urls,
            ]);
    }

    public function purgeAll(): void
    {
        Http::withBasicAuth($this->apiKey, '')
            ->get("https://api.keycdn.com/zones/purge/{$this->zoneId}.json");
    }
}

Origin Header Configuration

KeyCDN caches what the origin sends. Proper headers on Nginx:

location /assets/ {
    expires 1y;
    add_header Cache-Control "public, max-age=31536000, immutable";
    add_header Access-Control-Allow-Origin *;
}

To improve hit rate, use s-maxage and stale-while-revalidate for the CDN. Enable WebP via the ?format=webp parameter in zone settings.

Our Process

1. Audit—analyze current metrics, identify static resources, check caching headers.
2. Zone creation—set up Pull Zone, specify origin, enable HTTPS, CORS, custom domain.
3. DNS—add CNAME record, wait for propagation (up to 30 minutes).
4. SSL—KeyCDN automatically issues Let's Encrypt.
5. Integration—plug CDN into code (Laravel, WordPress, any CMS), set up cache invalidation.
6. Testing—verify caching accuracy, load speed, WebP.
7. Monitoring—set up KeyCDN analytics (traffic, cache hit rate, status codes).

What's included: integration documentation (code, commits), access to KeyCDN panel, API keys, team training on cache and invalidation, 30-day technical support.

Timelines and Guarantees

Basic setup—2 to 4 hours from access provision. Complex projects (custom origins, multiple zones)—up to 2 days. Pricing is individualized. 5+ years of experience, 50+ projects delivered—we guarantee stable operation and support. Contact us for a free audit of your current infrastructure. Get a consultation on KeyCDN setup.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.