Use case
Source code & software IP
Code is protected by copyright as soon as it's written. But you still need to prove who wrote it, and when.
The situation
One scenario, two outcomes
The same moment, depending on whether the work was timestamped or not.
The trigger
An agency delivers the technical foundation of your product. Three developers contributed to it, none of them employed by you.
Without proof
During due diligence, the buyer asks for the chain of title on the code's rights. The Git history shows commits reattributed during a repository migration, and two of the developers are unreachable. The indemnity clause gets heavier.
With a certificate
Each delivery was certified on receipt, attributed to its author and its date. The chain reads in a single page, outside the repository, where it can't be rewritten. The matter is resolved in a day.
Votre situation est différente ?
L'adaptation n'a pas abouti — le scénario type reste affiché. Vous pouvez reformuler votre situation et réessayer.
Scénario adaptéD'après : « »
Texte rédigé automatiquement à titre d'illustration, à partir de la phrase que vous avez saisie. Il décrit une position probatoire, pas une issue : il ne constitue pas un conseil juridique et ne préjuge d'aucune décision.
The need
Ownership, contractors, technical audit.
A Git repository is not proof
A repository's history can be altered: dates rewritten, authors reattributed, branches rebuilt. Certifying commit or archive fingerprints at regular intervals anchors this history outside the repository, where it can no longer be rewritten.
Freelancers, agencies, external contributions
A significant share of a startup's code is written by third parties. Attributing each delivery to its author and its date documents the chain of title — the first item requested in a technical audit.
Algorithms and models
An architecture, a set of parameters, a training pipeline often falls under trade secret rather than patent protection. The certificate dates them without disclosing them, and documents the protection measures taken.
→Fingerprint of a commit, a release, or a full archive
→Automatable via API in your CI/CD pipeline
→Contributions attributed to each developer
→The code is never sent to Ipocamp, except for optional storage enabled by the subscriber
For an answer tailored to your case, talk to an expert: this page describes a typical situation, yours has its own specifics.
Contact us