5
Ventures
One engine + four services that prove it.
JTTL builds Klok Integration — an engine for information supply — and runs its own services on it. QuickRace runs in this company. Barnbok runs on the same engine. That is how we know it holds.
A software company is strongest when it runs what it builds.
We believe infrastructure should not be an abstraction you buy and hope for — it should be something you understand. That is why every flow is built with clear data contracts, standardized patterns and open observability. Intelligible from day one.
We run our own services on the engine we build. QuickRace runs in JTTL. Barnbok runs on the same engine. quick.tickets sells tickets for organizers on it. Badväder takes Copernicus’s large weather datasets through ingestion, transformation and API. They are not side projects — they are proof. Every customer flow we then set up runs on proven, in-house technology.
We eat our own dog food — on purpose.
It forces us to build for reality, not demos. Models shipped to production, documentation generated automatically, information dependencies analysed before they become problems — we do all of that for ourselves first, then for our customers.
The core: curiosity and a serious ambition to show what well-built infrastructure can actually carry. Credibility does not come from what we say — it comes from what we run every day.
A well-oiled engine for information supply. We combine clear data contracts, standardized integration patterns and observability so every flow is intelligible from day one — with our own AI services on klok.ai. QuickRace and Barnbok run here. quick.tickets is built here. Badväder takes Copernicus’s large weather datasets through ingestion, transformation and API. That is how we know the engine holds, before a customer flow does.
A service JTTL co-owns — built and run on the Klok engine. Every book created, every flow that runs, is also proof that Klok’s infrastructure carries a product in live operation, around the clock.
JTTL’s own service — AI race timing. Designed to show how Klok’s infrastructure handles hard requirements: real-time data, computer vision on bib numbers and scalable public flows at the race’s actual traffic peak.
JTTL’s own service — and a production proof. The organizer gets a ticket shop of their own and double exposure for every event: quick.tickets internationally and biljett.shop on the Swedish market. One event, two markets, and an address of their own such as theclub.quick.tickets. The buyer needs no app. At the gate, check-in stays fast even when there is no network. The money goes straight to the organizer, and every event gets an AI colleague that answers the questions the organizer would otherwise answer themselves.
JTTL’s own service — and a production proof. Large open datasets from Copernicus, the EU’s weather data, become a small service: coastal water temperature, ice cover for skating in the archipelago in winter. All of Klok’s ingestion, transformation and API are used. A web page and app for people. MCP so AI — Claude, ChatGPT and others — can connect to the swimming-weather information. An API so other apps can carry the same info.
You can see Barnbok, QuickRace, quick.tickets and Badväder as four products. We see them as something else, and more important: hard tests of Klok. QuickRace runs in JTTL. Barnbok runs on the same engine. quick.tickets carries ticket purchases, payments and the gate. Badväder takes Copernicus’s large weather datasets through ingestion, transformation and API. Real load — real users, real flows, real response times.
When we then set up a flow for a customer, it is not theoretical. It runs on the same engine we ourselves depend on every day.
WHAT HAPPENS WHEN YOU RUN ON THE ENGINE
Clear contracts first. Data contracts are defined before code is written — every party knows what flows.
Standard patterns. Every integration follows proven patterns, not unique solutions nobody understands.
AI as a workhorse. Documentation is generated, information dependencies are analysed — automatically.
Intelligible from day one. Observability in every corner. No black boxes, no magic, just systems you can follow.
Klok Integration is run jointly by JTTL AB and integrera.com. Exact ownership is handled in each company’s articles.
We build information flows that are intelligible from day one — and we prove it by running them ourselves. Talk to us about how Klok can carry your operation.
JTTL AB · Just Think, Then Launch