Create an account
Open the IXCDN console and connect one workload.
Why IXCDN
IXCDN does edge delivery only, with two core products: CDN and AI Gateway. Together they answer the three questions global teams ask most: cost, latency and security.
-
Websites, APIs, downloads and media run through edge cache, DNS routing and origin shielding: up to 91% cache hit ratio, 80%+ faster overseas page loads and 60% lower origin bandwidth cost.
Start for Free -
Chat, search, agents, AIGC and model APIs share one OpenAI-compatible ingress for token streams, keys, routing and logs: 38% lower first-token wait with almost no code changes.
Start for Free -
The Free plan is free forever. Pro bills by delivered traffic, while AI tokens, storage, compute and enterprise routes are metered separately.
Start for Free -
DDoS, WAF, TLS, access control and token validation run before origins and model services, with a 99.9%+ attack blocking rate and an observe-first rollout.
Start for Free
Start in minutes
Four steps to run one workload
Take one workload through speed, cache hit, HTTPS, token streaming, security policy and billing before expanding.Add an ingress
Enter the domain, origin or AI API endpoint and complete DNS validation.
Enable acceleration and protection
Use a free certificate or upload your own, then set cache, token, rate-limit and security policy.
Read the numbers
Check traffic, hit ratio, token requests, logs, billing and suspicious requests in the console.
Decision points
Traditional CDN vs IXCDN
Area Traditional CDN IXCDN
Latency
Origin-only or single-region delivery is exposed to route changes, long origin distance and origin pressure.
CDN and AI Gateway traffic enters the edge first, then routes by region, carrier, load and policy.
Cost
Traditional setups mix traffic, origin fetches, model requests and enterprise routes, so budgets are hard to review.
CDN traffic, AI tokens, storage, compute and enterprise routes are separate line items that map to projects.
Security
Security often sits outside or is split across tools, so bad traffic is found close to origin or model services.
DDoS, WAF, TLS, token validation and origin protection take effect at the edge ingress.
Operations
Domains, certificates, cache, security and logs are configured in separate tools, so onboarding depends on manual handoffs.
Add a domain or AI API, verify DNS, enable HTTPS, and set cache, security and logs in one console.