Inkwellportfolio demo

About this demo

Inkwell 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 form endpoints are sandboxed and the database wipes daily.

Why this exists

Most engineering portfolios stop at the README. A buyer evaluating a freelancer for a "buy vs build" decision on form-submission infrastructure has to extrapolate from "built a thing on GitHub" to "can run a real form backend with spam filtering, multi-destination fan-out, and a Filament admin where I'd actually want to live." The extrapolation is expensive. Inkwell exists to shorten it.

Where my sibling projects sell to API teams (webhook-relay) or product teams (pennant), Inkwell is shaped for small businesses, marketing teams, and indie devs running a Webflow / Eleventy / static site who need a backend just for their contact form. The buyer profile is wider, the infrastructure flair is lighter, and the admin is a first-class artifact rather than a shell.

What's "production-shaped" mean?

The architecture is the architecture a real form backend would use: rate-limited public endpoint, JSON Schema validation, composable spam-scoring pipeline with explicit decision rules, multi-destination fan-out via Horizon, idempotency-keyed delivery jobs, audit log, compliance endpoints. 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.

What I'd build for you

If your team is debating buy vs build on a form backend, or you need a form-submission product that integrates with your existing stack (Zapier, Slack, CRM, sheets, …), the artifacts on this site are the kind of thing you'd be paying for. Contact me at philiprehberger.com or via Upwork.

What's not in v1

This is the honest framing — what a real engagement would harden: