IMGIAINFO

IMGIAINFO inc. — Québec, Canada

Tailor-made platforms:
image, AI, information

We take a process that lives on paper or in a spreadsheet and turn it into a system that does the work for real — keeping the trace that goes with it: every action named, every machine identified, every value before and after preserved.

Our four fields

One chain, from the raw data to the signed trace

Web, applications, data integrity, ALCOA++

Web and desktop applications, databases, and the audit trail that goes with them: attributable, legible, contemporaneous, original, accurate — plus complete, consistent, enduring, available.

What ALCOA++ means →

Trusted AI, under control, compliance proven

Vision and language models installed inside the work chain, with the safeguards that make every decision explainable — and one simple rule: the model creates nothing and signs nothing.

An LLM in the loop →

Sovereign cloud: public, private, local, your rules

On your hardware, inside your network, or with a provider you choose. No dependency on a service you do not control.

Replace the dependency →

Sovereignty: replacing the dependency on American companies

Linux instead of Windows, Droidian instead of Android, our own git forge instead of GitHub, open models instead of paid APIs — and an old graphics card instead of a new server.

Digital sovereignty →

“The model creates nothing and signs nothing.”

Our rule, for any AI placed inside a regulated work chain.

Nine attributesALCOA++, applied line by line: who, where from, what, before, after, why, when, result.
Four jurisdictionsFDA, NMPA (China), PIC/S (Japan), Health Canada — the functional requirements, not the brand of the tool.
Zero external dependencyYour rules, your hardware, your models. Nothing leaves without your decision.

The trace

What every entry carries

A defensible record is a record that reads on its own, and answers an inspector on its own.

Who a named user, never a shared account
Where from the machine, identified by its key
What the action taken
Before the value that existed
After the value written
Why the reason
When a precise UTC timestamp
Result success or failure — both are written

Append-only

You add, you never erase. A previous value cannot disappear from the record.

Failures too

A refused login, a rejected rule, an invalid entry: each one leaves an entry behind.

Chained

Every entry depends on the previous one: editing, moving or inserting something shows.

See the full ALCOA++ page →

Getting started

How a project begins

  1. We look at how the work is done today. Your forms, your spreadsheets, your paper steps, your exceptions.
  2. We write the rules and the action blocks. What the system may do, what it may not do, and what requires a validation.
  3. We put the trace in. Every write enters the log with the person, the machine, the value before and the value after.
  4. We read a witness record with you, line by line, before widening the scope.