An AI co-pilot for your IT operations.
One platform for tickets, assets, contracts, licenses, and employees. The agent classifies, drafts, and surfaces past fixes — your team reviews and signs off.
free workspace · no credit card · bring your own LLM key
From: priya.shah@acme.co
Outlook search returns no results after Windows update
Matched KB-0094 “Rebuild Outlook search index”. Drafted reply with the 3-step fix and a rollback note. Awaiting your review →
They sell you three tools.
We built one platform.
Most IT teams stitch together a ticketing system, an asset spreadsheet, and a contracts folder — then pay a consultant to make them talk. Lumzi has one data model: tickets link to assets, assets link to contracts, contracts link to people. No reconciling. No "which tool was that in?"
Every quarter you discover another row in the asset sheet that nobody owns, another contract auto-renewed, another laptop you can't find. The system that was meant to give you control just told you about it three months late.
| Dimension | Legacy stack | Lumzi |
|---|---|---|
| System of record | A ticket tool + an asset sheet + a contracts folder | One data model: tickets ↔ assets ↔ contracts ↔ people |
| AI model | Bolted onto a pre-AI ticketing core | Co-pilot built into every surface |
| Human oversight | Auto-replies fire without review | Drafts queue — a human signs off on every send |
| AI inference cost | Marked up per token, opaque on the invoice | Bring your own LLM key · zero markup |
| Time to first value | 3–12 month implementation | First AI-assisted ticket in under an hour |
| Audit trail | Per-tool, irreconcilable across ITSM and ITAM | One signed log across the whole platform |
| Multi-tenant | Single instance per customer · heavy ops | acme.lumzi.io · isolated by default · fleet-ready for MSPs |
The agent drafts.
Your team decides.
Not a chatbot bolted onto a ticket form, and not autonomy without oversight. Lumzi runs inside your service desk: classifies new tickets, drafts replies from past resolutions, links assets and contracts, and proposes KB articles — all in a queue your team approves before anything ships.
Inbound via web form, email, Slack DM, or M365 Teams capture.
→ INC-04221 “OneDrive sync paused”
Pre-classified, draft response ready, asset + contract linked, KB-0094 surfaced.
Tech accepts, edits, or rejects. Audit log captures the decision.
→ sent · KB promoted · ticket resolved
01 · Classify
Every new ticket lands pre-tagged with type, priority, and team. Your tech accepts or adjusts in a click. Less morning queue-grooming, same human in control.
02 · Suggest
On every open ticket, the agent surfaces the matching KB article, similar past resolutions, and a draft reply. Your tech reviews, edits, and sends. Nothing leaves the queue without a human signing off.
03 · Learn
Every resolved ticket teaches the agent. It drafts new KB articles when a recurring issue surfaces and improves existing ones when better fixes appear. Drafts stay in a queue until your team publishes them.
One system of record.
Every module already talking to every other.
A ticket about a laptop knows which contract that laptop is on. A leaver workflow knows which licenses to reclaim and which assets to recover. The data graph is the product.
Service desk
Incidents, requests, problems, changes — one ticket model, one queue, one SLA engine.
Knowledge base
Articles auto-promoted from resolved tickets; the agent matches new tickets to past fixes.
Asset register
Devices, peripherals, accessories. Tags, photos, depreciation, custody chain.
Contracts
Renewals, cancellations, amendments. Linked to assets, licenses, and the vendor record.
Software licenses
Seat allocation per employee or device. Over-allocation alerts. License-key encryption.
Employees & teams
Directory, departments, joiners and leavers. Right-to-erasure baked in.
Self-service portal
End users open requests, track them, attach files. No login? No problem — magic links.
Workflows
Joiner / mover / leaver flows that route across modules. Built in the visual editor.
Built for the IT team that's tired of waiting on the platform team.
Series-B biotech
180 employees · multi-site
“We replaced our legacy ITSM stack, an asset spreadsheet, and a contracts folder with Lumzi in a Tuesday morning. The agent already knows our environment by Friday because it's reading from one data model, not three. We stopped paying $48k/yr in seat licenses and got better answers.”
Live in under an hour.
Not six months of “discovery.”
Sign up
Pick a workspace slug. Free plan, no credit card. Land on your dashboard with a default tenant and admin user already wired up.
Connect M365
Paste your Entra ID app credentials in Settings → SSO. Employee directory syncs every 6h. Add your SMTP details for ticket emails.
Drop in your AI key
Paste your LLM provider API key in Settings → AI. The agent starts triaging incoming tickets, drafting replies, and matching past resolutions immediately.
Import your assets
CSV import for assets, contracts, and licenses. Or wire the Intune integration for a one-way device sync. Tags auto-generate to your pattern.
The boring, important stuff.
Done right.
Security, isolation, auditability, and the disciplines your compliance team will ask about. Built into the platform, not bolted on for the deal review.
Encryption at rest
AES-256-GCMTenant secrets — SMTP passwords, license keys, integration tokens — are envelope-encrypted in the database. The platform owns the key; you never see ciphertext, the agent never sees plaintext.
Multi-tenant isolation
Prisma extensionTenant scoping enforced at the database client layer, not just route guards. Bypassing it requires explicit SUPER_ADMIN context — the surface area for a leak is one file, audited.
Audit log
Every writeEvery create / update / delete writes to AuditLog with actor, IP, action enum, and diff. Global viewer at /audit. No silent mutations — the agent’s writes show up the same way a human’s do.
GDPR right-to-erasure
Soft-delete + scrubEmployee records support a structured erasure: PII fields scrubbed, the row kept with a placeholder for referential integrity. Built in from day one, not bolted on for compliance.
Pricing clarity
No token markupYou bring your own LLM provider key. The inference bill stays on your contract. Lumzi never marks up tokens — when AI gets cheaper, your cost falls immediately.
MSP-ready
Fleet of workspacesOne <slug>.lumzi.io per customer, isolated by default. MSPs can manage many workspaces from a central platform admin without ever crossing tenant boundaries.
Ready to stop stitching tools together?
Sign up free. Wire up M365 and your LLM key. Watch the agent triage its first ticket. All before lunch.
free workspace · no credit card · cancel any time