Frequently asked questions
Is Obsign a quality management system?
No, deliberately. Your QMS owns manufacturing, batch records and release. Obsign owns the consignment layer your QMS does not reach: permits, balances, shipment documents, dispatch control, and the evidence trail.
Does Obsign read or extract data from uploaded documents?
No, deliberately. It fingerprints them, guards them, and proves they have not changed. A person on your team remains the only thing that can say a document satisfies a requirement.
Is this blockchain?
It uses the same cryptography a blockchain is built from, hash chaining, without the blockchain. Every record is fingerprinted into the next, so any alteration is detected and the exact record named, verifiable on demand. It skips the distributed ledger, which adds cost and data-protection friction without adding anything an inspector asks for.
How does data get in?
Through the registers and uploads, deliberately human-entered at the control points; your counterparties upload their documents through single-use secure links. From the moment data is in, the system makes the downstream mistakes impossible and the history provable.
What happens to our data if we leave, or if Obsign disappears?
Your records are exportable in open, machine-readable formats on request, documents always download as the original files, and the audit trail verifies from its own content, so the integrity of your record does not depend on Obsign.
Do you integrate with our other systems?
Integrations are built with founding operators around their actual systems, not speculatively. The near-term shape is referencing your existing batch and document identifiers; deeper integration follows real customer need.