At a Glance:
ClearFlask is an open-source feedback management tool that can be self-hosted using Docker or Kubernetes, offering a transparent alternative to Canny and UserVoice with flexible dependency choices including MySQL, ElasticSearch, or OpenSearch.
Overview:
ClearFlask is an open-source feedback management tool designed to serve as a self-hosted alternative to Canny and UserVoice. It helps teams collect, organize, and manage user feedback without relying on closed-source SaaS platforms. The system consists of two main components: a Java Tomcat application for serving API requests and a Node.js component for server-side rendering, static file serving, and automatic certificate management. It supports deployment via Docker for quick starts or Kubernetes for production environments with horizontal pod autoscaling and zero-downtime rolling updates. ClearFlask is intended to be deployed on its own domain or subdomain and provides a super-admin dashboard for managing the platform after initial setup.
Key Decision Points:
Self-hosting complexity: ClearFlask can be deployed via Docker for quick evaluation or via Helm charts on Kubernetes for production environments, but both require managing separate dependencies like a database, an S3-compatible object store, and an email service.
Search engine flexibility: Administrators can choose between MySQL for lightweight, exact-match search suitable for small projects, or ElasticSearch/OpenSearch for advanced, fuzzy search intended for larger projects, with a documented migration path between the two.
Infrastructure dependency options: Self-hosters can swap out individual dependencies with API-compatible alternatives, such as using MinIO instead of AWS S3, Localstack or a DynamoDB-compatible database instead of AWS DynamoDB, and any SMTP provider instead of AWS SES.
Automated certificate management: The platform includes a built-in integration with Let's Encrypt to automatically fetch and renew TLS certificates, but it can also run behind a reverse proxy with user-managed certificates or, though discouraged, over plain HTTP.
Core Features:
Feedback Collection: Collects and manages user feedback as an alternative to Canny and UserVoice.
Dual-Component Architecture: The system is split into
clearflask-serverfor API request handling andclearflask-connectfor SSR, static file serving, and dynamic certificate management.Pluggable Search Backend: Supports MySQL for exact-match searching and ElasticSearch or OpenSearch for advanced fuzzy searching, allowing administrators to migrate between them based on project size and query requirements.
Automated TLS Certificates: Provides an option to automatically fetch and renew certificates from Let's Encrypt during the initial site load when publicly accessible.
Helm Chart for Kubernetes: Offers a production-ready Helm chart with built-in features like horizontal pod autoscaling, zero-downtime rolling updates, and health checks.
Super-Admin Account Control: Enables server administrators to whitelist an email for initial super-admin account creation and subsequently disable public signups.
Use Cases:
Teams wanting to own their feedback data: Organizations that need to collect and manage user feedback or feature requests while keeping all data within their own managed infrastructure.
System administrators evaluating alternatives: DevOps and infrastructure teams looking for a feedback platform that integrates with their existing container orchestration (Kubernetes), databases (MySQL, ElasticSearch, OpenSearch), and object storage (AWS S3, MinIO) systems.
Projects with varying search requirements: Small teams that can start with a lightweight MySQL backend for basic feedback search and later migrate to ElasticSearch as their feedback volume and search needs grow.
Open-Source Alternative Value:
ClearFlask provides a self-hosted, open-source alternative to proprietary feedback management tools like Canny and UserVoice. Its value lies in its documented self-hosting deployment model via Docker and Kubernetes, allowing operators to run the platform on their own infrastructure. The architecture offers concrete flexibility through swappable dependencies, including choice of search engine (MySQL, ElasticSearch, or OpenSearch), object storage (AWS S3 or MinIO), and email delivery (SMTP or AWS SES). This design enables system administrators to adapt the platform to their existing technology stack and resource constraints, avoiding a fixed dependency on a single vendor's infrastructure.
