Fixora

Self-hosted preventive maintenance for teams running machines, vehicles or plant: every PM triggers on engine hours, distance or the calendar — whichever comes first.

The problem it solves

Searching for self-hosted CMMS maintenance software you buy once instead of renting? That search usually ends in one of two places: monthly per-user tools like MaintainX or UpKeep, or free open-source CMMSs that assume somebody runs Docker and a VPS. Fixora is the third option — $129 one-time, full PHP source, ordinary shared hosting, and maintenance records that stay yours.

Every operation with equipment runs the same loop: something breaks, somebody fixes it, nobody writes it down. Preventive maintenance lives on a whiteboard, work orders live in a group chat, spare parts run out the day you need them, and the only cost report is a bad feeling at budget time.

• CMMS is typically sold as SaaS priced per user, per month, forever
• Most one-time scripts in this niche are just asset lists with a due-date column
• The pieces that make a real CMMS — usage-based triggers, a parts inventory, and a maintenance calendar — are exactly what they leave out

Every feature

• Work-order photos and documents. PNG, JPEG or PDF up to 10 MB on the work order — the manual page, the compliance certificate, the photo of the fault — checked by the file's bytes, stored under a minted name, served back with the recorded type.
• A PM calendar your team subscribes to. Planned maintenance as a token-guarded read-only .ics feed — due dates appear in Google/Outlook/Apple calendars by themselves, and a revoke button kills a feed the moment it should stop existing.
• Usage meters. Track engine hours, odometer km, or cycle counts per asset with a monotonic reading log that rejects backwards readings unless explicitly flagged as a correction.
• Spare-parts inventory. Part numbers, stock quantity, and unit cost with atomic stock consumption that can never go negative, plus min-stock alerts on the dashboard.
• Maintenance calendar. A month-grid calendar shows every PM due date and open work order, with overdue PM pinned to today under a red badge.
• Usage-based & calendar PM schedules. Preventive maintenance triggers on whichever comes first — a calendar interval or a usage-meter threshold — computed live with no cron job required.
• Work orders with an enforced state machine. Work orders move through an enforced open, in-progress, done/cancelled flow, with a required resolution note before closing.
• Cost & downtime reporting. Month-over-month and per-asset reports roll up labor minutes, downtime, and parts consumption into integer-cent cost totals.
• 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.
• Printable QR asset tags. Print a sheet of QR tags for every asset from the browser. A phone camera on the tag opens that asset's record in your own install — signed-in staff only.
• A daily PM digest. Switch it on and your notification address gets one email a day listing PM overdue or due soon, by date or by meter, and parts at their minimum — through your own mail server.
• Requests from anyone, no seats. Tenants, other departments and customers report a fault from one link or the QR tag on the machine, with a photo, and follow it on a link of their own. It lands in your Requests inbox: accept it into a work order, or decline it with a reason they can read. No login for them and no seat to pay for; off until you switch it on, with a trap field and per-address limits against junk.
• Checklists on PM work. Give a PM schedule its steps: logging it asks for done, fail or not applicable on each, keeps the answers on the work order, and turns every failed step into a corrective work order. A work order with an unanswered step does not close.
• Weekly report for people without a login. List up to 10 addresses, such as a facility manager, an owner or a client. Each gets last week's work orders, what is still open, PM overdue and parts at minimum, once a week, with no prices and their own stop link. No seat needed.
• 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 Fixora, 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 Fixora, 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 Fixora, 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 Fixora 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 Fixora, 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 asset and part import preview tells the truth. The asset and part imports' preview used to count a tag or part number that already exists, or appears twice in the file, as ready, and the import then skipped it. Now the preview names it before you import.
• Own It 3.3: the report reaches people without a login. The 3.3 wave let people without a login take part. For Fixora, that meant a weekly report for a facility manager, an owner or a client: up to 10 addresses, each sent last week's work orders, what is still open, PM overdue and parts at their minimum, with no prices and a stop link of their own.
• Own It 3.2: anyone can report the fault. The 3.2 wave let the people you serve do things for themselves. For Fixora, that meant tenants, other departments and customers reporting a fault from one link or the QR tag on the machine, with a photo, and following it on a link of their own, with no seat to pay for. Preventive maintenance gained checklists, and every failed step becomes a corrective work order.
• 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. What this app gained is listed at the top of this section.
• Own It 3.0: works for your AI, not just for you. My jobs is the whole app narrowed to a technician holding a spanner: their open work in priority order, the next legal status move, a meter reading, a before-and-after photo — a view over the same writers the desk uses, so nothing on a phone can do what that person could not do at the desk.
• Own It 2.0: API, 2FA, backups, dark mode. Fixora 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.