An open-source CMMS for work orders, preventive maintenance, spare parts and reliability. Built on ISO 14224, hosted by you.
The real application, running the bundled demo plant. Interface shown in Swedish; English is built in.
Your maintenance history is the most valuable data your plant owns. Years of failure codes, repair times and spare-part usage decide what you replace, what you inspect and what you can stop doing.
Today that history usually lives inside a licence. When the contract changes, the price changes or the vendor retires your version, the data you created becomes something you rent back.
OSMAINT starts from the other end. The code is open under AGPLv3. The database is plain PostgreSQL. The taxonomy is ISO 14224, loaded as data you can read and change. If you stop using us, you keep everything.
A working alternative to IBM Maximo, SAP PM and MaintMaster, built by a maintenance consultancy rather than a software vendor.
Corrective, preventive and emergency work in one list. Every order carries its asset, priority, ISO 14224 failure code, attachments, logged time, spare parts issued and returned, and the cost that follows.
Operators file work requests in plain words. A planner turns them into work orders with one click.
Time- and meter-triggered schedules generate their own work orders. Set lead times, seasonal windows and parent and child PMs. The PM calendar shows what is due long before it is late.
Meter trends feed predictive maintenance, so an interval can follow real wear instead of a guess made at commissioning.
MTBF, MTTR, availability, PM compliance and cost per asset, calculated from the work you actually logged. Labour, parts and other costs split per machine. Export to CSV, or build your own report and watch it over time.
Describe a fault the way a technician would say it. OSMAINT proposes the equipment class, failure mode and priority. Ask questions of your own data in English or Swedish and get answers drawn from your records.
The engine is pluggable. Point it at any OpenAI-compatible model, a local LLM on your own hardware, or nothing at all. Without a provider it falls back to deterministic rules and still runs fully offline.
Pick the taxonomy your industry speaks when you set up. The asset tree, its levels and the allowed failure modes follow. Change it later and the whole tree changes with it.
Terminology follows EN 13306. Asset-management readiness maps to ISO 55001.
Forty-five views in the web application, one REST API with 299 endpoints behind them. No module on this page is held back for a paid tier.
On the plant floor: a Flutter app for phones and tablets that queues work orders offline and syncs when the connection returns.
The project runs its own release gate on production hardware. These are the latest results, with the method published next to them.
Not yet passed: an independent penetration test and a year of production use at a customer plant. Both are on the scorecard, in the open, until they are done. Read the scorecard
One Go binary and one PostgreSQL database with PostGIS. Docker Compose starts the database, the API and the web interface in their own containers. Every migration applies automatically on start.
No Docker? Build the server with go build and point it at your own PostgreSQL. No telemetry you did not ask for.
# get the code
git clone https://github.com/MaintComp/osmaint.git
cd osmaint
# database, API and web in one command
docker compose up -d --build
# web -> http://localhost:3000
# api -> http://localhost:8080The full system under AGPLv3. Every module on this page, on your own server, for as many users and sites as you have. Change it, extend it, send improvements back.
Get the sourceOSMAINT hosted and operated for you, single sign-on, white-label, a support agreement with a service level, and a commercial licence when AGPL does not fit your organisation. Help moving off Maximo from people who work in it every day.
Talk to MaintCompContributions are welcome, including AI-assisted ones, as long as they are actually tested. The contributing guide covers dev setup, the acceptance checklist and how to report a bug.
Contributing guide