Data sovereignty

A system that listens to your company
has to live inside your company.

VigilIA handles the most sensitive material an SME has: what its people say when they believe nothing is being recorded. Margins, names, purchase prices, internal arguments, deadlines you would rather nobody knew about. That is why the model runs in your own house, and there is no version of this in which your conversations train somebody else's model.

01

On-premise by default

The standard deployment is in your own plant or on a private server of yours. Shared cloud is the exception, not the rule.

02

Local model

Extraction uses gpt-oss:20b on your own hardware. External providers exist, but they have to be switched on by hand and in writing.

03

Quotation always

No statement the system makes exists without the sentence it came from, with its origin and its time. Traceability is not a menu option.

04

MIT licence

The code is open. You can audit it, fork it or keep it the day you decide to carry on without us.

Architecture

The full journey of a sentence

From the moment someone forwards an audio message to the moment the commitment is closed with evidence, everything inside the box happens on infrastructure you control.

VigilIA architecture Sources come in through connectors, are normalised with api_convert and api_whisper, commitments are extracted with the local gpt-oss:20b model through api_chat, the VigilIA core stores and schedules them, and the outputs go to messaging channels and back to the client's own repository. Everything except the external channels happens inside the client's perimeter. CLIENT PERIMETER · your server, your network 1 · SOURCES Email and IMAP WhatsApp audio Photos and documents NAS, Drive, Nextcloud ERP and CMMS 2 · NORMALISATION api_convertMarkdown + OCR api_whisperspeech to text 3 · EXTRACTION api_chatgpt-oss:20b local Validationschema + hard signals 4 · CORE VigilIAcommitments and evidence Clockordered by consequence Schedulerreminders and escalation PostgreSQL + MinIOdata and attachments api_authidentity and audit 5 · OUTPUTS Telegram Email Web dashboard Your repository the evidence goes back to your folder

The only thing that leaves the perimeter is the message an external supplier receives — because that is what it is written for — and it contains exactly what you would write in that email, not one line more.

Data processing

The questions a DPO asks,
answered before they are asked.

VigilIA processes personal data of employees and of third-party contacts. There is no way around it, so the only honest thing to do is design it on that assumption from the start.

In the standard deployment, pibiCo is neither controller nor processor of your data, because it holds none of the data: it lives on your server. When the deployment runs on pibiCo infrastructure, the corresponding processor agreement is signed.

No further than the transcription, unless you configure it the other way round. The audio is turned into text, the commitments are extracted and the audio file is deleted according to the retention policy you set, with a default of seven days.
For as long as you decide. The default is five years for the commitment and its evidence, in line with the usual contractual limitation periods; the full source text can be purged earlier, keeping only the quotation.
The commitments they are part of and those of their team, the same as they would see by asking in the corridor. There are no individual performance screens and no comparisons between people, and there are none on the roadmap.
It is processed under the legitimate interest of managing the contractual relationship, minimised to what is necessary — name, company, contact channel — and rights of access and erasure are answered from the dashboard itself, without having to open a ticket.
In most SMEs, no: there is no automated decision-making with legal effects and no systematic large-scale monitoring. Even so, we hand over the record of processing activities and the risk analysis ready-made as part of the deployment, so that your adviser decides with the papers in front of them and not by hearsay.

Deployment profiles

Four ways to have it, three of them in your own house.

Comparison of VigilIA deployment profiles
ProfileWhere it runs GPUWho it is for
Pilot on the pibiCo cloudpibiCo server, database separated by organisationSharedThe eight weeks of the trial, without buying anything
Dedicated private serverYour own VPS or server, managed by pibiCoDedicatedSMEs with no server room and no wish to have one
On-premiseYour own plant, two machines in active and passiveRTX 5090 32 GBAnyone who wants the data inside and accepts keeping hardware running
Extended on-premiseYour own data centre, high availability of dataBlackwell 96 GBIndustry with an isolated network or hard sovereignty requirements

High availability comes from replicated, restorable data, not from the GPU. If the card goes down, VigilIA stops extracting for a few hours but does not lose a single commitment already on record, and searches and reminders carry on working.

Take it to your IT person before your director.

It is the conversation we would rather have first. If the architecture does not convince whoever keeps your network running, the rest is beside the point.

Talk to a technician