ClearFlask

ClearFlask collects product ideas from users and turns them into a public roadmap. It is positioned as an alternative to Canny and UserVoice, so a team can keep its feedback portal, customer dashboard and roadmap on infrastructure it controls rather than renting the whole conversation.

The codebase separates an OpenAPI definition from a Java server and a React frontend. A Node server nicknamed Connect serves static files and server-side rendered pages and issues TLS certificates for customer domains, while the backend keeps most data in DynamoDB, replicates it to Elasticsearch for search, serves uploads from S3 and uses KillBill for billing.

Self-hosting is the part the documentation covers most closely.

• One-click deploy: a Railway template runs a self-contained instance with API server, rendered frontend and MariaDB on a generated domain.
• Docker Compose: a single compose file with a dependency profile brings everything up and opens on localhost.
• Kubernetes: Helm charts install ClearFlask and its dependencies after you generate the signing and cursor secrets.
• Storage choice: search runs against Elasticsearch or MySQL, with a documented migration between them.
• Domains and mail: a custom domain needs DNS and certificate setup, and outgoing email is configured separately.

Managed hosting is offered by the maintainers for teams that would rather not operate any of this. The self-hosted path suits a product team that wants its feedback portal on its own domain and its data in its own account.