Klority
Connected Wiki docs, tasks, and QA test management
We got tired of context switching and siloed data. So we built everything in one workspace:
Project Management with Kanban, sprints, capacity planning & burndown
QA/Test Hub with versioned test cases, cycles, runs, and public shareable reports
Wiki/Documentation powered by Tiptap + Mermaid diagrams + bidirectional linking
Light CRM for deals, pipelines, contacts, and activities
Everything is deeply linked — click from a bug straight to the failing test run and the related wiki page.
Built with React + Fastify + Drizzle on Postgres. Focused on lean teams that want Atlassian power without the complexity or cost.
Would love honest feedback, feature requests, or just to hear how you're solving the same problems. Free tier available, no credit card needed.
3 Comments
One thing I'd keep testing is whether customers are buying fewer tools or fewer context switches.
Replacing Jira, Confluence, and TestRail is a feature comparison. Helping a team stay in the same flow while moving from planning to testing to documentation feels like the much stronger reason to switch.
Exactly. “Fewer tools” is the outcome. “Fewer context switches” is the real value.
The interesting part for us is what happens between the tools — a requirement becomes a task, the task becomes a test, the test exposes a bug, and the whole chain stays connected without someone having to recreate context elsewhere.
That connected flow is what we're building Klority around.
Appreciate the perspective, Aryan.