Scan the label
Every asset carries a QR label. Scanning it with a work phone opens the record: what it owes, where it was last left, and anything staff have reported about it.
Screenshot of the running software
Know what every asset needs, and when it last got it.
Aether keeps one record per asset for Ontario hospitals and the wider public sector: the inspection schedules you set, the faults your staff report, and a history you can print and hand to an inspector.
Fire extinguisher, 5 lb ABC
| Schedule | Every | State |
|---|---|---|
| Visual inspection | 4 wk | Due 11 Nov |
| Annual maintenance | 52 wk | Done 3 Feb |
| Six-year maintenance | 312 wk | Never serviced |
Open fault report
Damaged or missing part. Needed today.
Reply: I'm working on it
Drawn for this page. The intervals are the organization's own settings.
Supported by
NexLotus works with Innovation Factory, Southern Ontario's innovation centre in Hamilton and Burlington, on bringing Aether to its first public sector partners.
- Infusion pumps
- Fire extinguishers
- Patient lifts
- Emergency lighting
- AEDs
- Boilers
- Elevating devices
- Fume hoods
- Backup generators
- Hospital beds
- Autoclaves
- Playground structures
If you can stick a label on it, it can have a record.
One record per asset, and four ways to keep it current.
The record is built from events, written down as they happen and never rewritten. A mistake is struck through with a reason, not erased.
The due list
A technician's home screen. Every schedule that is due, overdue or has never been done, sorted by how much the asset matters and then by date.
- AED-0031Battery and pads checkOverdue 6 days
- LFT-0108Sling inspectionDue 4 Nov
- GEN-0002Load testNever serviced
Fault reports
Anyone on staff files one in about ten seconds: what is wrong, where it is, and how soon it is needed.
Recalls
Health Canada medical device recalls, checked against your inventory. Healthcare sites only.
Built in a hospital. Useful wherever assets get inspected.
You name each inspection and set its interval. Aether keeps the evidence that it happened. It never certifies anything: that stays with your inspector.
Infusion pumps, beds, AEDs, wheelchairs, and everything biomedical engineering keeps on a schedule.
- Preventive maintenance at the intervals your biomedical team sets
- Health Canada medical device recalls swept against your inventory
- The Ontario Fire Code inspections for extinguishers and emergency lighting
Ceiling lifts and slings, beds, AEDs and mobility equipment, used every day on every floor.
- Sling and lift inspections on your own schedule
- Health Canada recalls for the medical devices you hold
- Fire Code inspections, and TSSA ones for elevating devices
Arenas, community centres, fire halls and parks: generators, refrigeration plants, playground structures.
- TSSA inspections for boilers, pressure vessels and refrigeration plants
- Fire Code inspections across every building you run
- Fault reports from front-line staff, without another app to learn
Emergency lighting, extinguishers, elevating devices and AEDs, spread over dozens of schools.
- Fire Code inspections by school, with what is overdue first
- TSSA inspections for elevating devices
- Electrical Safety Authority work recorded against the asset it touched
Fume hoods, autoclaves, lab equipment and generators, owned by many departments and serviced by one team.
- TSSA inspections for autoclaves and other pressure vessels
- Fume hood checks at the interval your safety office sets
- Electrical Safety Authority and Fire Code work in the same record
Aether does not encode any regulation. The Ontario Fire Code, TSSA and the Electrical Safety Authority set what must be inspected. You turn that into named schedules, and Aether shows what is due, what is overdue and what has never been done.
From a label on a machine to a record an inspector can read.
Five steps, in the order they happen. Most staff only ever do the third one, and it takes them about ten seconds.
-
1
Label it
Print a QR label for each asset. The code on it never changes, so a label stuck on today still opens the same record years and many upgrades from now.
-
2
Set its schedules
Name each recurring inspection and give it an interval in weeks. One asset can carry several. The interval is shown as your setting, never as a legal requirement.
-
3
Hear from the floor
Anyone on staff scans the label and files a fault report. Technicians reply with one tap, and the report stays open until someone resolves it. Text is screened for patient details before it is saved.
-
4
Record the service
A technician marks a named schedule done, writes a condition note in their own words, and says whether the asset should be replaced. If it must not be used, they take it out of service and every scan says so.
-
5
Hand over the history
Print the record for any asset: every inspection, every fault report, and every correction, struck through with its reason rather than erased.
Aether keeps the evidence. It will never tell you an asset is compliant. Your inspector decides that, and the printed record is what you hand them.
Also part of Aether, for hospitals.
The same self-hosted platform carries two products for patients and visitors. Neither one holds a patient record.
What we can show you, and what we can't yet.
Every figure here is self-assessed, not independently audited. We print that at the same size as the numbers.
Shown
- 21 screens
- across all four apps, at zero WCAG 2.0 and 2.1 Level A and AA violations in the 12 September 2026 run
- ASVS Level 2
- a security self-assessment against OWASP's verification standard, and the two findings writing it exposed
- Append-only
- no update and no delete on the event log at any layer, including for an administrator
- Self-hosted
- runs on your infrastructure, with Microsoft sign-in in your own tenant
Not yet
- It has never run at any organization. There is no customer to name.
- No independent accessibility or security audit.
- The fault report screens arrived on 25 October 2026, after that accessibility run, and have not been through it.
- No work orders: no assignment, no due dates on a report.
- The recall sweep covers Health Canada medical devices only.
Questions a facilities manager asks first.
Is this a work order system?
No. A fault report is filed about one asset and stays open until it is resolved, but nobody is assigned to it and it has no due date. Aether is the record of each asset and its inspections. If you dispatch crews and track parts, keep the system that does that.
Which regulations does it cover?
None directly, and that is on purpose. You name each inspection the Ontario Fire Code, TSSA, the Electrical Safety Authority or your own policy asks for, and set its interval. Aether shows what is due and keeps the evidence. It never marks anything compliant.
Is it in use anywhere yet?
Not yet. Aether is feature-complete and pre-pilot. We are looking for a first Ontario partner: a hospital, or any public sector organization with assets to keep inspected.
What personal information does it hold?
No patient record. It does hold staff accounts and the history of who took and returned each asset. Fault report text is screened for health card numbers, record numbers and birth dates, and refused before it is stored. Names cannot be caught reliably, so the screen is a safety net rather than a guarantee.
Where does it run?
On your own infrastructure, not ours. Staff sign in with Microsoft, registered in your organization's own tenant, and backups are sealed before they go off-site.
What does Innovation Factory do?
Innovation Factory supports NexLotus as a growing Ontario technology company. They do not sell, operate or certify Aether. Questions about the product come to us.
Bring us the asset you worry about most.
Tell us which one, and in the briefing we will walk through its record: the schedules, a fault report, and the page you would print for an inspector.