If it happened to your hardware, it's in here. Forever.

lazyit is the system of record for the five-person team that runs everything — inventory, access, secrets, knowledge. Append-only history, soft-deletes, no telemetry, AGPL. Nothing quietly disappears.

docker compose up

Open source · self-host free · no account.

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.

LAZYIT · ASSET LEDGER#A001
#A001CREATEDlaptop · MacBook Pro 16"
#A001ASSIGNEDana.r
#A001RETURNEDoffboarding · wiped
#A001ASSIGNEDmarco.v
#A001ASSIGNEDjoaquin// the very first one

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

    It never phones home. No tracking, no per-seat billing. Your data lives on your servers and stays yours.

Don't take my word for it. Watch it work.

Two parts of the record, doing their job — no slideshow, no mockups.

Topology / production
DEPENDS_ONDEPENDS_ONMEMBER_OFDEPENDS_ONRUNS_ONlb-01web-prod-01web-prod-02db-primarycache-01
Blast radius — db-primary down ·2 dependents affected

When db-primary dies, you already know what dies with it.

lazyit-agent — install
root@lazyit-agent:~#curl -fsSL https://lazyit.acme.co/install.sh | sh -s -- --token lzit_sa_…
Detecting platformUbuntu 24.04 LTS · x86_64
Fetching collectorlazyit-agent 1.4.2
Installing servicesystemd · enabled
Registering hostlazyit.acme.co
Collecting facts142 facts
web-prod-01 reported 142 facts to lazyit

One line on a box, and it reports in. The inventory keeps itself honest.

Zero-knowledge. The server never holds the key — so it can't leak what it can't read.

Secrets are encrypted in your browser before they ever reach lazyit. What lands on the server is a shape it can't open: no master key, no back door, nothing an admin or a backup could ever hand over.

Stamped, not promised — check the source. It's AGPL.

How it works →
Vault / production

Production secrets

12 items · 4 members

Encrypted client-side
  • DATABASE_URL••••••••updated 2d ago
  • STRIPE_SECRET_KEY••••••••updated 5w ago
  • ZITADEL_SA_KEY••••••••rotated 14h ago
GitHubRotates every 30s

The server can never decrypt your secrets.

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.

Joaquín MinatelSolo founder, lazyitjminatel.dev

Put it on the record.

One command, on your own servers. No account, no trial, no telemetry.

docker compose up
Watch the 2-min tour →