Inspectora

Self-hosted inspection register: what is due, what is overdue, and what was last done to it — every due date computed from the last inspection, never stored.

The problem it solves

Equipment inspections are found out the expensive way. The extinguisher service was due in March, the calibration certificate for the gauge lapsed at some point nobody can name, and the first anyone hears of it is the audit.

The register that fixes this is small: every asset, every inspection type that applies to it, and the date the last one was done.

• A wall planner, a folder of certificates, and one person who remembers the rest
• CMMS platforms priced per asset per month, for what is a list of dates
• "Is it overdue" stored as a flag, which is only correct until the day it silently is not

Every feature

• The due board. Every asset down the side, every inspection type across the top, each cell colored in date / due soon / overdue / never done / failed — and hatched where an inspection does not apply to that class of asset. Click a cell to record an inspection without leaving the board.
• Due dates that compute themselves. You set the interval; the next due date comes from the last inspection. Nothing stores an is-overdue flag that could go stale between a cron that did not run and the screen somebody is reading.
• Never done is its own state. An asset that has never been inspected is not the same as one that lapsed, and neither is the same as one where the inspection does not apply. Three states, because they are three different problems.
• The logbook. What was last done to this asset, by whom, when, with the certificate attached. The board answers what is due; the logbook answers what happened — and a warranty claim rests on the second one.
• Evidence on the record. Calibration certificates and inspection reports attach to the inspection they evidence. PDF or image, sniffed by magic bytes and re-checked by the controller that serves it.
• Schedules and rounds. Book a round of inspections, tick each asset off as it is done and pick its result — pass, pass with remarks or fail — and every asset gets its own dated logbook entry, rather than the same date typed forty times. A failed check shows as failed on the due board until a later pass is recorded.
• A calendar feed that is not a guess. A read-only .ics URL puts every upcoming due date into Outlook, Google Calendar or Apple Calendar and keeps itself current. Revocable, because the link is the credential.
• Reminders that go out. A daily digest of what is expiring to you and, if you switch it on, a note to the address on each asset whose check is due, through your own mail server. Schedule cron/reminders.php, or press Run reminders now.
• Checklist inspections from a phone. Give an inspection type its steps; the form asks pass, fail or not applicable for each, with a note and a photo from the camera. One failed step records a fail.
• Send one inspection's report. A PDF of a single inspection, and a read-only link you can email to a client or contractor without a login. You can withdraw it with one click.
• QR labels and certificates. Print a QR label for every asset, and a certificate of inspection for any passed inspection.
• Assigned schedules. Assign a schedule to a team member; My inspections lists theirs, soonest first.
• Inspections survive a dropped connection. The phone keeps your answers as you go. If the signal drops or the page reloads, they come back; press the button again when you are back online. An inspection sent twice is recorded once.
• 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 Inspectora, 4.0.1 fixes an installer that had lost its styling, a rollback that a page opened during an update could stop 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 Inspectora, 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 Inspectora, 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 Inspectora 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 Inspectora, 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.4: the README in the download tells the truth. The README at the top of the download had not changed since 3.1.4 and still said there is no certificate generator or QR code. It now matches the app's own README, which also names the assets import fix shipped in 3.3.0. No code changed.
• Own It 3.3: the inspection survives a dropped signal. The 3.3 wave kept phones working when the signal drops. For Inspectora, the inspection form keeps your answers on the phone as you go: after a dropped connection or a reload they come back, and an inspection sent twice is recorded once. It is still not an offline app, because nothing is recorded until the form reaches your server.
• Own It 3.2: inspected on a phone, sent to the client. The 3.2 wave let the people you serve do things for themselves. For Inspectora, that meant inspections answered step by step on a phone, with a photo from the camera, and a single inspection's report sent to a client or contractor as a PDF, or as a read-only link they open without a login. QR labels, certificates of inspection for passed inspections, and schedules assigned to a team member came with it.
• 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. This app gained no new outbound path in 3.1 — its pass rewrote the honest-limitations list against the shipped code instead, which is the more useful change when the product was already complete.