Capture the work
Epics, Stories, Tasks, Bugs, and Sub-tasks follow a clear hierarchy. Markdown descriptions can include attachments, labels, priorities, and due dates.
Open source · self-hosted · MIT
Every ticket.
One clear view.
Ticket Hub helps software teams plan work, follow progress, and keep context close. It runs on your infrastructure and stays practical for everyday use.
Built for one team and its software projects. Accounts are created by an administrator.
Kanban + backlogActive and planned work
PostgreSQL / SQLiteTwo database backends
C++20 + CrowA focused server stack
Vanilla webHTML, CSS, JavaScript
Everyday work
From idea to done
Create a ticket, add the details, and give the team a shared view of what is happening. Ticket Hub keeps the work and its context together.
Move it forward
A separate backlog and Kanban board distinguish planned work from tickets that are active, under review, or done.
Keep the decisions
Comments, mentions, change history, and ticket links preserve context where the work happens.
The full picture
Everything important on one ticket
Status, ownership, comments, work logs, and history each have their place. Old ticket keys remain resolvable after a move between projects.
- Markdown descriptions, checklists, and attachments
- Links for dependencies and related tickets
- History of real field and status changes
Your infrastructure
Run it on your own terms
Ticket Hub is built for a single self-hosted installation. The supported production path uses Docker Compose with PostgreSQL. SQLite offers the same user-facing features for a single-process setup.
Administrators create accounts, fixed project roles control editing, and the source code is available under the MIT license.
Read the deployment guide →
See the product
Take a closer look at Ticket Hub.
Real application screens and a clear account of what it does today.