by OriginStamp AGData anchoring and timestamping
A Swiss timestamping API that batches SHA-256 hashes into Merkle trees and anchors them to Bitcoin and Ethereum, priced by offer.
Anchor your hashes to Bitcoin and Ethereum through one REST call, without running wallets, nodes or Merkle batching yourself.
OriginStamp takes SHA-256 hashes over a REST API, merges them with other customers’ hashes into Merkle trees and anchors each root to Bitcoin and Ethereum, so one on-chain transaction covers many proofs. Webhooks report when a tree is confirmed, and a proof request returns the branch you need to verify later. Teams that want blockchain proofs for logs, archives or documents without building the chain side get it as a service.
Against 3 other products we reviewed in Data anchoring and timestamping: what you pay for with each, the five access facts, the plan limits we recorded and each review's bottom line. The note under the table says how each one was checked.
| Metric | OriginStamp | Hedera Consensus Service | Bernstein | Truestamp |
|---|---|---|---|---|
| What you're paying for | Saves engineering timeAnchor your hashes to Bitcoin and Ethereum through one REST call, without running wallets, nodes or Merkle batching yourself. | Worth the priceOrdered, consensus-timestamped records on a public ledger at a published $0.0008 per message, with no contract or vendor account. | Compliance includedCourt-oriented proof of authorship for IP files: Bitcoin anchoring plus EU qualified timestamps, without the vendor seeing your files. | Saves engineering timeProofs that verify offline with an open-source CLI, committed to two public chains, and free for 50 items a month. |
| Overall score | 3.8 | 4.8Best | 3.7 | 3.5 |
| Free option | –Not measured | Paid only | Paid only | Free plan |
| Card to start | –Not measured | –Not measured | –Not measured | No card needed |
| Getting access | Sales call required | Self-serve | Self-serve | Self-serve |
| Starter priceCheapest paid plan | –Not measured | $0.0008/message | $54/mo | $0 |
| Pricing model | Custom quote | Usage-based | Tiered | Tiered |
| Pricing page | Prices hidden | Public prices | Public prices | Prices hidden |
| What it anchors to | Bitcoin and Ethereum (Merkle root per batch) | Hedera public ledger (messages on a topic) | Bitcoin, plus EU and China timestamp authorities | Stellar and Bitcoin (epoch roots of its own ledger) |
| Billing unit | Offer based on timestamps and proofs | $0.0008 per message, paid in HBAR | Registration credit (one project version, up to 99 files) | Items a month per plan; paid tiers not on sale |
| Free option | Free web tool for single proofs; test API key on request | Testnet only | None; certificate validation is free | 50 items a month, 90-day retention |
| Reference scenario (100,000 hashes/mo) | Priced by sales | $80, one hash per message, computed | Not offered (no API) | No plan on sale |
| Proof you keep | Downloadable certificate or raw proof | No proof file; records on mirror nodes | PDF certificate | Self-contained proof bundle (JSON or binary) |
| Verify without the vendor | Manual steps documented | Open-source mirror node you can run | Manual steps documented; browser validator | Open-source CLI, offline |
| Only the hash leaves your systems | Yes | Yes, you choose the message content | No; files uploaded encrypted | Yes; content can also be redacted |
| Qualified timestamps (eIDAS) | eIDAS compatibility on request | No | EU qualified on Scale and Enterprise | No (terms say not qualified) |
| SOC 2 / ISO 27001 | Not stated | Node data centres must be SOC 2 Type 2 | Not stated | Not stated |
| API and webhooks | REST API, batch hashes, webhooks | SDKs, mirror node REST and gRPC; no webhooks | None | REST, GraphQL, CLI, MCP; webhooks on paid tiers |
| SSO | Not listed | Not applicable (key-based accounts) | Enterprise plan, one-time setup fee | Not listed |
| Bottom line | From its public pages, OriginStamp is a long-running anchoring API with two chains, batching and webhooks. The price is an offer, and a few docs pages describe an older anchoring method. | From its public pages, HCS is the cheapest way here to put hashes on a public ledger at a price you can compute. You build the proof handling yourself, and there is no plan, contract or vendor audit report. | From its public pages, Bernstein is the most legally oriented option here, with EU qualified timestamps on a self-serve plan. It is a web app for IP files, not an anchoring API, from $54 a month. | From its public pages, Truestamp has the strongest proof portability here: two chains, self-contained bundles and an open-source offline verifier. Only the free plan can be used today. |
Evidence: OriginStamp: facts checked 2026-10-15 from its public sign-up and pricing pages, no completed hands-on run; Hedera Consensus Service: facts checked 2026-10-15 from its public sign-up and pricing pages, no completed hands-on run; Bernstein: facts checked 2026-10-15 from its public sign-up and pricing pages, no completed hands-on run; Truestamp: facts checked 2026-10-15 from its public sign-up and pricing pages, no completed hands-on run. Prices in USD as listed, excluding tax. "–" means not recorded.
Review from public pages
Written from OriginStamp's public pages (pricing, security or privacy, and docs) as read on Oct 15, 2026. We did not sign up, and no hands-on run is published yet.
We read OriginStamp's timestamp product pages, its demo page, the company FAQ and legal page, and its documentation (concepts, FAQ, guide, API reference) on Oct 15, 2026; we did not sign up or request a test key for this review. The home page now leads with OriginVault, an archive product; the timestamping service sits under the OriginStamp Timestamp menu with a 'Try Free' demo and a 'Book a meeting' button.
The docs are clear on the mechanics. You send SHA-256 hashes to /v1/timestamp, the response names a Bitcoin tree and an Ethereum tree, and a webhook fires when each tree is verified on chain; the docs list a 24-hour timestamp interval for both chains. A proof request returns the Merkle branch, and a separate guide explains how to check it against the OriginStamp Bitcoin address or Ethereum contract without the vendor.
Two things need a question. The docs FAQ still describes turning the Merkle root into a Bitcoin private key and address, while the verification guide says roots have been stored in an OP_RETURN output since Feb 15, 2021. And the product page lists 'REST API, webhooks, SDKs', but the docs show plain HTTP calls and name no SDK.
Each submitted hash goes into a Bitcoin tree and an Ethereum tree, so one proof does not rest on a single chain.
vs Bernstein: Bernstein anchors to Bitcoin only, with EU and China timestamp authorities alongside.
The docs say the hash is calculated locally and only the hash is transmitted; the demo page hashes the file in the browser.
The timestamp endpoint takes an array of hashes, and webhooks report tree and proof events, with a status endpoint as a fallback.
vs Bernstein: Bernstein has no API; Hedera bills each message separately.
The vendor states it has run timestamping since 2013 and created more than 60 million proofs.
The docs FAQ says pricing depends on the number of timestamps and proofs and asks you to email for an offer or a free test API key.
Workaround: The free web tool on the demo page creates single proofs without an account.
The FAQ describes deriving a Bitcoin address from the Merkle root; the verification guide says OP_RETURN outputs have been used since Feb 15, 2021.
Workaround: Follow the verification guide, which covers both methods.
The GitHub repository the FAQ links for verification holds instructions, not code, and was archived on Mar 27, 2026.
The pages say the service is hosted in Switzerland by default and is eIDAS-compatible on request, but name no audit report.
OriginStamp publishes no price list. The docs FAQ says the price depends on the number of timestamps and proofs you request and asks you to email for an offer or a free test API key; the timestamp page leads to a meeting booking. So our scenario of 100,000 hashes a month cannot be priced from the public pages. The cost model is explained, though: hashes from many users share one Merkle tree per period, so the on-chain fee is split across them. Proof requests are a separate count in the pricing statement, so ask whether proofs are billed per hash.
Proofs stay valid without the vendor: the docs say existing timestamps remain verifiable if OriginStamp stops existing, and the verification guide gives the steps with the original file and the proof. Keep both, because OriginStamp does not back up your data.
From its public pages, OriginStamp is a long-running anchoring API with two chains, batching and webhooks. The price is an offer, and a few docs pages describe an older anchoring method.
| Limit | As recorded |
|---|---|
| What it anchors to | Bitcoin and Ethereum (Merkle root per batch) |
| Billing unit | Offer based on timestamps and proofs |
| Free option | Free web tool for single proofs; test API key on request |
| Reference scenario (100,000 hashes/mo) | Priced by sales |
| Proof you keep | Downloadable certificate or raw proof |
| Verify without the vendor | Manual steps documented |
| Only the hash leaves your systems | Yes |
| Qualified timestamps (eIDAS) | eIDAS compatibility on request |
| SOC 2 / ISO 27001 | Not stated |
| API and webhooks | REST API, batch hashes, webhooks |
| SSO | Not listed |
Read from the vendor's public pages on Oct 15, 2026. No hands-on run is published yet. How we check
We have not published a sign-up run for OriginStamp yet. The access facts above were read from its sign-up and pricing pages on Oct 15, 2026.
We have not published API calls for OriginStamp yet; access was not open to our agent.
OriginStamp lists 2 plans. Paid plans are priced by quote only.
Prices as listed, USD, excluding tax; observed 2026-10-15.
Source: docs.originstamp.com pricing page. Prices change; the observed date above is when our agent read them.
We read the pricing, fee, security, legal and docs pages of three data anchoring services on the same day and scored them on the same six indicators. How each one bills, what 100,000 hashes a month cost, and who should pick which.
