Self-hosted IT asset & access management
If it happened to your hardware, it's in here. Forever.
lazyit is the system of record for the 5–20 people who run all of a company's IT. Append-only history, an AI that asks before it acts, no identity provider to babysit, CSV export on nearly every list. AGPL, no telemetry.
git clone https://github.com/joacominatel/lazyit && cd lazyit./infra/start.sh- AGPL-3.0
- Self-hosted
- No telemetry
- v3.0.0 · released Oct 17, 2026


One asset. Its whole life, on the record.
Every line is an event that actually happened — created, assigned, returned, reassigned. Append-only, top to bottom. You can read off exactly who had what, and when, without trusting anyone's memory.
Spreadsheets lie by omission. Ledgers don't.
What can't disappear.
Three properties baked into the data model — not settings you remember to switch on.
Append-only
Every change is a new line, never an edit in place. The past stays exactly as it happened.
Soft-delete
Retire isn't erase. Offboard a person, decommission a laptop — the record stays on file.
No telemetry
No tracking, no per-seat billing. Nothing leaves your servers unless you switch it on — AI is off by default, and it can run on a model you host.
An AI that asks before it acts.
Ask it which laptops are unassigned in Madrid, or tell it to give Ana VPN access. It reads with your permissions, every change it wants lands on a card you approve, and then on a log nobody can edit.
Your permissions. Not one more.
It acts as you, through the same server checks as a click in the app. Viewers get no AI by default.
Off until you switch it on.
The assistant, MCP, web search and document extraction each have their own switch. Turning the assistant on takes a passing connection test and a data notice you acknowledge, on the record.
Pick the model. Or host it.
Anthropic, OpenAI, Gemini, or any OpenAI-compatible server. Point it at Ollama or vLLM on your LAN and the chat never leaves the building.
Claude Code, over MCP.
An MCP server and a Claude Code plugin. Your client brings its own model; lazyit runs none. OAuth on HTTPS, expiring personal tokens on a plain-HTTP LAN.
Secrets stay out.
Secret Manager values, cleartext credentials and the AI's own settings never reach the model.
The fine print, on the record: you can let one chat auto-approve routine edits; roles, access, credentials and purchases still wait for you. Over MCP, your client decides when to ask.
How the assistant is fenced in →JMGive Ana Ruiz Admin access to VPN.
AIHere's the change. Nothing happens until you approve it.
Give Ana Ruiz Admin access to VPN.
Creates access in an outside system through an automation.
Don't take my word for it. Watch it work.
Five parts of the record, doing their job — real screens from a running instance, not diagrams.


Who had this laptop, and since when. Written once, never edited.
Every assignment, release and delivery lands in the asset's append-only activity log. There's no delete-assignment button: past owners move to the ownership history, dates intact.


The order says 113. The shelf says 38. The record says both.
Receiving a line creates the assets or stock it ordered, linked back to the purchase. The status follows what actually arrived: ordered, partially received, received.


Who can reach Okta, who let them in, and whose access runs out next.
Every grant names who gave it and when. Revoking ends a grant but never erases it: it moves to Revoked with who revoked it and when, and a grant past its expiry date is revoked on its own.


When db-primary dies, you already know what dies with it.
The map draws itself. The reporting agent checks in from Linux and Windows boxes, Docker containers appear under their host, and Proxmox, libvirt, XCP-ng or Hyper-V hosts list their guests — no agent inside each VM.


