Edge cachingEdge caching that works from the first request.
Static files are cached automatically as soon as your site is live. nsin follows your server's Cache-Control headers, serves a saved copy from the edge, and leaves your origin with far less to do.
On by default, safe by default
Images, CSS, JavaScript, fonts, media and downloads are cached by file extension for every domain. HTML is not cached this way, and nothing private is ever stored.
- Static files cached automatically
- Never stores no-store, private or Set-Cookie responses
- Query string is part of the cache key, so ?v= busting works
Cache rules when you want more
Decide what is stored by path, file extension, query string and cookies. Choose cache-first to serve hits instantly and refresh in the background, or upstream-first to ask your server before falling back to the copy.
- Cache HTML and API responses on your terms
- stale-while-revalidate and stale-if-error honoured
- Rules scoped to all hostnames or selected ones
Purge, inspect and debug
Every response carries an Nsn-Cache-Status header: HIT, MISS, BYPASS or DYNAMIC. Clear everything or a single page from the panel, and switch on developer mode while you are editing.
- One-click purge, whole site or by URL
- Developer mode that turns itself off
- Cache hit rate and storage in analytics
Frequently asked questions
What does nsin cache by default?
Static files by extension: images, CSS, JavaScript, fonts, media and common download formats. Pages that change per user stay uncached unless you add a cache rule.
How long is a file cached?
As long as your server's Cache-Control header says. If your server sends none, nsin checks back after five minutes, or after the refresh interval of your cache rule.
How do I show a new version right away?
Purge the page or the whole cache from the panel. Files with a hash or a ?v= version in the URL need no purge at all.
Will logged-in users see each other's pages?
No. Responses that set a cookie, requests with an Authorization header and anything marked private or no-store are never cached.