Skip to content

OpenAsset ITAM: IT Asset Management Software

By Bikram Bhujel

Software case study · October 2026

OpenAsset ITAM: IT Asset Management I Built from Monthly IT Work

An IT asset management application for the work IT teams do every month: inventory, assignments, depreciation, chargeback and disposal with evidence. It runs offline on Windows and macOS, with an optional online edition for several users in a browser.

StackGo · Wails · React · SQLite · PostgreSQL
Version1.2.2 (October 2026)
EditionsWindows · macOS · online
TypePersonal project
Offline firstDesktop app with a local database; online edition optional
Audit trailEach entry chained to the last, so edits show
TestedAutomated tests on SQLite and PostgreSQL, CI builds, signed installer
01 · Why I built it

Asset work lives in spreadsheets until it doesn't.

Monthly IT asset work, from who has which laptop to what each department is charged and what was disposed of and how, usually lives in spreadsheets. They work until someone needs history, approvals or an audit trail.

OpenAsset is built around those monthly tasks rather than around a generic database.

02 · Features

Covering the full life of an asset.

01
Inventory and assignments

Assets, people, contracts, assignments and full history.

Core
02
Depreciation and chargeback

Calculated charges, with posted history that cannot be changed afterwards.

Finance
03
Disposal

Approvals and evidence for every disposed asset.

Lifecycle
04
Users and roles

A permission matrix, and an audit trail where each entry is chained to the last.

Control
05
Backup and restore

Encrypted backups in a documented file format.

Recovery
06
Import and reports

Validated CSV import, reports and a dashboard.

Data
03 · Editions

Desktop first, online when needed.

EditionHow it runsState
Windows desktopLocal database, signed installerReleased
Online editionSame app in a browser for several users, PostgreSQL, scripted upgrade and rollbackReleased
macOS desktopBuilt automatically by CIBuilt; final checklist open
04 · Engineering

Treated like software someone else will rely on.

TestsAutomated tests run on SQLite and, with a flag, on PostgreSQL.
BuildsGitHub Actions builds on each version tag.
SigningWindows installer signed with my own certificate authority, with a kit for machines that should trust it.
Data hygieneRepository rules keep staff data, backups, environment files and certificates out of version control.
ProceduresWritten procedures for onboarding, issue and return, exits, licences, disposal, month-end, access reviews, backups and upgrades.
05 · Lessons

What building it taught me.

01
Write the procedure with the feature.

A feature without a procedure gets used differently by every person.

02
History you cannot edit is a feature.

Posted charges and a chained audit trail make month-end disputes short.

03
Keep real data out of the repository from day one.

It is much harder to remove later.

Comments

Questions and corrections are welcome. I read every comment before it appears, and remove spam and promotional links.