About this demo

Pennant is a portfolio demonstration by Philip Rehberger. It is not a production service. Don't point real production traffic at it; the live demo's API key minting and sandbox isolation are intentionally relaxed so you can read the wire format end-to-end without registration friction.

Why this exists

Most engineering portfolios stop at the README. A buyer evaluating a freelancer for an "API product" engagement is being asked to extrapolate from "built a thing on GitHub" to "can deliver a production API with docs, SDKs, and a deploy story to my team's standards." The extrapolation is expensive, and most freelancers don't shorten it. Pennant — and its sibling project webhook-relay — exist to close that gap.

Where webhook-relay sells to API teams (HMAC signing, retries, dead-letter queues), Pennant is shaped for product teams: targeting rules, percentage rollouts, kill switches, audit trails, real-time SDK updates.

What's "production-shaped" mean?

The architecture is the architecture a real flag service would use, and the SDK is built the way a real flag SDK gets built — synchronous reads that never throw, deterministic bucketing, offline-resilient cache, graceful degradation when the SSE connection drops. But this is one person working on a portfolio. There is no on-call rotation, no five-nines SLA, no SOC2 audit. "Production-shaped, not production-grade" is the honest framing.

What I'd build for you

If your team is debating "buy vs build" on a flag service, or you have an API project that needs the whole product surface delivered, the artifacts on this site are the kind of thing you'd be paying for. Contact me at philiprehberger.com or via Upwork.