The company behind QUANTIL
QUANTIL traces its corporate history to Mileweb, Inc., established in the United States by the Wangsu group on 23 July 2012. The company changed its name to Quantil, Inc. in May 2015. Its work focused on developing a new generation of content delivery technology for websites, software and media businesses reaching users across regions.
An engineering-led background
Bin Ni joined QUANTIL in 2013 as a founding engineer to work on its CDN platform. After Wangsu acquired CDNetworks, he led research and development for both companies from 2017. QUANTIL’s technology evolved beyond acceleration toward a programmable edge platform, giving development teams configuration tools and APIs to manage delivery behavior.
Its place within the Wangsu group
Quantil, Inc. is a US company controlled by Wangsu. Wangsu’s 2026 interim report lists it separately from Quantil Networks, Inc. and the regional CDNetworks companies. QUANTIL and CDNetworks have shared engineering and business connections; buyers should identify the supplier and service scope through the selected product, account entry point and order.
Accounts and the current buying route
QUANTIL’s documentation terms name Quantil, Inc. as the service provider. Its current new-account link leads to CDNetworks, whose self-service terms name CDNetworks, Inc. Confirm the account, service order and invoicing entity before agreeing traffic, CPU usage, features, support and payment dates. Mainland China delivery needs valid domain ICP registration and activation by support; Near China is a separately enabled premium route.
Control delivery through configuration and an API
QUANTIL’s website covers downloads, video on demand, live streaming and edge compute. Its documentation also maintains CDN Pro and HDT as distinct product lines. CDN Pro is built for teams that want direct control over edge behavior: NGINX directives and JavaScript configure caching, headers, origin access and authorization within an application delivery workflow.
CDN Pro organizes configuration into properties and versions. Configure origins and certificates, validate and test in staging, then deploy to production and point the service hostname to an edge hostname with a CNAME. Deployed versions are locked; cloning a version before editing preserves a configuration to roll back to.
Design the cache key before caching personalized content
By default, caching follows the origin’s Cache-Control and Expires headers. Responses without cache instructions are not cached, and Set-Cookie also prevents caching. A no-store response is not stored; no-cache and max-age=0 require origin revalidation. Path and status rules control TTLs alongside purge, prefetch and stale-object handling.
The default cache key includes the hostname and path, while excluding the query string. Origin Vary headers do not automatically create separate cached variants. Add relevant parameters, languages, cookies or identities to the key, or bypass caching. Test rules for login, payment, personal data and API responses in staging.
Choose delivery scope by region and network
Client-zone rules select delivery server groups, redirects or rejection by visitor region and ISP. Groups such as Standard, Premium, Deluxe and Ultra affect delivery options and cost. Selecting a higher group also includes lower groups; usage is attributed to the group that serves the traffic.
Delivery from mainland China requires ICP Beian for the hostnames and activation by support. Setting the Beian flag alone does not enable access. Near China is a separate add-on using servers outside mainland China, with its own price and performance considerations. On-demand Anycast for apex domains has a different node footprint from normal CNAME routing.
Make security and operations explicit in the configuration
CDN Pro supports client-certificate verification, a client certificate for origin access, signed links, IP and Referer rules, and remote authorization services. Enable origin-certificate verification explicitly. HTTP/3 is available per property and is off by default. A WAF can be integrated with delivery.
Access logs require a hostname and format configuration, with retention selectable from one to 30 days. Real-time log streaming requires separate activation and an agreement. Confirm account permissions and charges for advanced features such as Origin Shield and Fast Route. The API and console share customer-level rate limits, so automation should handle HTTP 429 responses and retry guidance.