Evaluation criteria
Use this checklist when comparing tools in the directory or writing a contribution.
| # | Question | Catalog fields |
|---|---|---|
| 1 | What problem am I solving? | problems, workflows |
| 2 | Is this tool appropriate? | categories, description, roles |
| 3 | License reality? | license.class, license.spdx, notes |
| 4 | Realistic run cost? | cost.* |
| 5 | Implementation & maintenance difficulty? | implementation.* |
| 6 | Which coworking workflows? | workflows |
| 7 | Which tasks reduced/augmented (not “replaced”)? | tasks_reduced_or_augmented |
| 8 | What data will it hold? | data_privacy |
| 9 | Privacy, security, compliance, lock-in risks? | risks |
| 10 | Install, backup, update, remove? | Implementation guides, compose packs |
| 11 | Integration with the rest of the stack? | integrations, stacks |
| 12 | Smallest useful experiment? | implementation.smallest_useful_experiment |
Scoring guidance (optional)
If you score tools internally, weight exportability, license fit, and maintenance burden higher than feature checklist length. A simpler tool you can restore from backup beats a feature-rich system nobody understands.