Open Repair RecordWhat does a completed repair mean?

Self-hosted

Run it inside your company

The editor, the guide and the examples can run on your own server, behind your firewall. It is the same site as openrepairrecord.com, minus the visit counter, and it never needs the internet.

What you get

  • The whole site: the report editor with its check, print and PDF, JSON download and upload, the guide, the five examples, the blank template and the format with its JSON Schema.
  • No outside requests. No analytics, no fonts, no scripts or images from anywhere else. Our tests load every page and fail if a single request leaves the server.
  • No server-side data. It is a set of static files. Records are written in each person's browser and saved as files on their device; nothing is stored on your server.
  • No account, no licence key, no telemetry. MIT licence for the code, CC BY 4.0 for the text.

Option 1: Docker

One container, an unprivileged nginx on port 8080:

docker run -d --name open-repair-record -p 8080:8080 --read-only --tmpfs /tmp \
  ghcr.io/dmytrorybka/open-repair-record-editor:1.0

Then open http://your-server:8080/build/. The container runs as a non-root user, works with a read-only file system, answers /healthz for your load balancer, and sends a strict Content-Security-Policy that only allows its own origin.

Tags: 1.0 follows the latest 1.0.x release; 1.0.0 stays fixed. Images are built for amd64 and arm64 from this repository by GitHub Actions.

Option 2: a folder of files

Download open-repair-record-onprem-1.0.0.zip from the releases page, check it against the published SHA-256, and unpack it into any web server's document root: IIS, nginx, Apache, or an internal static host.

  • IIS: the zip includes a web.config with the file types and the 404 page.
  • nginx or Apache: serve the folder as it is; /build/ maps to build/index.html.
  • It must be served over HTTP or HTTPS, not opened from the file system, because the editor's script is a module.

Option 3: build it yourself

From a clone of the repository, with Node.js 20 or newer:

npm ci
npm run build:onprem      # writes the self-hosted copy to dist/

Good to know

  • Drafts are per browser. Each person's draft lives in their own browser. To share a record, download it as JSON or PDF and keep it where your team keeps documents.
  • Updates. Every 1.x version only adds; a file written with 1.0 still opens. Pull a newer image or unpack a newer zip; there is nothing to migrate.
  • Your own wording. The text is CC BY 4.0, so you may adapt the guide to your company. Keep the credit "Open Repair Record, openrepairrecord.com".
  • Checks in a pipeline? The orr command line validates and checks records before an import.
  • Questions or a feature your IT team needs? Write to support@pmfriend.com or open an issue on GitHub.