← All problems
Problem

Rules in one line

The problem

Real rules for splitting the cache combine values: one shared answer per customer and language, a preview for editors that skips the cache, a user ID you'd rather keep out of your logs.

With GraphPilot

Radiogram, GraphPilot's policy expression language, reads verified token claims next to headers, cookies and URL parameters, joins and normalizes them, compares versions and can turn a user ID into a pseudonym, in one line of configuration.

Docs: Policy expressions ↗
Transcript

Splitting the cache by one value is easy. Real rules rarely are.

One shared answer per customer and language. A preview for editors that skips the cache. A user ID you'd rather keep out of your logs.

Build that into your origin, and each rule ends up in app code, often keyed on a header any caller can set.

GraphPilot has its own small expression language: Radiogram. It reads verified token claims, and headers, cookies and URL parameters.

Join values, normalize them, compare versions, or turn a user ID into a pseudonym, in one line.

When you deploy, GraphPilot warns you about a negation that a request could leave undecided.

Cleared for takeoff

Start on Glider (Free).
No credit card, no commitment.

Prefer to talk first? Book a call