No rollup
Six boards, no picture
Every team has a board. Nobody has the view across them — so “are we on track” gets assembled by hand, in a spreadsheet, the night before the steering committee.
Self-hosted · free for one teamSee across every team
See across every team
on Jira.
Flow metrics, commitment accuracy and the cross-team rollup Jira never gives you — running on your own servers, reading the Jira you already have.
No account neededYour data never leaves your networkDeploy in an afternoon
Program health · PI 24.3
Delivered
82%
▲ 6 ptsCommitted
94
on planSpillover
18%
▲ 11 ptsCycle time
9.4d
▲ 2.1 dCommitted vs deliveredlast 7 sprints
S1
S2
S3
S4
S5
S6
S7
Predictability by team
Navigator91%
Beacon74%
Harbour38%
Meridian86%
Jira records what happened. It won't tell you what's coming.
History drifts
What did we actually commit to?
Sprint scope changes and Jira quietly forgets. Without replaying the changelog, commitment versus delivered is a story people tell, not a number you can check.
No flow
Cycle time lives in a spreadsheet
Flow efficiency, queue time, rework, spillover — all computable from data you already have, none of it where the decisions actually get made.
Each view answers one question somebody keeps asking you.
cross-team-rollup.png
Cross-team rollup
Which team is in trouble right now?
commitment.png
Commitment accuracy
What did we promise versus deliver?
flow-metrics.png
Flow metrics
Where does work actually sit and wait?
compliance.png
Compliance & risk
What's blocked, stale, or unowned?
pi-planning.png
PI planning
Does the plan survive contact with capacity?
backlog-health.png
Backlog health
What's unsized, orphaned, or rotting?
Live demo
Open the demoA full instance on a real portfolio. Nothing to install.
Every chart populated with a programme that has genuine problems in it — because a demo where everything is green proves nothing.
Nowhere.
That's the point.
Tekio Delivery runs as a container inside your own network and talks to your Jira directly. Your issues, your changelogs and your metrics never reach us.
Which also means there's no data processing agreement to negotiate, no sub-processor register, and nothing for your security team to review beyond the image itself.
Runs on your infrastructure
Docker, on your server or your cloud
Read-only Jira access
An API token is enough; it writes nothing
Token encrypted at rest
Stored on your box, never transmitted
No GDPR processor relationship
We never receive your data
No telemetry
The free tier phones nobody
Free for one team. Paid when a programme runs several.
A Scrum or Kanban project tracks one team, and that's free for good. SAFe mode — several teams on one programme — is what the licence unlocks, priced on how many teams you actually run.
Free
€0
forever · one team
- One Scrum or Kanban project
- Flow, commitment, compliance
- Sprint reports and PDF export
- No time limit, no nag screens
Starter
€4 900
per year · up to 5 teams
- SAFe mode · up to 5 teams
- Cross-team rollup
- Role-based access and SSO
- Source code included
Most orgs
Growth
€9 900
per year · up to 15 teams
- Up to 15 teams — a full ART
- PI planning, planning board, ART sync
- Forecasting and cross-PI trends
- Source code included
Scale
Let's talk
beyond 15 teams
- Several ARTs, no team limit
- Portfolio module
- Priority on feature development
- Source code included
Source code included on every paid licence. Read it, modify it, extend it, adapt it to your own Jira — internal use, for as long as you like. You may not redistribute or resell it, or run it as a service for anyone else. So if I'm ever hit by a bus, you still own your tooling.
Or have it landed for you
Installed, connected to your Jira, field mapping validated on your own data, and a metric design workshop with your delivery leads — so it arrives configured and your team already knows what the numbers mean. Licence for the first 12 months included.
€19 000See what's included
Who built this
I'm Florian Grassot. Twenty years building software, ten transforming how organisations deliver it — around 600 people coached, at Airbus, Thales and Marlink.
I built Tekio Delivery because every engagement started the same way: three weeks of interviews to work out what was actually happening, when the answer was already sitting in Jira. Now I plug it in and we look at real data on day two.
If you'd rather have it implemented and your metrics designed than install it yourself, that's what I do for a living.
Point it at your Jira and see for yourself.
The image isn't published yet. Leave an email and you'll get it the day it is — a confirmation now, one email then, nothing else.