DEV Community: Ownware

A customer's AI agent vetted us before he bought. Here is what it fetched, what 404'd, and what we changed.

Ownware — Sun, 30 Aug 2026 06:06:15 +0000

We sell small self-hosted business apps: plain PHP and MySQL, bought once, run on your own server. Recently a sale came with something we had not seen before, and we wanted to share what an agent-driven purchase looks like from the vendor's side. The order itself took eleven seconds. The evaluation that preceded it took two hours the day before, and part of it was not done by the buyer at all. It was done by a program acting on his behalf.

This is the account of that visit, taken from our own access log, with everything that could identify the buyer left out. We are writing it up because the pattern is going to be ordinary very soon, and because it changed four things about our site the same morning.

What the log shows

The buyer arrived from a DuckDuckGo search on one of our comparison pages, the one that answers "what is a self-hosted alternative to a well-known retail point-of-sale product". From there the path was the one you would expect from a careful person: a related product page, the home page, the product he eventually bought, its live demo, the suite that bundles it with four neighbours, two of those neighbours' pages, the pricing page, and the page that explains how to connect an AI assistant to the software.

Interleaved with those page views, from the same network, was a second visitor with a different signature. Its User-Agent named an AI coding assistant, and it did not browse the way a person browses. In the space of a few minutes it fetched:

/legal: the terms, the refund policy, the licence.
/support: what is covered, how to reach a human, what happens when a download fails.
/.well-known/security.txt: the machine-readable security contact defined by RFC 9116.
The product page, and the home page.

Then it asked for four URLs that did not exist:

/suites
/contact
/p/field-service-suite
/jobora, the product's bare slug without the /p/ prefix

Each returned a 404. The agent did not retry with a different spelling; it reported what it found and moved on. Fifteen hours later the buyer came back through the same search engine and bought.

We do not know what the agent's owner asked it. The fetch pattern is consistent with a simple instruction, something like "check whether this vendor is legitimate before I pay them", and the four guesses are exactly what a person would type if they were looking for a bundle, a way to get in touch, and a shorter address for the product. The point is not that the agent was clever. The point is that its report almost certainly contained the sentence "the site has no contact page", and that sentence was wrong for a reason entirely of our making.

What "vetting" looks like to a machine

A person deciding whether to trust a small software vendor looks for signals that are hard to fake: a real terms page, a named refund policy, a way to reach someone, evidence that the software exists and runs. An agent looks for the same things, but it can only find them at addresses it can guess or that the site tells it about.

That makes the machine-readable surface of a store load-bearing in a way it was not two years ago:

/llms.txt: a plain-text index of what the site is and what it sells, written for language models. Ours lists every product with its current price, read from the database at request time, so it cannot drift from the store.
Structured data: each product, suite and comparison page carries a schema.org Product and Offer block with the live price.
security.txt: the standard place for a security contact. The agent fetched it third.
A pricing page with every price on it, added earlier this month after another agent guessed /plans, /pricing, /pricing-plans and /plans-pricing in sequence and 404'd on all four.
The obvious addresses: /contact, /suites, and a product's bare slug. These are not standards. They are what people and their agents type.

The first four we had. The fifth we did not, and the agent found the gap in under a minute.

What we changed the same morning

By the time this was written, the four missing addresses existed and had been verified from outside the network:

/suites is now an index of every suite: what each one bundles, its one-time price, what the same apps cost bought separately, and the difference. The figures are computed from the current single-licence prices on every request. There is no typed number on the page, and a test refuses a build that contains one.
/contact redirects permanently to the support page, which now carries a contact section for everything that is not a support request.
/p/field-service-suite and /p/field-service, a suite's slug under the product prefix, redirect permanently to the suite.
A bare product slug (/jobora, /invora, even /FLEETORA) redirects permanently to the product page. A bare suite slug, with or without -suite, redirects to the suite. Anything that is neither is still an honest 404. The catch-all is registered after every other route, so nothing that existed can be shadowed by it.

Eighteen tests cover the new routes. The change shipped through the same deploy pipeline as everything else, which, as of the same morning and for an unrelated reason, refuses to release a build in which any sellable product lacks its download file.

If you sell software, this is coming for you too

Look at your own 404 log for the addresses that are guessed rather than mistyped. /contact, /pricing, /plans, /docs, /status, /security, a product name without its prefix: every one of those is a report an agent will hand to its owner, and "the site has no contact page" is a worse sentence to have in that report than it deserves to be. The fix is a morning's work.

And keep the roles straight. The buyer's agent was not our referrer. It was his due-diligence tool. The search engine brought him; the comparison page kept him; the demo, the suite page and the pricing page did the persuading; the agent checked our homework. Each of those stages is a page you control.

