Show HN: Tegon: Open-source alternative to Jira, Linear

Original Article ↗ Hacker News Discussion ↗

AI Features and Intended Value

  • Current AI features: auto-generated titles, smart delegation, duplicate detection, summarization, filtering, and automated triage.
  • Upcoming: an AI assistant that checks issue completeness (against label-specific templates) and suggests sub-issues; a chat assistant; specialized “agents” (e.g., code-fix and PRD-writing agents).
  • Cohere is used for embeddings, vector search, and re-ranking to improve duplicate detection and triage; OpenAI is used for other LLM tasks. Local models and Ollama support are planned; llama.cpp compatibility is noted.
  • Some users see clear value for support staff and non-technical reporters (e.g., dyslexia, missing details) if AI can complain about or fix low-quality bug reports.

Skepticism About “AI-First”

  • Multiple commenters question what “AI-first” concretely means, noting the product looks like a standard issue tracker with AI add-ons.
  • Concerns that AI hallucinations could degrade trust; some say they’d rather switch tools for speed, extensibility, and integrations than for AI.
  • Others argue every incumbent is already adding similar AI features, so this is not a durable differentiator.

Licensing and Business Model

  • Strong debate over MIT vs AGPL vs BSL vs “source-available.”
  • Some recommend AGPL to deter cloud giants while staying OSI-compliant.
  • Others push BSL to protect the vendor’s commercial interests, but critics stress BSL is not open source.
  • “Commercial use” restrictions are viewed as legally and practically ambiguous.
  • Dual-licensing (AGPL + commercial) is suggested; others warn enterprises often avoid AGPL entirely.

Open Source, Code Quality, and Docs

  • Critiques: sparse/broken self-hosting docs, empty pages, outdated scripts, confusing env vars, leftover foreign LICENSE file, and apparent dead/duplicated auth code.
  • Some see “open source” here as more marketing than community-centric.
  • Maintainers acknowledge gaps and promise to improve documentation, PR discipline, and modularity for contributions.

Performance, Hosting, and Integrations

  • Performance is highlighted as critical; Tegon preloads data on the client and syncs in the background.
  • Backend is Node.js; some question this, others say frontend is the real bottleneck and Node can be fast.
  • Plans for Slack-style chat interaction and ticket creation; duplicate-detection and smart merging intended to mitigate ticket spam.
  • Demo instance has had reliability issues (“no healthy upstream”, random issue spam).
  • Import/migration scripts from Jira etc. are in progress; a CRUD API exists, with OpenAPI spec planned.

Use Cases and Differentiation

  • Comparisons with Linear and Plane; design similarity to Linear is noted and criticized as derivative, though a redesign attempt is acknowledged.
  • Some users are curious about personal task-management use; Tegon has this on the roadmap.
  • Overall, many question what unique problem Tegon solves beyond “Jira but faster with AI helpers.”