A small lab for the grey areas between tools.
Limbus Lab is a focused engineering studio created to solve problems sitting in the grey area between tools, teams, and workflows. Today that work is Hooq: it keeps work in sync between two instances, with nothing in the middle.
- 2024
- Founded
- Hooq for Jira
- On the Atlassian Marketplace
- Hooq for ServiceNow
- In preview
Why this exists.
Founder, Limbus Lab
We started Limbus Lab because we kept running into the same pattern: teams struggling with problems that lived between tools — not quite big enough for a vendor solution, but painful enough to slow everything down.
The gap between "we need this" and "someone will build this" is where most productivity quietly bleeds out. People build workarounds. They copy data between spreadsheets. They write the same update in three places. They accept friction as normal.
We didn't want to build another platform that promises to change everything. We wanted to build small, specific tools that solve one problem well — and then get out of the way.
That's what Limbus Lab is. We build practical software. We focus on the problem, not the pitch. We keep things simple because simple things actually get used.
Every product we ship starts the same way: someone on a team somewhere is frustrated by something that should be easier. If we can make it easier, we build it. If we can't do it well, we don't do it at all.
There's no grand vision here. Just good engineering applied to real problems, one tool at a time.
Four commitments we hold ourselves to.
Engineering first.
We lead with engineering, not sales. Every decision starts with what makes the software better. The roadmap is shaped by what users hit, not what marketing wants to announce.
User-centred.
We build for the people who use the tools every day, not the people who approve the purchase.
Nothing in the middle.
Hooq has no server of its own. Your work goes straight from one instance to the other, and stays on the platforms you already use.
Ship & iterate.
We ship working software early and improve based on real usage, not assumptions. Every release ends with a question: did this make someone's day easier? If not, we go back.
How we make decisions when something is unclear.
If we can help, we will.
Questions about Hooq, a problem to report, or something you would like it to do? Tell us.
Get in touch