Should you build your own MaintenEase?

Build me a self-hosted maintenance work-order app for one facility.

- Use Node 22, Express, EJS, and better-sqlite3 with vanilla CSS and JS;
  server-render the pages and avoid a frontend build step.
- Model locations, assets, technicians, work orders, preventive-maintenance
  plans, and timestamped work logs.
- Give each asset a unique code, location, status, notes, and complete service
  history; add a printable QR code that opens its detail page.
- Work orders need priority, assignee, due date, status, checklist, labor notes,
  parts used, and photo attachments stored on disk.
- Provide a mobile-friendly technician queue with My Work, Due Today, Overdue,
  and Completed views plus large tap targets for status changes.
- Let an admin create recurring plans with daily, weekly, monthly, or meter-based
  intervals; a background job creates the next work order without duplicates.
- Send assignment and overdue alerts through ntfy, with its URL and topic in
  .env; show delivery failures in an admin log.
- Add dashboards for open work by priority, overdue work, completion time, and
  preventive-maintenance compliance.
- Support CSV import and export for assets and work orders, plus a documented
  command that backs up the SQLite database and attachment directory.
- Use session authentication with admin and technician roles, bcrypt password
  hashes, CSRF protection, upload limits, and an audit log.
- Include seed data, focused tests for recurrence and permissions, an .env.example,
  and a README with setup, backup, restore, and upgrade steps.
- Out of scope: native apps, predictive maintenance, accounting integrations,
  SSO, and multi-tenant billing.