FlowDesk - A local-first workspace for teams and creators

FlowDesk is open source. Anyone is welcome to study, fork, and build their own projects using the source code in accordance with the project's license. However, the official FlowDesk project is maintained and released only by the FlowDesk core team. Contributions to the official project are accepted through review and approval by the maintainers.

Add a comment

Replies

Best
👋 Hi Product Hunt! I'm Kharis, the creator of FlowDesk. I started building FlowDesk because I wanted a project management tool that truly puts users in control of their data. Most productivity apps today are cloud-first, require subscriptions, or stop being useful when you're offline. FlowDesk takes a different approach. It's local-first, meaning your workspace lives on your own device by default. You can manage projects, tasks, notes, documents, and files completely offline. When collaboration is needed, you can create a Local Workspace for your team or deploy an Online Workspace without changing how you work. FlowDesk is also open source, and I'm building it as a long-term project with a focus on privacy, ownership, and simplicity. I'd love to hear your feedback, feature ideas, or questions. Thank you for checking out FlowDesk!

The open source approach is refreshing, and the repo is clean enough to fork without hours of cleanup. The core team's review process seems strict though, which is probably a good thing long term.

 Thank you for your thoughtful feedback!

Making the codebase accessible for learning and experimentation has been one of my goals from the beginning. At the same time, I want to keep the official project stable and maintainable as it grows, so contributions go through a careful review process.

Anyone is welcome to learn from, fork, or build upon FlowDesk. The official project, however, is maintained through a reviewed contribution process to help ensure long-term quality and consistency.

I really appreciate you taking the time to explore the repository and share your thoughts!

A contributing guide in the repo would be a nice touch, even though contributions go through review. Something simple like a CONTRIBUTING.md with a checklist for PRs and how to run the project locally would lower the barrier for new folks wanting to fork and experiment.

Love that it's open source and the maintainers are keeping a tight grip on official releases. Forked it yesterday and the code is surprisingly clean, made it easy to tinker with.

the maintainer-first approach to contributions shows real care for code quality. open source done with that level of curation tends to age really well.