Knowledge
What is Git — and why is it under easo?
We mention Git on many of our pages. Most of our customers are not software developers — so here it is in plain words: what Git is, why it is the best possible foundation for a quality management system, and why you never have to operate it yourself in easo.
Git in one sentence
Git is a storage system that keeps a complete record of every version of a file — who changed it, when and why, and exactly how it looked at any point in time. Think of it as a logbook that forgets nothing and that no one can quietly rewrite after the fact. Git comes from software development, where millions of people rely on it; today it is the de-facto standard for keeping versioned documents traceable.
You never touch Git
Important: in easo, Git is the engine in the machine room, not your interface. easo hides Git completely. You create, review and release documents like in a familiar editor — no repository, no technical commands, no Git knowledge. The technical foundation works invisibly in the background.
Why Git is the best foundation for a QMS
A quality system stands or falls on one property: you have to be able to trust what it says. Git brings exactly those properties out of the box.
-
A history that cannot drift
Every change is stored as its own immutable entry, chained to the previous one by a checksum. The version history cannot be quietly rewritten — precisely what an audit expects of document control.
-
Every release signed and attributable
Releases are cryptographically signed and verifiable even without easo. For every document it is provable who released it and when — not as a line in a list someone could edit, but secured mathematically.
-
Four-eyes and release are built in
Releasing under the four-eyes principle is not a bolted-on workflow but part of the structure: drafts are kept separate, and only a second approval makes a document valid. Nothing can be marked “released” by accident.
-
Your data, your exit
The store is yours: your documents live in your own Git, never on our infrastructure. Because the format is open and entirely in your hands, leaving easo is possible at any time — no lock-in.
The QMS questions Git answers
The hard questions in an audit are almost always questions about traceability. Because Git keeps the history clean, they are answered before they are asked.
-
“Which version applied on this date?”
The complete history shows every state at any point in time — including the version that was valid on a given audit date.
-
“Who released this — provably?”
The signed release is firmly bound to the document and independently verifiable, even outside easo.
-
“What changed since the last audit?”
Every change is recorded individually; the difference between two states is visible at the press of a button — no manual reconstruction.
-
Document control per ISO 9001 (7.5)
Versioning, controlled changes and a traceable release state are not add-on features — they follow directly from the foundation.
In short
Git gives your QMS a foundation an auditor can trust — complete, signed, verifiable — without you ever seeing a line of technology. easo translates that foundation into an interface people without a technical background actually use.
Stay in the loop
easo is available for macOS — the Windows version is coming soon. Leave us a note and we'll reach out the moment it lands.