featkpr Private demo

The open-source apps featkpr has run on, and how far each got.

BookStackopen-source wiki 307 features in 12 modules · 163 paths to 69 goals · 304 tests pass, 269 refused to the wrong user · 605 of 2,372 missed in the missed-items check
featkpr itselfthis product, on its own code dogfooding stage 1 built: 26 of its own screens entered as planned rows · reading its own merge requests, crawling and testing itself are planned
Uptime Kumauptime monitor the TypeScript indexer read 8,475 symbols in 388 files in 10 s · 0 of 113 routes keyed yet · first target for the Node route reader
Paperless-ngxdocument manager the Python indexer read 405 of 405 files, 18,867 symbols · routes need the Python route reader (planned)
InvenTreeinventory management a chosen next-stage target, with its own package and pass criteria
Immichphoto library a chosen next-stage target, with its own package and pass criteria
Formbrickssurveys a chosen next-stage target, with its own package and pass criteria
Actual Budgetpersonal finance picked as the product a non-technical person already has opinions about · nothing run yet
16 more weighed in research, not started
Chatwoot

customer support

kept as an alternate: named feature flags
Documenso

document signing

kept as an alternate: 132 end-to-end specs to compare against
OpenProject

project management

on the candidate list
Mastodon

social network

on the candidate list
Weblate

translation

on the candidate list
Discourse

forum

on the candidate list
Taiga

agile boards

on the candidate list
Outline

team wiki

on the candidate list
Cal.diy

scheduling

dropped: maintenance
Medusa

commerce

dropped: six times the size
Baserow

no-code database

dropped: hosted on GitLab, split tiers
Plane

project tracking

dropped: no end-to-end suite to compare with
Twenty

CRM

dropped: per-object GraphQL API
Zulip

team chat

dropped: few screens
Sylius

commerce

dropped: no end-to-end suite
Firefly III

personal finance

dropped: no end-to-end suite

How a product joins

The same route for each one, and the audit says what was missed before anything is published.

1 · a folderDescribe the targethow to check it out, start it and seed one user per role
2 · a readerRead its stackLaravel and Mezzio are read fully today; Node and Python readers are planned
3 · one paid stepName the featuresthe naming pass, about a dollar for a new product
4 · a copyCrawl, draft, teston a throwaway copy, never the real product
5 · the auditCount what's missingthen publish, with the misses printed

Want your product in the library? Name it in the demo form →