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.
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.
Building now, in the open. Tell us how your hardware moves and it shapes what ships next.
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.
| Asset | Owner | Status |
|---|---|---|
| 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 |
Nothing is re-keyed between stages. The gadget carries its own history from purchase order to disposal.
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.
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.
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.
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.
Everything about a gadget lives in one place, including the evidence.
Three decisions the whole system is held to, not features that can be switched off.
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.
Status is derived at the moment you read it. There is no nightly job to fall behind and no field to forget to update.
Invoices, serial-plate photos and condition shots upload straight onto the gadget, so the evidence lives with the asset it belongs to.
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.
Four questions decide whether a tool gets through review. Here are the answers, and where each one is enforced.
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.
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.
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.
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.
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.