GadgetCloud
Sign in

Every gadget your company owns, on one record.

GadgetCloud manages the full life of enterprise hardware — from the purchase order to disposal — so you always know what you own, who is holding it, and what is still under warranty.

Sign in

Building now, in the open. Tell us how your hardware moves and it shapes what ships next.

The gadget lifecycle A record moves continuously through eight stages: procure, receive, assign, operate, service, recover, retire, dispose — then round again. ProcureReceiveAssignOperateServiceRecoverRetireDispose ONE RECORD per gadget MBP-014 ProcureReceiveAssignOperateServiceRecoverRetireDispose

The spreadsheet is accurate for about a week.

Most teams track hardware in a sheet that is correct the day it is written. Then a laptop changes hands, a phone is replaced under warranty, three tablets go into a drawer, and the sheet quietly becomes fiction. The cost shows up later — at audit, at renewal, or when someone leaves and nobody knows what to collect.

hardware-tracker.xlsx
AssetOwnerStatus
MBP-014 Ana Iyerleft in March In useunreturned
IPH-221 Supportswapped, not logged In usereplaced under warranty
TAB-045 Field teamin a drawer In useidle since June
MBP-097 D. Raonow on loan Repairreturned in May
Nobody edited this sheet incorrectly. It simply stopped being asked, while the hardware carried on moving.

Eight stages, one record per gadget.

Nothing is re-keyed between stages. The gadget carries its own history from purchase order to disposal.

Stages 01–02

Procure and receive

Record the purchase once: supplier, invoice, serial, cost and warranty term. Check it in with condition photos. The receipt stays attached to the gadget rather than in someone’s inbox.

Stages 03–04

Assign and operate

Give it an owner — a person or a team. A handover is a change of owner on the same record, not a new row in a new sheet.

Stages 05–06

Service and recover

Repairs route out and come back onto the same record. At offboarding the gadget is collected and its condition noted, so nothing walks out of the door unrecorded.

Stages 07–08

Retire and dispose

Close the loop: withdrawn from service, then resold, recycled or written off — with the date, the reason and the proof kept for the audit that asks about it later.

What one record holds.

Everything about a gadget lives in one place, including the evidence.

MBP-014 In warranty · 214 days left
Owner
Design team
Serial
C02X1234JGH7
Purchased
14 Mar 2026 · ₹1,84,000
Warranty term
36 months from purchase
Attached
Invoice, serial photo
Nobody keeps that badge up to date. It is worked out from the purchase date and the term every time the record is read.

Built on three rules.

Three decisions the whole system is held to, not features that can be switched off.

Rule 01

One owner, always

A gadget belongs to a person or to a team, never to both and never to neither. The rule is enforced in the database, so ownership cannot drift into ambiguity.

Rule 02

Warranty you can trust

Status is derived at the moment you read it. There is no nightly job to fall behind and no field to forget to update.

Rule 03

Proof attached

Invoices, serial-plate photos and condition shots upload straight onto the gadget, so the evidence lives with the asset it belongs to.

It is not a mockup. It is running.

The fleet dashboard, the gadget register, the audit history and the permission controls are built and deployed. This is what signing in looks like today.

Fleet DashboardGadgetsPeopleActivity
Gadgets 1,284
Need attention 81
Open repairs 115
Out of warranty 63
In service 902
In stock 210
Under repair 104
Awaiting parts 41
Retired 27
The fleet dashboard, as it renders today. Warranty is worked out at the moment you read it, so the figure above is never a cached number waiting to go stale.

What procurement asks before anything else.

Four questions decide whether a tool gets through review. Here are the answers, and where each one is enforced.

Can another company see our data?

No, and not because the code remembers to filter. Isolation is enforced by PostgreSQL row-level security: a query that forgets which organisation it is for returns nothing, rather than everything.

Where does our data live?

India. Every service runs in AWS Mumbai (ap-south-1), and nothing crosses a border — no replica, no backup, no analytics pipeline in another region.

What happens to our passwords?

There are none. Sign-in is a one-time email code or your own identity provider, so there is no password for us to store, leak or be asked about in a security review.

Can someone quietly change history?

No. The audit log is append-only in the database itself — update and delete are revoked, for every account including ours. What was recorded stays recorded.

Know what you own, before someone asks.

We are building GadgetCloud now and shaping it around what enterprise teams actually track. Tell us how your hardware moves and what breaks down today.

Sign in