Here’s a sneak peek of’s DRM protection

Protection of your content is of paramount importance. supports Digital Rights Management (DRM) for your content via a central authorization server. This method of content protection requires you to have an authorization URL where all requests for protected content must first be authorized.

How It Works

When a client requests protected content over, the path of the file and any HTTP GET query parameters are sent via HTTP POST to the authorization URL configured for the site. If the request is authorized, the authorization server responds with an HTTP 200 response. The content body of the response can optionally contain a JSON object with the correct path for the content on the origin server. Any other response from the authorization server is considered as an authorization failure and the client will receive an HTTP 403 error instead of the requested content.

Head on over to our docs to read more about how’s DRM protection feature works.

We’ve got more awesome features coming soon, like Hotlink Whitelists and customizable cache paths and lifetimes, so stay tuned 🙂