Questions, answered

Yes. Iskue runs entirely on your own infrastructure with Docker — a single host for most teams, or a distributed PostgreSQL (Citus) cluster when you need to scale out. Your tickets, attachments and user data never leave servers you control.

Iskue imports tickets from a Jira CSV export — the import understands Jira's export format — and CSV export works the same way in the other direction. Project workflows, labels and custom fields are all configurable per project, and Jira priorities map onto Iskue's five-level priority scale during import.

Yes — optional OIDC single sign-on with Google and Microsoft (Azure AD). New users are auto-provisioned and existing accounts link on a provider-verified email. Local accounts can additionally enable TOTP two-factor authentication with single-use recovery codes. Without an SSO provider configured, the app simply stays password-only.

Iskue has TQL, a ticket query language: for example, project = CORE AND assignee = me AND status != Done ORDER BY priority DESC. It supports AND/OR/NOT, IN lists and ~ full-text contains backed by PostgreSQL, plus saved private and shared filters and an instant quick search. All results respect project membership and ticket visibility.

Yes. There is a full REST API with OpenAPI documentation, outbound webhooks signed with HMAC-SHA256 and delivered through an outbox with retries, a Slack integration that posts ticket activity to a channel, and inbound Git integration that links commits to tickets by key reference.

English and French, throughout the entire application.

Use the contact form or write to contact@iskue.com for a demo, a pilot on your infrastructure, licensing and support.