Kendo HQ

Appearance

Mission & Vision ​

Vision ​

A world where development teams spend their time building, not managing tools. Where AI handles the routine so humans can focus on the creative.

Mission ​

Build the issue tracker that lives in your terminal — where your AI assistant manages your board, your time tracking is built in, and your data stays in Europe.

Beliefs ​

  • Tools should disappear. The best project management happens when you barely notice the tool. If you're spending time configuring workflows, the tool has failed.
  • Simplicity is a feature. Every feature we don't add is time saved for every user. We add things when the pain of not having them is obvious.
  • Developers deserve better. The people building software shouldn't have to fight their project management tool. It should feel like it was built by someone who gets it — because it was.
  • Everything included. Time tracking, audit logging, compliance — these aren't enterprise upsells. They ship with every tier.

Strategic Priorities ​

  1. Nail the core — Issue tracking, board, backlog, sprints, and epics must be fast, reliable, and pleasant to use before anything else matters. See product-overview.md for the full feature set.
  2. MCP ecosystem — Be the project board that lives inside AI assistants. 29 MCP tools. If a developer uses Claude, Cursor, or Codex, they should manage Kendo without opening a browser. This is currently our strongest differentiator — see competitors.md for the competitive landscape.
  3. European trust — Amsterdam-hosted, Dutch-owned, database-per-tenant, hash-chained audit logs. GDPR by architecture, not by policy. 54% of EU IT decision-makers prioritize data sovereignty; no competitor in the developer PM segment offers EU hosting by default at this price point. Regulatory tailwinds (NIS2, EU Data Act, Schrems III threat) only strengthen this position. Resonates most with the CTO "Christiaan" persona. (See research/eu-data-sovereignty-demand-2026.md)
  4. Everything-included pricing — Time tracking, audit logging, and compliance at every tier. Competitors gate these behind enterprise plans. We don't. See go-to-market.md for pricing rationale.
  5. Community-first growth — Developers buy tools that other developers recommend. Build in public, share decisions, earn trust. See go-to-market.md for the community playbook.