Infrastructure and installation
Requirements, supported environments, dependencies, secrets, network exposure, and upgrade path.
Open source · self-hosted business systems
Software you can run, inspect, and leave with.
Evaluate business fit, infrastructure responsibility, data ownership, deployment, backup, security, updates, and support before adopting a solution.
repository status
Repository URL required before install guidance is publishedSolution catalog
Operational products, not a wall of stars.
Repository counts change quickly. This design prioritizes purpose, requirements, license, release source, and support boundaries.
Repository inventory requiredNo approved solution repositories have been supplied.
Provide repository detailsConnect each repository, license, release status, documentation source, security policy, self-host path, and support expectation before publishing a catalog entry.
Self-hosting model
Ownership includes operating responsibility.
A useful solution page makes the work after installation visible before a team commits.
Backups, recovery, and updates
Data location, backup verification, restore process, release cadence, and rollback expectations.
Security and ownership boundaries
Reporting process, maintainer scope, contribution policy, and commercial implementation support.
Evaluation matrix
Every solution answers the same operational questions.
The comparison becomes useful when real repository and deployment data is connected.
| Evaluation field | What must be published | Source of truth |
|---|---|---|
| Purpose | Business problem, users, and workflow fit | Maintainer-approved description |
| Deployment | Requirements, install path, upgrades, backup | Versioned documentation |
| License | Use, modification, redistribution, obligations | Repository license |
| Security | Reporting, supported versions, known limits | Security policy |
| Support | Maintainer scope and commercial help | Published support policy |
Implementation support