Live today
Browser voice over WebRTC and the native app open the same realtime session — the same pipeline, processors, and flags. Telephony is built and key-gated; it is not carrying production phone calls, and nothing here should be read as saying otherwise.
Live
Read every entry
Each entry carries its current status instead of a release date. No dated log was kept, and no date is better than an invented one.
Read the entriesA capability that is built but key-gated is not live. Telephony is that case, and it is written down that way.
See safetySpeech and language models come from vendors. What we build is the Korean turn-taking, the orchestration, and the reliability layer.
See the platform
Everything that reaches production passes one human gate. Nothing lands on a live call path on an automated approval alone.
Contact the teamThe implementation state, written down as it stands. Every entry rests on something countable in the repository, and live, built, in progress, and platform are not mixed.
10 entries
WebRTC carries a complete realtime voice session in the browser. It is the same pipeline, processors, and flags the mobile app runs, so a change to turn-taking or failover is not a per-surface fork.
iOS and Android open the same realtime pipeline. A flag flipped for the call is a flag flipped for the pipeline — web and mobile do not keep separate copies.
Backchannel handling sits on voice-activity detection, so a listening 네 or 음 does not count as handing the turn back. Greetings are pre-synthesized at startup, so the first audio does not wait on a model round-trip.
PII redaction runs as an inline processor during the call, not as a batch job afterwards. What the operations layer sees is already redacted and speaker-attributed.
The telephony architecture exists, but it is key-gated. It is not handling production phone calls today, and it is listed here as built, not as shipped. Integration is per deployment.
Records, schedules, and notification screens are finished. The backend integration behind them is not. It is marked in progress rather than written up as done.
If a synthesis vendor stops responding mid-call, the pipeline switches to another and stays there for the rest of that call instead of flapping. When a tool call runs long, Korean filler audio covers the wait.
Each flag is a component that can be turned down without taking the rest of the call with it. Degrading is the designed outcome, not an accident.
We do not assume something upstream already checked. Every public function authenticates the caller in its own body, and a test proves it.
IntuneLabs holds no security or privacy certification, and this site claims none. Where a control exists it is described as what it does, not as an audited standard.
There are no release dates in this list. No dated release log was kept for these milestones, and we would rather show no date than invent one.
Whether each of the four areas is live, key-gated, or still integrating.
A realtime pipeline tuned for Korean conversation
Turn-taking, backchannel handling, Korean text normalization, redaction, and guardrails all run in one pass.
Web and mobile read from the same pipeline
A flag flipped for one is a flag flipped for the pipeline, not a per-surface fork.
Everything after the call finishes on one screen
Where redacted records, risk signals, and per-call timings are reviewed. Those timings are for operations; they are not published as benchmarks.
The architecture is ready and still closed
The telephony modules are built and key-gated. They are not handling production phone calls.
UI complete, backend integration in progress
The records, schedules, and notification screens are finished; the backend integration behind them is not.
Degrade over crash, and one human gate
Flags and sticky failover keep the call alive, and the only gate to production is a person.
What is next
Live, built, and in progress are on this page. Direction of travel lives on the roadmap, labelled as intention rather than commitment. If a deployment needs a path that is still key-gated, that is a conversation, not a date.
Open the roadmap