Self-hosted issue tracker.
Ekso is a self-hosted issue tracker that runs on your own infrastructure — public cloud, private cloud, on-premise, or air-gapped. It logs bugs, defects, change requests, and incidents in the same workspace as project tasks, sprints, helpdesk tickets, and time tracking. Pricing is flat-rate for unlimited users with no per-seat fees. Ekso migrates from Jira, Linear, and Azure DevOps in two CLI commands.
Last reviewed May 2026
Issues, tasks, and tickets. One data model.
Ekso is an enterprise operations platform with a built-in issue tracker. Issues — bugs, defects, change requests, incidents, and feature requests — share the same data model as project tasks and helpdesk tickets. A bug logged via the helpdesk can be linked directly to the sprint task resolving it, with full traceability in a single self-hosted workspace.
Ekso is self-hosted by design: deployed on your own public cloud, private cloud, on-premise hardware, or air-gapped network.
Companies we've delivered for
Ekso issue tracker vs alternatives
| Feature | Ekso (self-hosted) | Jira / Linear / Azure DevOps |
|---|---|---|
| Hosting model | Your own infrastructure | Cloud-first (Jira Data Center EOL 2029) |
| Pricing | Flat-rate, unlimited users | Per-seat per month |
| Issue tracking | Built in | Built in |
| Helpdesk / service desk | Built in, same workspace | Separate product or integration |
| Time tracking | Built in | Add-on or separate tool |
| Financial reporting | Cost per issue, team, client | Not available |
| Workflow automation | Visual rules engine. No code. | Varies — XML or scripting on Jira |
| AI / MCP server | 104-tool MCP server in the box | Vendor AI only, cloud-hosted |
| GDPR boundary | Your firewall. Vendor not in the data path. | Vendor data processing agreement required |
| Air-gapped deployment | Supported | Not available on cloud products |
| Migration to Ekso | Two CLI commands. History preserved. | N/A |
Issue tracking in Ekso
Ekso’s issue data model supports configurable status workflows, custom fields, priority levels, severity ratings, labels, assignees, linked items, and file attachments. Issues can be created manually, via inbound email, via the REST API, or by AI agents using the MCP server. Each issue supports threaded comments, activity history, and time logging against the item.
Sprint boards display issues and tasks together. Backlog management, cycle planning, and board views are all available within the same workspace — no switching between a separate project tool and an issue tracker.
Workflow automation without scripts
Ekso’s rules engine triggers on issue events: field changes, status transitions, SLA breaches, incoming email replies, or scheduled conditions. Available actions include field updates, agent assignment, webhook delivery, and creation of linked tasks. All rules are configured through a visual interface — no code, no XML, no scripting. Business clocks (working hours and public holidays) can be applied to SLA and escalation rules.
Migrate from Jira, Linear, or Azure DevOps
Ekso migrates from existing issue trackers using two CLI commands:
ekso migrate jira collect --config migration.config.json --project ACME ekso migrate jira apply --config migration.config.json --process <process-id> --dry-run ekso migrate jira apply --config migration.config.json --process <process-id>
Issue history, comments, attachments, custom field values, sprint assignments, and user attribution are preserved. Supported sources: Jira Cloud, Jira Data Center, Linear, Azure DevOps, and Zendesk. Full documentation: ekso.dev/cli/migrate/overview.
104-tool MCP server, in the box
Ekso ships with a 104-tool MCP server in the standard installation. AI agents — including Claude, Cursor, and ChatGPT — can read issue backlogs, create and update issues, query sprint data, and generate reports using natural language. Users bring their own AI model keys — Anthropic, OpenAI, or Azure Foundry. No separate agent gateway licence is required.
Compliance and data residency
Ekso runs on your own infrastructure, so issue data — bug reports, change requests, linked attachments — stays within your environment. Ekso is not in the data path. GDPR, HIPAA, SOC 2, and DORA compliance is governed by your own infrastructure boundary. Air-gapped deployment is supported for defence, healthcare, and financial services environments.
Frequently asked questions
Ekso is a self-hosted issue tracker that combines issue tracking, project management, helpdesk, time tracking, and financial reporting in one workspace on your own infrastructure. Flat-rate pricing, unlimited users, and a 104-tool MCP server for AI integration.
An issue tracker records bugs, defects, and incidents. A project management tool organises tasks, milestones, and sprints. Ekso provides both in a single workspace — issues and tasks share the same data model, so a bug can be linked directly to the sprint task resolving it.
Yes. Ekso covers Jira’s core issue tracking — configurable workflows, custom fields, sprint boards, backlogs, and reporting — with no XML configuration and no per-seat fees. Jira Data Center reaches end-of-life in February 2029. Ekso migrates from Jira using ekso migrate jira collect and ekso migrate jira apply.
Yes. Connect a mailbox in Settings and inbound email is automatically converted into a trackable item, allowing external users to submit issues by email without an Ekso account.
Ekso’s visual rules engine triggers on issue events — field changes, status transitions, SLA breaches — and executes actions such as field updates, assignment, webhook calls, and linked task creation. No code or scripting required.
Yes. Ekso ships with a 104-tool MCP server. Claude, Cursor, ChatGPT, and any MCP-compatible agent can read and write issue data directly, enabling AI-assisted triage, duplicate detection, and natural language backlog reporting.
See the full Jira head-to-head: Ekso vs Jira →