featkpr Private demo

See featkpr on a real product, privately

We show you the live app on BookStack, an open-source wiki we don't own. After that, read-only access for you and the people you choose.

private, by invite · no public demo yet

How it goes

You askone email is enough; the rest is optional
We show you the real app, livehalf an hour, on BookStack, your questions first
A read-only inviteonce invites exist; until then, the call is the demo
Your product nextwe take a few at a time; the library shows who is in line

Ask for a private demo

You get one email saying we have it, then a reply from Tim by hand. No newsletter unless you tick the box. What we keep. Prefer email? hello@featkpr.com

What you will see

the app's own screens, on BookStack · crawl of 25 Sep 2026

Every path, screen by screen, with what to check
Every test, what it sent, what came back
How far each feature is known, from code only to proven

What read-only will mean

invites are not built yet · this is the plan they are built to

You can

  • open every screen of the BookStack map
  • walk every path and see every test's evidence
  • share the invite with your team

You can't

  • keep or drop a path, or change anything
  • see another customer's product
  • start a crawl or a run

What it takes, today

as of 27 Sep 2026 · ask on the call if your case differs

Works withPHP web apps today: Laravel read in full, Mezzio read from code. Node and Python readers come next.
We needRead access to the repository, and a test copy of the app we can start and seed with one user per role. Never your production.
Your code goesTo featkpr's own servers, and, for naming features and drafting journeys, in excerpts to hosted AI models through OpenRouter. We name each model before we start.
You getThe map of your app, the journeys to keep or drop, and pytest tests that call your app through Playwright, each with what it sent and what came back.
PriceNot set yet. The first teams work with Tim directly.