Use cases
Where a private TSA fits, and where it does not
A trusted timestamp is cryptographic proof that data existed at a given moment and has not changed since. When the authority issuing that proof runs inside your own perimeter, the proof is issued under your own key and your own policy. That makes a self-hosted TSA the right tool for some workflows, and one half of the solution for others. This page maps the most common scenarios honestly.
Three questions decide the fit
Trust
Who has to accept the timestamp?
If the proof is checked inside your organization, by systems and validators that trust your own CA, your own TSA is enough. If a court, a tax authority or a business partner must accept it without discussing your internal setup, you need an eIDAS qualified timestamp, or a hybrid design that anchors your own timestamps to one.
Volume
How often do you timestamp?
Log segments every minute, every build, every internal record: high-frequency technical timestamping is where an unmetered internal TSA has no real alternative. A one-time license covers any volume.
Network
Can the system reach the internet?
Isolated and air-gapped networks cannot call a public timestamping service at all. A TSA inside the network is the only way to bring standards-based timestamps there.
Read the decision guide: qualified vs self-hosted timestamping →
Self-hosted
Where TSA Server is the complete answer
In these scenarios the timestamp is consumed internally, or there is simply no route to an external provider.
Isolated environments
Isolated and air-gapped networks
Internal networks without internet access, restricted server segments, test labs and air-gapped environments have no route to a public TSA. TSA Server runs entirely offline on a Windows / IIS host inside the network, signing with a certificate from your internal CA and, if required, a key held in an HSM.
The quality of the timestamps depends on the quality of the server clock. Without internet access, synchronize the TSA host with an internal reference such as a GNSS-disciplined time server or a stratum-1 NTP / PTP source, and monitor its drift. Read the deployment guide →
Software delivery
Internal code signing and build pipelines
Authenticode and JarSigner signatures stop validating when the code signing certificate expires, unless they are countersigned by a TSA. For software built and distributed inside your organization, such as internal tools, scripts, drivers and line-of-business applications, an internal TSA timestamps every build without rate limits or dependence on a public service.
Timestamps from an internal TSA are recognized on machines that trust your internal CA, typically distributed through Group Policy. Software published to customers or the public should be timestamped by a publicly trusted TSA instead.
Business applications
Audit trails of internal applications
ERP, HR, document management and in-house applications record who changed what and when. Those records are only as reliable as the database they are stored in: anyone with enough privileges can edit or delete them without leaving a trace.
Sealing audit trail exports, approval records and configuration changes with an internal TSA adds a cryptographic timestamp to each batch. Any later change to a sealed record no longer matches its token, so tampering with the trail itself becomes detectable.
Internal integrity controls
High-frequency sealing of internal data
Database snapshots, data pipeline outputs, configuration baselines, internal reports and workflow approvals can be sealed as they are produced. Integrity checks then detect any later change, and the sequence of timestamps shows when each version existed. Read the architecture guide →
Development & testing
Development, test and staging environments
Signing and archiving applications need a TSA in every environment, not only in production. An internal TSA gives developers and test pipelines an RFC 3161 endpoint that behaves exactly like the production service, without consuming paid timestamps or depending on internet access.
Hybrid
Where TSA Server works best together with qualified timestamps
In these scenarios you need both unlimited volume and evidence that a third party will accept. TSA Server timestamps everything, at high frequency; at regular intervals, the latest state is anchored with an eIDAS qualified timestamp from qtsa.eu. A few qualified timestamps a day then cover millions of internal ones.
Compliance & audit
Tamper-evident logs for NIS2 and DORA
NIS2 and DORA require security logs to be protected against unauthorized modification, and entities must be able to show that they are. Hash-chaining log segments and timestamping each one every minute with TSA Server makes any later change detectable.
An internal TSA is operated by the same organization whose logs it protects, so it cannot on its own rule out tampering by a privileged insider. Anchoring the head of the hash chain with a qualified timestamp every hour or every day adds independent, legally presumed evidence: 365 qualified timestamps a year per log stream with daily anchoring, or 8,760 with hourly anchoring. Read the NIS2 and DORA guide →
Records management
Electronic archives
Archives handle millions of objects: ingestion batches, format migrations, scanned records and periodic integrity checks. TSA Server can seal all of these internally, so every operation on the archive is traceable in time.
Records that may have to be produced to an auditor, a tax authority or a court need evidence that does not depend on the archive operator. For those, the archive timestamps of the evidence renewal chain (RFC 4998 Evidence Records or PAdES / CAdES / XAdES B-LTA) should be qualified. Read the archiving guide →
Intellectual property
Proof of existence for R&D and creative work
Design files, lab notebooks, source code commits and manuscripts can be timestamped internally the moment they are produced, building a complete, verifiable history of the work.
Priority disputes over authorship, trade secrets or prior art are decided by third parties. Anchoring the internal history with a qualified timestamp, for example once a day, gives that history independent evidential weight.
Planning a setup like these? Our timestamping guides and articles go deeper into how to run a TSA without internet access, how to design a high-frequency pipeline, and how to decide between your own TSA and qualified timestamps.
Qualified
Where a qualified timestamp is the right choice
Some documents leave your organization and must be accepted by others without any discussion of your internal setup. For these, use eIDAS qualified timestamps, which carry a legal presumption of accuracy and integrity in every EU Member State and are recognized out of the box by Adobe Acrobat and EU validation tools.
Signed documents shared with others
Contracts and PDFs signed for customers, partners or authorities, including their PAdES-LTA validation over many years. Read more →
E-invoices and financial records
Invoices whose integrity must be demonstrated to tax authorities and counterparties for the whole storage period. Read more →
Platforms serving many customers
E-signature and document platforms whose customers rely on the evidential value of every signature. Read more →
Map your scenario to the right setup
Tell us about your workflow: who validates the timestamps, how many you need, and what your network looks like. We will tell you whether TSA Server, qualified timestamps or a combination of both fits best.