Lendra

Log who has which laptop, tool, or camera checked out, and get automatic overdue flags on a live dashboard.

The problem it solves

Every team that shares gear has the same quiet chaos: the good drill is missing, a laptop walked off after an event, and nobody remembers who took the projector. The "system" is a whiteboard, a clipboard, or a spreadsheet that's always out of date. Cloud asset-tracking SaaS solves it, but it's overkill: depreciation schedules, ticketing, per-seat pricing, and it puts your inventory on someone else's server for a monthly fee.

• No live record of who currently has what
• Nothing stops the same item being lent out twice
• Overdue items go unnoticed until someone has to ask around

Every feature

• A desk built around the scan. Scan or type a tag and the desk finds the item, tells you before you commit whether it can go out, and issues it. Returns are one click from the same screen. Any keyboard-style barcode scanner works; no driver, no app.
• Borrowers hear before it is late. Switch it on and each borrower gets one email before their items fall due, and another if they run late — what they have, when it is due — never twice in a day, through your own SMTP. Run it from the button on the Overdue page or a one-line cron. An item returned damaged goes to maintenance, not back on the shelf.
• Live "who has what" dashboard. See available, checked-out, and overdue counts plus a currently-out table at a glance.
• Guided check-out / check-in. Pick an asset and borrower with a due date; check-in records the returned condition and puts it back on the shelf.
• Automatic overdue flags. Anything past its due date is flagged with how many days late it is and who to chase.
• Full loan history. Every asset and borrower keeps a complete history, exportable to CSV for all, open, or overdue loans.
• Tested double-booking guard. A state machine, backed by the offline test suite that ships with it, guarantees an asset can never be lent to two people at once.
• Installable mobile app (PWA). Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is not stored offline on the device; what you see is read live.
• Labels you can scan. Print labels for your kit on A4 or US Letter sheets or a label printer: the name, a barcode of the tag, and a QR code that opens the item's page on any phone.
• Scan with the camera. At the desk, tap Use camera and hold a label up: phone, tablet or laptop, iPhone included. Nothing leaves the device.
• Signed for, at the desk. The borrower signs on the screen when an item goes out and when it comes back; the signature stays with the loan.
• A page for each borrower. A private link shows what they have out and when it is due, and lets them ask for the items you choose to open to requests.
• Your own fields. Serial numbers, purchase dates, warranty ends: add the fields you track, search by them, export and import them.
• Sign in with your directory. Active Directory or LDAP, with groups for roles, and your own login kept as a way in.
• A usage report you group yourself. Pick two dates and see how much each item, category, department or borrower used the pool (loans, days out, late returns and the share of the time out), on screen or as a CSV.
• Back to an earlier day. Restore from any of the last 14 scheduled backups kept on your server, after a dry run that shows what would change.
• Updates from inside the app. The Updates page installs a new release with your license key: Ownware's signature is checked, a backup is taken first, and the app puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. It never checks by itself.
• Backups by themselves. Automatic backups, an optional copy to S3-compatible storage you own, and a weekly check that the latest backup reads back. The Health page names anything that needs attention.
• Own It 4.0.1 — fixes and an up-to-date manual. For Lendra, 4.0.1 fixes an installer that had lost its styling and a command-line update that ended in an error after putting the previous version back. Its manual, FAQ and QUICKSTART now cover everything 4.0 added, including two Nginx rules that keep the data folder private. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0.2 — the installer opens on every host. For Lendra, 4.0.2 fixes a fresh install on an Apache host: the one-page setup at /install/ looped back to itself and never opened, and now it opens. Your license covers it: press Check for updates on the Updates page, or download it from your order page.

Release notes in full

• Own It 4.1: client installations and your other tools. For Lendra, 4.1 makes two changes that every app gets. An Extended license bought from October 4, 2026 covers up to ten client installations, one per client project: hand each one over to the client or host it for them, with the client's logo and colors from the app's branding settings. The API reference now shows how to connect Lendra to Zapier, Make or n8n, using its own webhooks and API key. Your license covers the update: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0: it updates and backs itself up. For Lendra, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. A new install can start with a sample business and remove it in one click; backups run by themselves, with an optional offsite copy and a weekly check that the latest one reads back; and the Health page says whether the install is looking after itself.
• Own It 3.3: reports and going back a day. 3.3 adds a usage report you group yourself: pick two dates and see how much each item, category, department or borrower used the pool, on screen or as a CSV. You can also go back to an earlier day from any of the last 14 scheduled backups kept on your server, after a dry run that shows what would change.
• Own It 3.2: scan, sign and hand over. 3.2 made the lending desk quicker and the record firmer: labels you can scan, the camera as a scanner, and the borrower's signature when an item goes out and when it comes back. It also gave each borrower a page of their own, your own fields on every item (with checks due, such as PAT tests), and sign-in with your directory.
• Own It 3.1: it writes to the people you serve. The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Each outbound feature ships switched off and runs on your own credentials; a failed send is recorded, and the action that triggered it stands. Lendra gained the scan desk, one-click returns and reminder emails to borrowers, all listed at the top of this section.
• Own It 3.0: works for your AI, not just for you. Reservations join the desk: queue for an item that is out, and when it returns the head of the queue gets a claim window before the offer passes on — first come, first served, no queue-jumping. Over MCP an agent can look things up, lend and take back under the same atomic one-asset-one-loan rule.
• Own It 2.0: API, 2FA, backups, dark mode. Lendra 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.