References — Iterus's Own Products
Iterus has no client references — everything here is our own product, which we scoped, built and paid for ourselves. Three products have a case study with the architecture, numbers from the repository and what the human did versus the AI — two live, one pre-launch; projects still in progress get one sentence about what they are built on.
Case studies
Innea
live
Czech AI support between therapy sessions — text and voice chat, mood tracking and a crisis layer that points to the 116 123 helpline.
Innea Pro
live
Practice operations for Czech therapists on the same core as Innea — self-booking calendar, AI session notes, invoicing under Czech rules and health-insurer billing documents.
Legacy You
pre-launch
A platform for leaving messages to loved ones, designed senior-first: voice control, large touch targets and passwordless sign-in.
What we're working on
Iterus Platform
in development
An autonomous Claude Code orchestrator — reads tasks, runs Claude headless, runs tests and commits, until the task is done.
STAMIQ
pre-launch
Adaptive endurance training plans — Garmin Training and Health APIs, with plans recalculated from HRV and sleep.
Koordinační kalendář
in development
A coordination calendar for field-service operations — multi-tenant on PostgreSQL with row-level data isolation.
NT8-Optimizer
in development
Strategy optimisation for NinjaTrader 8 — NinjaScript in C# bridged over ZeroMQ to evaluation in Python.
GEO-SEO
in development
Measures how often AI engines mention a brand against its competitors — every number with a 95% Wilson confidence interval.
gaits
in development
A Garmin wearable app: raw 25 Hz inertial capture and machine classification of a horse's gaits.
The specific services we'd use for your project are on the Services page; how the collaboration works is on the How we work page.
Frequently asked questions
Why are there no client logos?
Because we have no client references — everything here is our own product, which we scoped, built and paid for ourselves. Instead of logos we show what other studios cannot because of NDAs: the architecture, the test and migration counts and the integrations used, straight from the repository in every case study.
Can we see the code?
We don't publish the source code of our own products. We're happy to go through the architecture, test coverage and integrations on a call, though — and on your project the code is yours on payment, so the question doesn't arise there.
Is the project finished, or still in progress?
The status is written on every project — live, pre-launch or in development — and a case study puts it in numbers: what is tested and deployed, not what is planned. For an unlaunched product we promise no launch date; we say what the launch is waiting for.