OrbitOne - Notes,Docs,Tasks,Repos,Vault - From the first note to the final commit

Hey Product Hunt! 👋 I’m David, the maker behind OrbitOne. OrbitOne started with a problem I kept running into in my own work: our documentation was in one place, notes somewhere else, tasks in another system, files on a drive and code in a repository. None of those tools were necessarily bad. The problem was everything between them. Why was a task created? Which decision led to a code change? Where is the current file? Which checklist item is still open? And where did we document how the system actually works? I built OrbitOne to keep that context connected. With OrbitOne, teams can manage: 📝 Personal and shared notes 📚 Structured documentation ✅ Tasks, lists and Kanban boards 📁 Files, versions and desktop synchronization 💻 Git repositories, commits and diffs 🔐 Personal and shared credential vaults 🔎 Search, activity and workspace permissions The part I care about most is not the number of modules. It is how they work together. A checklist entry can become a task. A task can link back to the note or document that created it. Files stay attached to the relevant work. Commits and repository changes remain visible next to the project context. OrbitOne currently includes: • A complete web workspace • OrbitOne Drive for Windows and macOS • A VS Code extension • A browser extension for OrbitOne Vault • Standard Git clone, push and pull over HTTPS There is a free plan for up to three users, including every OrbitOne module. The paid plan only increases capacity rather than unlocking the actual product. OrbitOne is still young, and mobile apps are already in development. I would especially love feedback from developers, IT teams, agencies and small product teams: Does connecting documentation, tasks, files and code solve a problem you recognize—or do you prefer keeping these areas in separate specialist tools? Thanks for taking a look! 🚀