Demo with an Engineer
A live session with an engineer from the team that builds Frontcache: how it sits in front of your app, fragment caching and invalidation running for real, and straight answers about your own pages.
fewer origin renders on our own benchmark — a replay of 100,000 production requests. Over that site’s full log the hit ratio was about 66.7%. In the session we talk about what yours could be. How it was measured
$200 · 45 minutes · video call
The Session
Built around your questions. Tell us in the form what you want to see, and the engineer comes prepared.
Where Frontcache sits — a reverse proxy in front of any origin, or in-process for Java apps — and what that means for your deployment, your CDN and your app servers.
Fragment caching, TTLs, tag-based invalidation and fallbacks running in front of a real site, including what the console shows while it happens.
A look at the site you tell us about: which pages and fragments look cacheable, where the boundaries would go, and what to measure before you decide anything.
How It Works
Details
An engineer from the team that develops Frontcache — someone who can answer how it works, not a sales script.
So the time goes to people with a real site and real questions, and the engineer can prepare for yours. If you would rather start free, send us an access log and we will tell you what share of your traffic looks cacheable.
Reply to the confirmation email up to 24 hours before the session and we move it at no charge. If we have to cancel, you get a full refund. A session missed without notice is not refunded.
The URL of a site or a staging copy, a rough idea of its traffic and what the app is built with, and the pages that are slowest or most expensive to render.
No. In front of your app, Frontcache is a reverse proxy, and anything that can set a response header can tell it what to cache. In-process mode is the Java-only option.
Next Step
Pick a time above. We respond within one business day.