Open source · Kubernetes-native · In development

Issue tracking built to run on your own infrastructure first

Projects, epics and configurable workflows linked to GitHub and GitLab, plus a service desk for requests from outside the team. It runs inside your environment, air-gapped if needed, from one container image, PostgreSQL and a Helm chart.

PLAT · Sprint 14 Scrum board

What's built

Everything a software team tracks, nothing it doesn't

Multi-project tracking, configurable workflows and Git-linked delivery, without a maze of configuration schemes.

01

Projects and hierarchy

Project keys, templates and roles. Epics, stories, tasks, bugs and sub-tasks, with links, custom fields, attachments, watchers and a full history.

02

Configurable workflows

Versioned state machines with conditions, validators and post-functions written in CEL. Edit them visually or apply YAML from Git.

03

Boards and planning

Scrum and Kanban boards with WIP limits and swimlanes, a ranked backlog, sprints, releases and a timeline across projects, updated live as the team works.

04

Query language

A JQL-like query language with saved and shared filters, compiled to SQL and backed by PostgreSQL full-text search.

05

Git-linked delivery

Branches, commits, pull and merge requests and pipeline status on every issue. Smart commits run real workflow transitions.

06

Identity and provisioning

Sign in with any OpenID Connect provider, including Keycloak, Entra ID and Google, or with a local account and two-factor authentication. Directory sync and SCIM handle joiners and leavers without a ticket.

07

Service desk

Service projects with a customer portal, request forms, queues, approvals and SLAs for first response and resolution. Customers see only their own requests.

08

Reports and time

Lead and cycle time, burndown, velocity and cumulative flow on shared dashboards, plus estimates, work logs and timesheets.

09

Automation

Rules that run on issue events, Git activity or a schedule, and signed outbound webhooks for everything else.

Workflows as code

Change your process with a pull request

Workflows are versioned YAML documents. Review them like code, apply them from CI, or edit them in the visual editor.

  • Statuses map to To do, In progress and Done, so reports work across every project
  • Conditions and validators are CEL expressions, tested like any other code
  • Issues stay on their workflow version until a migration moves them
More about workflows →
workflows/code-review.yaml
kind: Workflow
name: Code review
statuses:
  - { name: To Do, category: todo }
  - { name: In Progress, category: in_progress }
  - { name: In Review, category: in_progress }
  - { name: Done, category: done }
transitions:
  - name: Submit for review
    from: In Progress
    to: In Review
    validators:
      - expr: issue.devLinks.exists(d, d.kind == "pr")
        message: Link a pull request first.
  - name: Done
    from: In Review
    to: Done
    postFunctions: [{ notify: watchers }]

Integrations

Plugs into the tools you already run

Git hosts, identity providers and chat connect through standard protocols, with webhooks verified and processed idempotently.

Source control

GitHub

A GitHub App with fine-grained permissions and signed webhooks for pushes, pull requests, reviews and workflow runs.

Source control

GitLab

gitlab.com or self-managed. Group or project webhooks for pushes, merge requests and pipelines.

Identity

Keycloak

Sign-in with groups from the token, single and back-channel logout, and a scheduled sync of users and groups through the Admin REST API.

Identity

Google Workspace

Sign-in limited to your domains, plus a directory sync that deactivates suspended users on its next run.

Provisioning

Okta, Entra ID and SCIM

Any OpenID Connect provider can sign people in, and SCIM 2.0 lets your identity provider push users and groups.

Chat

Slack and Mattermost

Each project posts new issues, status changes, pull requests and failed pipelines to the channels it chooses.

AI assistants

MCP server

Claude and other assistants work with issues as the person who connected them, over OAuth, and their changes are marked as made through the assistant.

Migration

Import from Jira

Bring Cloud or Data Center projects over with their keys and history, and re-run the import while teams move across.

All integrations →

Your infrastructure first

One image, PostgreSQL and a Helm chart

Designed from day one to run inside your own environment, including air-gapped networks. Deploy with Argo CD; the same chart runs on a laptop, a home-lab k3s cluster or production EKS.

One container image

Runs as web, hooks and worker, so webhook bursts and background sync scale apart from the UI.

PostgreSQL is the only state

Issues, search, the job queue and the audit log all live in Postgres on CloudNativePG, and attachments can too.

k3s to EKS

Ingress and Gateway API routes, PDBs, NetworkPolicies, KEDA autoscaling and External Secrets support in one chart.

Zero-downtime upgrades

Schema migrations run as Argo CD PreSync jobs, written expand-then-contract.

Air-gap ready

Offline bundles of the images and chart, and only the webhook endpoint needs to face the internet.

Supply chain

The release pipeline signs images and charts with Cosign and attaches SBOMs, for regulated and defence environments.

How it runs →

Open source

Free to use, all of it

Workflow is licensed under Apache 2.0 and built in the open. There is one edition, and it has everything on this page.

No paid tier

No feature gates, no licence keys and no limit on the number of people or projects.

Yours to run

Your issues stay in your PostgreSQL, on your cluster, including networks with no internet access.

Built in the open

Read the code, report issues and send pull requests on GitHub. The contributor guide covers building, testing and the local cluster.

Run it on your own infrastructure

The docs cover installation, configuration and every feature. Moving from Jira? The importer brings your projects across with their history.