The server stores a shape it can't open. No master key, no back door.
Secret Manager values are encrypted in your browser with per-vault keys. The server stores only ciphertext.
Zero-knowledge. The server never holds the key — so it can't leak what it can't read.
Secret Manager values are encrypted in your browser, with per-vault keys, before they reach lazyit. The server stores only ciphertext: no master key, no back door, nothing an admin or a backup could hand over.
Stamped, not promised — check the source. It's AGPL.
How it works →Production secrets
12 items · 4 members
- DATABASE_URL••••••••
- STRIPE_SECRET_KEY••••••••
- S3_BACKUP_SECRET••••••••
The server can never decrypt these values.
What changed since 1.6.
Eight releases since this page last caught up. One line each, oldest first; the tag opens the full notes, warts included.
The importer grows up
Notes, cost and depreciation map on import, money parses in your locale, Snipe-IT statuses carry over.
AD/LDAP sync, read-only
People come in from your directory and nothing is written back. Per-app license seats, bulk receiving, warranty and access-expiry alerts.
The knowledge base becomes a reading room
Table of contents, backlinks, wiki-link previews, Mermaid, drag-and-drop .md import, a ⌘K switcher.
Windows agent, Docker on the map
The reporting agent runs on Windows as well as Linux, containers show up as child nodes, and the map shows blast radius.
Hypervisor guests
Proxmox, libvirt, XCP-ng and Hyper-V hosts report their VMs. One fleet view for every agent.
An AI assistant, and an MCP server
A chat that asks before it writes, MCP for Claude Code, a headless API. All off by default. 17 security findings closed, one of them disclosed in public.
Purchases
Suppliers and purchase orders; receiving a line creates the linked assets or stock. Drop in an invoice and lazyit drafts the purchase (off by default). Custom asset statuses, a webcam QR scanner.
No identity provider to run
The bundled identity provider is gone: built-in accounts by default, your own OIDC if you want it. CSV export on nearly every list, and the help desk can file an access request on someone's behalf. Deleting something in use asks one question instead of leaving orphans. An internal audit logged 105 findings; 104 are fixed and one is accepted as a known risk, with a boot warning.
Everything else is on the same record.
One system, one timeline. Here's the rest of what lives in it — read off the line you came for.
- InventoryEvery asset, with its whole history attached.
- Topology & reporting agentLinux and Windows agents report in; containers and hypervisor guests land on the map.
- PurchasesSuppliers and purchase orders. Receiving a line creates the assets, already linked.
- ConsumablesStock that warns you before it runs out.
- Applications & accessWho can reach what — granted, dated, revocable — and the seats you pay for.
- Access automationOffboarding, reviews and provisioning fire on grant and revoke.
- Knowledge baseRunbooks and docs, versioned beside the assets.
- Users & permissionsThree roles, least-privilege by default, full offboarding.
- AI assistant & MCPA chat that asks before it writes, and an MCP server for Claude Code.
- Global searchOne ⌘K spans every asset, person and runbook.
The boring part, on the record.
What you actually run, and how it comes up — no moving parts you didn't ask for.
- Stack
- Caddy · Next.js · NestJS · PostgreSQL · Valkey · MeilisearchA one-shot migrate step rides along, plus an optional daily backup sidecar. No identity provider in the box: sign-in is built in.
- Bootstrap
- One guided script: it detects your host, asks about six questions, writes real secrets, brings the stack up, and points you at /setup.
./infra/start.sh - Updates
- ./infra/update.sh vX.Y.ZTakes a verified database dump first, builds the new version while the old one keeps serving, then swaps. No dump, no update.
- Sign-in
- Built-in accounts by default, passwords kept as argon2id hashes. Or choose your own OIDC IdP (Entra ID, Okta, Keycloak) when you install; the installer asks. Nothing is written back to it.
- Directory
- Read-only AD/LDAP sync. People come in; nothing goes back.Directory sync →
- Export
- CSV on nearly every list, following your filters and permissions, and every export is logged. Leaving is a download, not a project.Exporting data →
- License
- AGPL-3.0 · single-org · no telemetry · nothing leaves unless you switch it on
I built lazyit because I was the IT team, and the spreadsheet was killing me.
No procurement, no committee — just one person tired of guessing who had which laptop. So I wrote down the thing I wished I'd had: a record that doesn't lie, on hardware I control.
It's built in the open and AGPL-licensed. If I disappear tomorrow, you still have the code and your data. You're never stranded.
Put it on the record.
Two commands and about six questions, on your own servers. No account, no trial, no telemetry.
git clone https://github.com/joacominatel/lazyit && cd lazyit./infra/start.sh