Most AI waits
to be asked.
LIMEN is the interaction runtime for consumer AI: real-time voice, live perception, persistent memory, and shared context through one connect(). Built for products that need to understand what is happening now, remember what mattered before, and act at the right moment.
Everything an AI needs to feel present.
The hard real-time problems, already solved and on the wire. Compose them per session and toggle modalities turn by turn.
Voice
Barge-in capable, low-latency speech in English and Chinese. Pick a voice or bring your own model.
Perception
Screen, camera, and sensor understanding streamed frame-by-frame to the model.
Memory
Persistent, per-user recall across sessions and devices. Forget on command.
Context
Live state, tools, and identity injected into every turn. One shared world model.
One session. Every modality.
A single real-time connection carries audio, frames, and context both ways. You decide which senses are live at each turn.
Open a session
Authenticate and call connect(). LIMEN negotiates a low-latency transport to the nearest edge.
Stream the senses
Push mic audio and screen or camera frames over a single WebRTC channel, no pipeline to build.
Toggle modalities
Flip voice, perception, and memory on or off per request as the interaction changes.
Ship the presence
Receive transcripts, intents, and synthesized speech. Your AI is present.
An SDK,
not a pipeline.
- Open a session, stream audio and frames over WebRTC.
- Toggle voice, perception, and memory per request.
- Managed cloud runtime, deployed close to your users. Your model or ours.
- Events for speech, intent, and perception, fully typed.
// the web SDK is built and documented.
Want early access? Request it below.
import { Limen } from "@limen/sdk";
// one session: voice, perception, memory, context on the wire
const session = await Limen.connect({
presence: "nova",
language: "auto", // EN + ZH, routed per turn
});
// turn senses on per turn
session.startPerception("screen");
session.on("speech", (turn) => {
console.log(turn.text); // low-latency, streamed
});One layer. Every kind of product.
The web SDK ships today, extracted from the product below. The same provider-pluggable stack is built to adapt to each device class as those SDKs land, from battery-bound wearables to always-on desktop agents.
Sidekick AI — the proving ground
LIMEN packages the real-time stack behind Sidekick AI, our own AI gaming companion live on Steam. Real-time voice, screen perception, and per-user memory were built and hardened there first — against real players, in long sessions, under constant interruption — then pulled out as infrastructure.
Wearables & earbuds
Low-latency voice with on-device wake and barge-in, tuned for low-power radios and intermittent connectivity.
Companion robots
Fuse camera, depth, and audio into a shared world model so the robot perceives the room and remembers who it's with.
Desktop agents
Stream the screen frame-by-frame so the agent sees what the user sees, then acts with full context and tools.
Voice toys & kiosks
Drop-in conversational presence with a chosen voice, persistent per-user memory, and per-modality consent built in.
Real-time senses, handled responsibly.
Voice, screen capture, and sensor data are sensitive by nature. LIMEN is built so you can give your AI presence without giving up control of what it perceives or remembers.
Formal certification (SOC 2, GDPR, HIPAA) is on the pilot roadmap, not yet audited. We say what is true today.
Encrypted in transit
Every session stream is encrypted in transit over DTLS-SRTP and TLS 1.3.
Scoped consent
Per-modality permissions and clear in-session indicators when senses are live.
Memory you control
Inspect, export, or forget per-user memory on command. Nothing is sticky by default.
Residency you choose
Pick the region a session runs in and where its memory lives, so sensitive data stays where your market requires.
Before you start building.
What exactly does LIMEN provide?
Do I bring my own model, or use yours?
Which device classes are supported?
How is sensitive data handled?
Can I try it before it's generally available?
Ship presence,
not plumbing.
We're onboarding early-access design partners now. Join the waitlist to build against the web SDK before general availability.