Tickets with real structure
Epics, stories, tasks and bugs with sub-tickets and automatic progress rollup. Labels, watchers, story-point estimates, comments and a full change history — under race-safe sequential keys like PROJ-123.
Issue tracking & agile planning
Iskue: plan, track and ship on infrastructure you own
Iskue gives your team kanban boards, sprints, a real workflow engine, a service desk with SLAs and a query language people actually use — self-hosted with Docker, backed by PostgreSQL, with every byte of your data on your own servers.
English & French interface · your data never leaves your servers
8custom field types
40backend modules
130+end-to-end tests
EN·FRfull bilingual UI
Everything a tracker should do.
Nothing it shouldn't.
Iskue covers the full life of a ticket — from backlog to board to release — in one product with three editions. The tracker itself is Standard; cross-project planning is Professional; the scaled-agile suite is Enterprise. Tiles say which, and nothing is a plugin you have to hunt for.
Custom fields
Eight field types you define per project, stored natively in PostgreSQL — capture what your process needs without schema surgery.
A workflow engine, not a status list
Per-project statuses and transition rules, editable in settings. Start from Scrum, Kanban, bug-tracking or SAFe-portfolio templates; every transition is validated against the rules you set.
Boards that stay live
Drag-and-drop kanban with instant updates streamed over Server-Sent Events — when a teammate moves a card, you see it move.
Backlog & sprints
Precise, stable backlog ordering, one active sprint per project by design, and unfinished work that returns to the backlog when the sprint closes — automatically.
Reports you can trust
History-based burndown that survives ticket renames, velocity across sprints, a sprint roadmap timeline, and a personal dashboard of your open work across every project.
Structures for portfolios
Shareable ticket trees built from TQL — insert, extend by children, group, filter, sort — with saved views you can share and computed columns that write back to fields.
TQL search
A ticket query language with AND/OR/NOT,IN lists and full-text ~ matching — plus saved private and shared filters, and instant quick search.
Docs with live ticket blocks
Confluence-style Docs spaces and project wikis: a visual editor, 30 blocks, live TQL ticket lists and charts, a drag-and-drop page tree and permanent page links.
Plans, goals & docs
Cross-project Gantt plans with dependencies, capacity and what-if scenarios you commit or discard; goals that measure themselves from linked tickets and align to strategic themes; documentation spaces with page trees, revisions and one search across every wiki.
Scaled agile (SAFe)
Agile Release Trains and solution trains, Program Increments with objectives, ROAM risks, burn-up and predictability, a program board with dependency arrows, value streams with lean-budget guardrails — on the same tickets your teams already use.
Notifications, your way
An in-app inbox with an unread badge, a per-project activity feed, and an optional email channel every user can switch off for themselves.
Service desk built in
Request types, a branded customer portal, queues, SLAs that pause, multi-stage approvals, an email channel, a knowledge base customers can search and CSAT — in the same product as your sprints.
ITSM and a status page
Incidents with a priority matrix and timeline, changes with risk and freeze windows, problems, services, assets — and a public status page that never leaks a restricted ticket.
AI, off until you say so
Portal answers from your knowledge base, reply drafts, summaries and plain-language search — with your own Anthropic or OpenAI-compatible key and a monthly token budget.
Automation rules
When a ticket is created, updated, transitioned, commented or relabelled — and your conditions match — assign it, set priority, transition it, label it or comment. Rules run after commit and respect your workflow.
Plays well with others
A REST API with OpenAPI docs, personal access tokens, HMAC-signed webhooks with retries, two-way Slack, Microsoft Teams notifications, Git commit linking by ticket key, and a live Jira Cloud / Data Center importer alongside Jira-compatible CSV.
Administration that scales
Global and per-project roles, user management with a last-admin guard, an audit log of what changed and who changed it, and built-in rate limiting.
Coming from Jira?
If your team works in Jira today and would like to keep its tracker on its own servers, Iskue may be worth a look. Atlassian has announced the end of life of its Data Center products for March 2029. Iskue runs on infrastructure you own, and its importer brings projects, issues, comments and attachments over from Jira Data Center or Jira Cloud — so you can try it side by side, at your own pace.
Atlassian's announcement: Data Center end of life.
Ask your tracker a real question
TQL — the Ticket Query Language — reads the way you think, with full-text matching backed by PostgreSQL. Then open the results as a spreadsheet across projects and edit them in place.
project = CORE AND assignee = me AND status != Done ORDER BY priority DESCYour servers. Your data. One command.
A single Docker Compose command brings up the full stack. When one box stops being enough, the same application deploys onto a distributed PostgreSQL (Citus) cluster.
# configure secrets
$ cp .env.example .env
# full stack, one host
$ docker compose --profile full up -d
iskue ready → http://localhost:8088See Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.