Know your hit ratio before you buy anything.

Two weeks of our engineers on your traffic and your pages. You get the number your site would actually reach, and the plan to get there — before you commit to a subscription or an implementation.

  • $9,500, fixed fee, two weeks. No open-ended consulting meter.
  • Credited in full against a first-year subscription if you go ahead.
  • Start with a $200 demo with an engineer — credited toward the Assessment.
  • You keep the report either way — your hit ratio, your fragment plan, your projected saving.
  • With a bot-traffic section: how much of your traffic is bots, and which “crawlers” are not.
  • Any origin language. Frontcache runs as a reverse proxy in front of the app; Java apps can also run it in-process.
98.7%

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%. The Assessment measures yours. How it was measured

Start with 45 minutes with an engineer

$200, credited in full toward the Assessment if you book it. We look at your pages and scope the two weeks.

1. Pick a time

Times are in your time zone.

Loading open times…

2. About you

Reschedule free up to 24 hours before by replying to the confirmation email; if we cancel, you get a full refund; a session missed without notice is not refunded. Payment by PayPal — privacy policy.

Not ready for a call? Send us an access log for a free first look.

What the Report Contains

Measured on your traffic, not a generic benchmark — with the arithmetic shown, so your finance team can check it.

Your hit ratio and offload

Your recorded traffic replayed against a Frontcache node in front of your app. The hit ratio you would actually reach, the share of renders that leave your origin, and the app-tier capacity that frees.

A fragment plan

Which pages to split, where the fragment boundaries go, which TTL and which invalidation tags each fragment gets — including a separate lifetime for crawlers where that pays.

Dollars per year

The origin compute you would no longer run, priced at your rates, next to what Frontcache would cost. If the saving does not cover it, the report says so.

Your bot traffic

From the same log: the share of your traffic that is bots, the share that claims to be a search crawler and does not come from its network, and which guard rules — rate limits, honeypots, challenges — would have acted, and on how many requests.

Two Weeks, Four Steps

  1. ScopeA call to pick the pages and traffic that matter, and to agree on a traffic sample and a staging environment we can work against.
  2. ReplayWe put a Frontcache node in front of your app and replay your traffic through it, measuring hit ratio and origin load.
  3. PlanFragment boundaries, TTLs, tags and crawler policy for your pages — with the hit ratio each change buys.
  4. ReportA written report and a walkthrough with your team. Yours to keep, whatever you decide next.

The Multiplier Is Yours, Not Ours

A 6× throughput gain means roughly one sixth of the app tier — and the database, search tier and third-party API calls behind it see the same cut. But the multiplier depends on your pages, your TTLs and your traffic. Our own benchmark shows 98.7% on a hot working set and about 66.7% over the full log of the same site.

You can measure it yourself: the engine is free, and the Docker quickstart takes five minutes. The Assessment is for when you want the number on your own traffic, a plan to reach it, and someone accountable for both.

Run It Yourself

Common Questions

Is the fee wasted if we do not proceed?

You keep the report either way — your hit ratio, your fragment plan, your bot traffic and your projected saving. If you do subscribe, the full $9,500 is credited against your first year.

What do you need from us?

A sample of recent traffic (an access log is the usual starting point), a staging environment we can put a Frontcache node in front of, and a few hours from someone who knows how the pages are built.

Does our traffic data leave our infrastructure?

Only what you choose to send us, and it is used for the Assessment alone. If logs cannot leave, we run the replay inside your environment instead.

Our app is not written in Java. Does that matter?

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.

Can we start smaller?

Yes — a $200 demo with an engineer, credited toward the Assessment, or send us an access log for a free first look: what share of your traffic is crawlers, which URLs dominate, and a first estimate of what is cacheable.

Frontcache in Production

Frontcache in production — a walkthrough of the cache features running in front of hobbyray.com (13 mins)

Start With Your Own Numbers

Start with 45 minutes with an engineer — $200, credited in full toward the Assessment. Or send an access log for a free first look; we respond within one business day.