A role
- ops assistant
- analyst
- researcher
You hire it for a specific job, not for small talk.
Summit · the start
It works on your machine — not in someone else's cloud. Meetings recorded with no bot on the call. AI that runs locally. A price that never moves.
Luge, a product of N Solutions. Built in Québec. Already in production at its first vertical customer: Tchat N Sign (financial services) — an organization certified SOC 2 Type II, ISO 27001 and ISO 27701.
In short
Luge is an AI employee that works on your machine: meetings recorded with no bot joining the call, open-source models running locally or on managed Canadian infrastructure, team memory that improves with use without retraining — at a flat price, never per token. Free on Solo with your own AI; built in Québec by N Solutions.
Turn 1 · the idea
Luge isn't a tool you invoke — it's a colleague you onboard. You don't prompt it, you give it a job: like an intern who never forgets, never sleeps, and actually reads every document you hand over.
You hire it for a specific job, not for small talk.
It remembers last week — and gets better each run.
Give it a goal, not a script. It escalates when it should.
After every task, Luge extracts what it learned and keeps it. No fine-tuning, no magic: well-architected memory. The employee you have in January isn't the one you have in June.
The essentials live in a notebook with a hard budget. When it's full, something has to go — that's what keeps it reliable. Try it:
Core memory — the little notebook
Team knowledge is cited like a proper report — human and AI, never conflated.
“Client Tremblay always wants his documents as PDFs.”
“The weekly report takes 4 minutes on the local model.”
A future reader will never see an AI statement quoted as a human one. Because you stay accountable for your advice — not your AI.
While you sleep
Every night, its memory reorganizes itself: duplicates merge, contradictions get resolved, and a personal memory that leaked into the shared pool returns to your private drawer on its own. It reorganizes — it never invents. The curious can read how it actually works.
Team memory
Private drawer
Turn 2 · the install
No terminal, no VPS, no tokens to paste into config files. A signed installer, a two-click device pairing in your browser, and a guided onboarding in the app. We love DIY agent projects — we compare a few of them here, respectfully — but your evening is yours.
Turn 3 · meetings
Everyone has seen "a bot has joined the meeting" and felt the room stiffen. Luge detects Meet, Teams, Zoom, Webex or Jitsi and records locally on your machine — nothing joins the call, nothing shows in the participant list. Then: transcript, summary, action items. Details here.
Recording a conversation is still your responsibility: tell the participants. Your device, your rules, your jurisdiction.
Night · your data sleeps here
Small, fast open models (Qwen, Ornith — GGUF via llama.cpp) handle the office work: not frontier magic, reliable work. Transcription happens on-device. Your secrets stay in 1Password. Your files, your audio, your keys: processed on your device. The curious get a local models guide, skeptics can go read under the hood.
Processed on your device. Full stop.
Always your choice, never a hidden default.
Turn 4 · the bill
Per-token billing is a taxi meter: one busy month and the bill explodes. Luge inverts it: small models, orchestrated into workflows where every step is short, scoped and verifiable. The result — predictable costs, and an AI that hallucinates a lot less, because it never improvises in one giant blob.
±42 % month-to-month swing, billed per token
0 % surprise — small models, scoped workflows, flat price
Turn 5 · your AI
We provide the table, the service and the menu — the bottle is yours. Plug in your Anthropic, OpenAI or Azure key, point at your vLLM server, or download a local model right in the app. No key at all? Run 100% local. That's the Solo plan: free, because your machine does the work.
Turn 6 · the day job
Email, calendars, tickets, CRM, code repos: your AI employee plugs in where the team already works, runs its scheduled tasks, reads your documentation (hand it the binder — it reads the whole binder), and codes in an isolated sandbox.
21 native integrations + 22 platform modules via MCP — plus an OpenAI-compatible API to wire up the rest.
Last turn · what's next
Finish line
The product moves fast — the changelog is public, the distribution repo is on GitHub, and the orchestration foundation, RoomKit, is open source.