We build Ownware, the store this happened on: https://ownware.io. Nothing here identifies the buyer; the product is named because a product does not identify a person. This post was written by a human with AI assistance; every fact comes from our own access log and was checked against the live site on the day of posting.

Stop renting your maintenance software: the CMMS cost teardown

Ownware — Sun, 23 Aug 2026 17:31:00 +0000

A 10-technician shop pays $2,400–$9,000 every year for cloud CMMS at current list prices. A self-hosted CMMS is $129 once. Here is the math, and the honest list of what you give up.

The deal you actually signed

Every major cloud CMMS prices the same way: per user, per month, forever. Not per asset. Not per work order. Per human being who needs a login.

Think about what that means for maintenance specifically. The whole point of a CMMS is that everyone touches it — the techs closing work orders, the supervisor scheduling PM, whoever logs meter readings on the forklift. A per-seat meter on maintenance software is a meter on the exact behavior that makes the system work. Every person you add to the system adds to the bill; every person you leave off the system to save money punches a hole in your maintenance history.

The current list prices (fetched from the vendors' own pricing pages on 2026-07-20):

Fiix (fiixsoftware.com/pricing): Basic $45 per user, per month, Professional $75 per user, per month. Enterprise is custom pricing.
MaintainX (getmaintainx.com/pricing): Essential $20 per user/month billed annually ($25 billed monthly), Premium $65 per user/month billed annually ($75 monthly). There is a free Basic tier, and Enterprise is quote-only.

The store's comparison pages (prices checked 2026-07-05) add two more data points: UpKeep at $24/user/mo on Essential, and Limble, which publishes no price at all — tiers behind a quote-gated calculator. When a vendor won't print a number, that is itself information about how the number behaves over time.

The math at a 10-tech shop

Take a realistic small operation: ten people who need logins — eight technicians, a maintenance supervisor, an office admin who runs the reports.

CMMS	Per user/mo	10 users/mo	Per year
Fiix Professional	$75	$750	$9,000
Fiix Basic	$45	$450	$5,400
MaintainX Premium (annual)	$65	$650	$7,800
UpKeep Essential	$24	$240	$2,880
MaintainX Essential (annual)	$20	$200	$2,400
Fixora, self-hosted	—	—	$129 once

Read the cheapest row again. The entry tier of the cheapest metered option costs a 10-tech shop $2,400 a year — every year, with your entire maintenance history (what broke, when, what it cost, which machine is bleeding you) living on the vendor's servers. Stop paying and the history goes dark.

And that's the cheapest configuration. The tiers vendors mark "Most popular" — Fiix Professional, MaintainX Premium — put the same shop at $7,800–$9,000 a year. Over five years that's $12,000–$45,000 spent on software whose core job is date arithmetic and a parts ledger.

To be fair to the SaaS side: MaintainX has a genuinely free Basic tier, and if it covers your needs, use it — free beats $129. The teardown is aimed at the moment you outgrow free and the per-seat meter starts.

What a CMMS actually needs to do

Strip away the enterprise brochures and the core loop is small. Here is what Fixora — the $129 product on the other side of this comparison — actually ships. This is its real feature set, no inflation:

Assets — auto-numbered tags (AST-0001…), category, location, status, purchase info, photo, and a full per-asset view: maintenance history, open work orders, PM schedules, meters, downtime log.
Usage meters — engine hours, odometer km, cycle counts, with a monotonic reading log: a lower reading is rejected unless explicitly flagged as a correction, so history can't silently go backwards.
PM schedules, calendar AND usage-based — interval in days, and optionally every N units on a meter. Next due = whichever trigger comes first, computed live in your timezone. No cron job. Overdue and due-soon are flagged on the dashboard, the PM list, and the calendar.
Maintenance calendar — a month grid of PM due dates and open work orders; overdue PM is pinned to today with a red badge; print-friendly.
Work orders — WO-0001…, corrective/preventive, four priorities, assignee, labor minutes, downtime minutes, and an enforced state machine: open → in-progress → done/cancelled. Done requires a resolution note.
Spare-parts inventory — part numbers, stock, unit cost, min-stock alerts, CSV export. Consuming parts on a work order decrements stock atomically (stock can never go negative) and snapshots the unit cost onto the WO, so later price edits never rewrite history.
Cost and downtime reporting — month-over-month and per-asset: labor (minutes × your hourly rate) plus itemized parts, all in integer cents, never floating-point money.
Technician work view — each tech's open work grouped by priority; prints as a daily worksheet.
Printable QR asset tags — offline QR generation, no CDN; scanning opens the asset's page after sign-in.
CSV exports everywhere — assets, work orders, PM schedules, monthly costs, parts. You are never locked in.

The claim behind all of it: maintenance math you can audit. Next-due is pure date arithmetic plus a usage trigger against real meter readings, and the shipped test suite — 316 offline assertions, including hand-computed leap-year and timezone fixtures and the full work-order transition matrix — runs on your machine with one command. You don't have to trust the vendor's math; you can execute it.

The self-hosted math

Fixora is $129, once. Plain PHP 8 + MySQL (or SQLite), zero framework, zero Composer dependencies, no build step. It uploads to the $5/month shared hosting you probably already pay for and installs through a web installer in about two minutes.

Break-even against the table above, for the same 10-tech shop:

vs Fiix Basic ($450/mo): about 9 days
vs MaintainX Premium annual ($650/mo): about 6 days
vs UpKeep Essential ($240/mo): about 16 days
vs MaintainX Essential annual ($200/mo): under 3 weeks

Even at the store's more conservative 3-user comparison scenario (prices checked 2026-07-05 at ownware.io/vs/fixora), the one-time price equals 1–3 months of subscription. After break-even, the delta compounds: year one at the cheap end saves ~$2,270; at the "Most popular" tiers it saves ~$8,900. Every year after that, the SaaS column resets to full price and the Fixora column reads zero — because there is no per-user meter. Ten logins-worth of usage or two, the price was $129.

The other half of the ownership argument isn't money. It's that your maintenance history — the record of every failure, every part consumed, every hour of downtime — lives in your database, on your server, exportable to CSV at will. That record is operational memory. Renting it means it evaporates the day you stop paying.

What you give up — read this before the demo

Credibility requires the full list. Self-hosting is a trade, not a free lunch, and Fixora is deliberately the focused core of a CMMS, not an enterprise EAM suite. Straight from its own documentation:

You operate it. Uploading files, pointing a web root, making one folder writable. It's a two-minute installer on standard shared hosting, but the two minutes are yours.
You run backups. No vendor is snapshotting your data nightly. The backup surface is small — one MySQL database (or a single SQLite file) plus an uploads folder — but if you don't back it up, nobody does.
No vendor support SLA. This is a one-time commercial license for source code, not a subscription with a 24/7 support desk. When something confuses you at 2 a.m., there is no chat widget.
Single admin login per installation. Fixora is single-tenant by design: one shared sign-in, with technicians managed as an assignee list rather than as separate user accounts with roles and permissions. For a small crew this is often fine; if you need per-user audit trails and role-based access, it's a real limitation.
No native mobile app. The web UI is responsive and works in any phone browser — techs can scan a QR tag and land on the asset page — but there is nothing in the app stores.
No IoT / telematics auto-ingest. Meter readings are typed in by a person. The monotonic log keeps them honest, but nothing reads your sensors automatically.
No purchasing / purchase-order module. Parts stock is adjusted by hand or by work-order consumption. If your parts workflow revolves around POs and vendor management, that lives outside Fixora.
Reports are on-screen + CSV. No server-generated PDFs; the calendar and worksheets are print-CSS instead.

Each of those is a feature the metered products legitimately sell. The question the math forces is whether they're worth $2,400–$9,000 a year to your specific operation — or whether they're enterprise features you're being charged for while using the core loop.

Who should NOT switch

Honesty cuts both ways, so plainly:

Multi-site enterprises. If you run maintenance across plants with site-level tenancy, approval chains, and integrations into ERP, you are the customer Fiix Enterprise and Limble exist for. Fixora is single-tenant and will not stretch that far.
Operations that need sensor-driven PM. If condition-based maintenance from live telemetry is your model, manual meter entry is a non-starter.
Teams where per-user accountability is mandatory. Regulated environments needing individual logins with audit trails per user should not run on a shared admin sign-in.
Crews with zero tolerance for self-administration. If nobody on staff can upload files to a web host and download a backup, the subscription's white-glove layer is what you're actually paying for — and that can be rational.
Teams the free tier already covers. Again: MaintainX Basic is free. Don't pay $129 to escape a bill you don't have yet.

Everyone else — the small factory, the facilities crew, the fleet on hour-based service intervals, anyone currently quoted per-user-per-month for assets + PM + work orders + parts + cost visibility — is paying an enterprise meter for a core loop that fits on shared hosting.

See it before you believe any of this

Don't take a teardown's word for it either. There's a live Fixora demo — real data, no sign-up — at ownware.io/demo/fixora. Open the maintenance calendar, log a meter reading, consume a part on a work order, and check the cost report against a calculator. Five minutes, and you'll know whether the core loop covers your operation.

And if you want the line-by-line comparisons against the vendors named above — Fiix, MaintainX, UpKeep, Limble, with cited prices and dates — they're at ownware.io/vs/fixora, alongside the rest of the alternatives library. The product page is ownware.io/p/fixora: $129, one-time, source included, your server.

Originally published at ownware.io/guides/cmms-cost-teardown — 50 self-hosted business apps, bought once, plain PHP on your own server. Pricing claims in this article are cited and dated on our Price Observatory.