Contact
Menu

First product: issue tracking for software and IT teams, in development

Great software, radically cheaper.

Most companies rent their business software by the seat, every month, for as long as they exist. We’re building open‑source replacements for those tools. Nobody will be moved over until the new one passes the checks agreed with their team.

Tell us about your tool How we build
issue-tracking.specexample

  1. Anyone on the team can open an issue with just a title.

    Test

  2. Every imported issue keeps its number, history and attachments, and the counts match the old system exactly.

    Reconcile

  3. The Monday report matches the one finance uses today, line for line.

    Sign-off: finance lead

  4. Dragging a card across the board feels as quick as it does now.

    Sign-off: the team
An example we wrote for this page, not a customer’s spec.

We’ll start by writing down what your software actually does.

A migration can fail on the details nobody wrote down: the report finance quietly depends on, the permission one manager asked for years ago, the reminder that goes out when a ticket sits too long.

So before we build anything, we’ll write a spec like the one above with the people who use the tool, and give every line a way to prove it. You correct it until it’s right. Then it’s the definition of done.

Test
Runs by itself, every time anything changes.
Reconcile
Compares your old data with the new, record by record.
Sign-off
A named person on your team says yes. For the things a machine can’t judge.

How a switch will work

  1. We map how your team uses the tool

    We sit with the people who use it and write down what they actually do. You correct it.

    With you

  2. You get the numbers in writing

    Whether we can replace it, and the full cost after: hosting, moving your data and our fee, which will come out of what you save. If the numbers don’t work, we say so and stop.

    You decide

  3. We build until every line passes

    A person reviews every change before it counts.

    Us

  4. You pick the day you switch

    Your data is moved and reconciled first, and the old tool stays until you’re sure.

    You decide

Why we started Tenseon

Per-seat pricing made sense when software was expensive to build and to run. AI is making it much cheaper to build, and we think the price should follow.

We also think you should be able to leave: read the code your business runs on, run it without us, and take your data with you. That’s why the core will be open source, under Apache 2.0.

The catch is that AI writes plenty of code quickly and proves none of it. Written checks, and people who put their names to them, are what make it safe to switch.

Open source How we build