Why choose a digital trust solution?
Because trust is not something you buy like a subscription. It is built into the architecture. That is where you decide where keys live, who can seal, who can verify, and what you are willing not to do.
The right questions before you choose
Before talking about interface or licence, ask the questions that actually decide. A forgotten certificate in a Windows store, a signature whose regulatory level no one can verify, a “cloud” promise that never says where the private key goes. Those details are often the ones that cost you later.
- What action do you actually need to perform? Seal a document, verify a proof, inventory certificates, orchestrate trust between organisations? These actions are not interchangeable.
- Where should the keys stay? On the workstation, in a local vault, with a qualified provider? A private key is the kind of object you do not lend out, even to your best friends.
- What regulatory level is required? An operational seal is not automatically a qualified electronic signature (QES). If QES is required, a QTSP certificate or service comes into the picture.
- Who must be able to verify? An operator on Windows, a third party via the browser, a partner organisation? The verification channel shapes the product as much as the sealing action itself.
- What is demonstrated today? Distinguish what is delivered, what is in progress, and what is roadmap. An honest architecture starts with what you can show.
Our approach
CertiShielder™ is a Freemindtronic® brand. It brings together building blocks with distinct roles. Seal Soft works locally on Windows. Seal Web targets browser-side verification. Sovereign Trust Gateway targets orchestration in B2B and B2G contexts. Soft first; Web and Gateway in progress, clearly announced as such.
We document digital trust with the same rigour we apply to product development. Explaining TLS, certificates or EviDNA™ in the Knowledge Center is not marketing décor. It is a way to make the black box a little less black. Write to be understood, not to impress — including when the subject is cryptographic.
Choosing a digital trust solution is first choosing an architecture of responsibilities. The software comes after.
What we do today
The demonstrable core of the offer is Seal Soft, on pre-order. On Windows, Soft lets you seal and authenticate documents in PAdES, CAdES and XAdES formats, with an EviDNA™ procedural proof layer (ACGT genome, TrustSequence, manifesto). It also handles generation or import of local certificates (PKCS#12), Windows store inventory, and a local encrypted vault with a segmented key (patent FR3063365 B1). An operator interface, a local API and a CLI complete the workstation.
Seal Web targets verification from a browser — a verify-only companion, in progress. Gateway targets trust orchestration between organisations — in progress, not commercialised. The three roles remain distinct. We do not borrow from tomorrow what has not yet been demonstrated.
What we do not claim to do
Certificates generated locally in Soft do not, on their own, constitute an eIDAS qualified signature. Soft is not document-content encryption via EviDNA™. EviDNA™ is not a legal identity. Network ACME renewal is not presented as an available Soft or Gateway capability. Seal Web does not sign in the browser. Gateway is not open for sale. No promise of inviolability, no “100% secure”.
Naming these limits is not a weakness of messaging. It is the condition for trust to remain credible. If your need exceeds the demonstrable scope, we will say so — rather than stretch a capability until it becomes blurry.
The criteria that really matter
Here is a useful grid, independent of brands. It works as well for evaluating CertiShielder as for framing any digital trust project.
- Documented standards. Recognised formats and profiles (for example PAdES, CAdES, XAdES) beat an opaque proprietary format.
- Demonstrated capabilities. What is delivered, what is in progress, what remains out of scope — with evidence, not adjectives.
- Key control. Who holds the private key, where it is stored, how it is protected.
- Verifiability. A proof that no one can check is only a claim. Who verifies, with which tools, in which context. When a standard format allows it, an external check on public validators such as DSS Validation or the eIDAS / EFDA tests adds an independent reading.
- Regulatory clarity. Distinguish operational sealing from eIDAS levels (including QES via QTSP when required).
- Pedagogy. An organisation that explains its concepts — certificates, TLS, proofs — reduces the risk of a bad decision.
- Stated limits. What the solution does not do should be as readable as what it does.
Why this approach inspires trust
Because it refuses the shortcut. We do not ask you to take our word for it. We show Soft, we document EviDNA™, we point to standards and the glossary, and we clearly separate the demonstrable from the desirable. Before exchanging a single byte, TLS starts by making introductions; with us too, each product has its role, without identity confusion.
This logic extends to external verification. When a signed document can be re-read by a third party on public European Commission validators, the discussion becomes simpler: we are not only asking you to believe us, we also give you ways to verify.
Digital trust is not a badge. It is a sequence of verifiable actions, a clear architecture, and the courage to say “not yet” when that is the truth. If that standard matches yours, the rest is in the facts — not in a generic promise.
To go further
Explore Soft’s scope, Knowledge Center articles, clear FAQ answers, or write to us for a factual pre-order.