Code Timestamping Service Pricing for Private Repos
Shopping for a code timestamping service starts innocently enough — you compare a couple of pricing pages, see a free tier and a paid tier, and wonder what the catch is. Then you notice the catch: most of that pricing assumes your code is public. The moment your IP lives in a private repository, the economics change completely. You are no longer buying a feature; you are buying a confidentiality guarantee plus a piece of evidence that survives a courtroom.
This is a buyer’s guide for that decision. It covers the three cost models you’ll run into in 2026, what each Timestamp GIT tier actually delivers for private repos, how to reason about ROI against the cost of a dispute, and the questions to ask any vendor before you sign.
The Purchase Decision: What You’re Actually Buying
Private-repo timestamping belongs in your budget as a risk-management line item, not as a developer tool. Nobody buys it because it makes commits faster. You buy it because you want admissible proof that a specific piece of logic existed on a specific date — proof that a lawyer, an auditor, or a procurement team will accept.
There are three cost models on the market right now:
- Free-but-public-only tools. Zero cost, but your repository and its hashes are effectively published. Fine for open source, useless for trade secrets.
- Per-repo or per-seat SaaS. A recurring subscription per protected repository or per developer, usually with a managed integration.
- Self-hosted licenses. You pay for a license and run the whole pipeline on your own infrastructure.
Why private repos change the math: a public anchoring service is a non-starter when confidentiality clauses or internal policy forbid any third party from touching your code. That constraint pushes you toward vendors with a zero-knowledge architecture, and zero-knowledge is exactly where pricing gets interesting.
For the underlying mechanics, the short version is enough here: Git produces a one-way hash fingerprint of your repository state, that hash is anchored into Bitcoin, and you get back a .ots receipt. The full walkthrough lives on the Concept page — this article is about what you pay for it.
Keep five criteria in mind as you read the tiers below: price, what is automated, how much code exposure you accept, whether verification is independent of the vendor, and what audit artifacts you get out of the box.
What You Get at Each Tier: Open Source, Pro Agency, Enterprise ZK
Open Source — free
Public repositories only. This is genuinely useful if you maintain an open-source project and want to prove authorship or prior art on code the world can already read. It is not a path to protecting private IP, and any vendor telling you otherwise is selling you a false sense of security.
Pro Agency — $49/mo
This is the tier most teams with private code need. You install the GitHub App once, and it reads only the HEAD commit hash of each monitored repository. From there the workflow is fully automated:
- Automatic nightly anchoring — commits are batched and anchored into Bitcoin each night, with no per-commit action from your developers.
- Proofs in your own repo — the manifest and
.otsreceipts land in a dedicated timestamps branch or a shadow repository you control. - Verification badges for READMEs, with a public link anyone can use to check the timestamp.
- REST API access for status, audit ledgers, and per-date PDF certificates.
Private repositories require read-only access on the source repo and read-write access on the target repo where proofs are written. That access requirement is a real cost consideration, so ask about it explicitly.
Enterprise ZK — $199/mo
Enterprise ZK exists for organizations whose policy forbids handing even a commit hash to an outside service through a GitHub App integration. Instead, a 12-line GitHub Action runs on your own infrastructure and pushes only the commit hash to the Timestamp GIT API. The service never has read access to your source repository — you keep read-write access on the target repo only, and you install the Action yourself.
Docker self-hosted license
For air-gapped or maximum-security environments, Timestamp GIT is available as a Docker image and you operate the entire pipeline yourself. A quick-start Docker Compose setup looks like this:
services:
timestampgit:
image: rue1401/timestampgit:prod
ports:
- "8080:8080"
volumes:
- ./data:/app/data
restart: unless-stopped
valkey:
image: valkey/valkey:8
restart: unless-stopped
docker compose pull
docker compose up -d
docker compose logs -f timestampgit
The application is available at http://localhost:8080 after startup, and a setup wizard walks you through connecting your GitHub App and configuring your instance. Evaluation is straightforward: a time-limited demo license is available by submitting the request form on the Docker License page with your name, company, email, and optional phone number.
Which tier fits which buyer
| Buyer | Tier | Risk removed |
|---|---|---|
| Open-source maintainer | Open Source | Authorship disputes on public code |
| Freelancer with private libraries | Pro Agency | Plagiarism claims against reusable code |
| Agency delivering client work | Pro Agency | Payment and delivery-date disputes |
| Compliance-bound company | Enterprise ZK | Third-party access to commit hashes |
| Air-gapped organization | Docker self-hosted | External data plane entirely |
Cost/Benefit and ROI: Pricing a Proof Against a Lawsuit
Anchor the comparison on failure modes, not features. A patent troll demand letter, an employee dispute over when a feature was conceived, or a competitor’s “we developed this independently” claim all cost orders of magnitude more than any subscription on this page — and those are the cheap outcomes. Litigation is the expensive one.
What you are buying with that money is evidentiary weight. Internal Git logs and GitHub history look convenient until an audit asks who could have edited them. History that lives on servers you don’t own, in databases that can be rewritten, gets dismissed as self-serving. A Bitcoin-anchored proof is immutable and independently verifiable by anyone — including a party who has no relationship with the vendor.
The hidden cost of the DIY route is worth naming. Doing this manually means per-commit steps, protocol knowledge, and a workflow your developers have to remember. That is the hard way. The managed GitHub App does the same job automatically each night, with nothing to install on developer machines and no changes to how your team commits.
Compliance and procurement requests get cheaper too, because the artifacts are already there:
curl -s "https://timestampgit.dev/api/statusSummary/your-org/private-repo" | jq
curl -s "https://timestampgit.dev/api/audit/your-org/private-repo" -o audit-ledger.csv
curl -s "https://timestampgit.dev/api/report/your-org/private-repo/2026-10-09" -o certificate.pdf
A downloadable CSV audit ledger and per-date PDF certificates mean you answer a diligence request in minutes instead of assembling evidence from scratch. Embeddable verification badges do the same job publicly. Frame ROI as avoided cost and faster diligence — not as a checklist of features you may never use.
Upgrade Path: From Free to Pro to Enterprise ZK to Self-Hosted
- Start free on public repositories to see the workflow end to end and confirm that proofs land where you expect them.
- Move to Pro Agency ($49/mo) the first time a private repository needs protection. There is no migration project — the GitHub App is already installed.
- Move to Enterprise ZK ($199/mo) when policy forbids a third party from reading commit hashes at all. The GitHub Action keeps source in your environment.
- Move to self-hosting for air-gapped networks, data-residency requirements, or a mandate to run the full pipeline on infrastructure you own.
One operational reality applies at every tier: commits are batched nightly, and Bitcoin confirmation normally takes around 3 hours. Proofs are therefore written a few hours after the batch, not instantly at commit time. Plan your compliance timelines around that, not around a real-time guarantee.
Cloud vs Self-Hosted: Which Pricing Model Fits Your Team
| Managed cloud (Pro / Enterprise ZK) | Self-hosted Docker license | |
|---|---|---|
| Ops burden | None — nightly anchoring runs for you | You run timestampgit and valkey |
| Data plane | Vendor-hosted | Yours |
| Access model | GitHub App (read-only source) or GitHub Action (no source read) | Fully under your control |
| Audit artifacts | Badges, API, CSV, PDF | Same pipeline, operated by you |
| Best for | Most teams | Air-gapped, data-residency, or maximum-security mandates |
Both models share one important property: the proof itself relies only on SHA-256 and Bitcoin block data via OpenTimestamps. There is no proprietary lock-in, and verification can be done offline even if the vendor disappears. That is what makes this a purchasing decision rather than a dependency.
Practical guidance: most teams should start managed and only self-host when a compliance rule forces it. Self-hosting is a real operational commitment — you are running the stack, not just paying for it.
How to Evaluate Any Code Timestamping Quote
Five questions cut through most marketing pages:
- What does the service actually see? A managed GitHub App needs at least read-only access to the source repo. Enterprise ZK needs none.
- Where do proofs live? They should land in a dedicated timestamps branch or shadow repo you control — not only in a vendor dashboard.
- Is verification independent? Anyone should be able to check a
.otsfile against the Bitcoin blockchain without the vendor’s help. - What audit artifacts are included? Per-date PDF certificates, a full CSV audit ledger, and public badges.
- How is private-repo privacy handled? Status URLs for private repos append an encrypted HMAC, so only authorized users can view them.
If a quote can’t answer all five, the price is irrelevant — you’re buying something you can’t use when it matters. Current tier details are on the pricing page.
FAQ
Is there a free tier for private repositories?
No — the free Open Source tier covers public repositories only. Private repositories require Pro Agency ($49/mo) or Enterprise ZK ($199/mo). If you need to keep everything on your own infrastructure, the Docker self-hosted license offers a time-limited demo license for evaluation.
Why does Enterprise ZK cost more than Pro Agency if it uses a GitHub Action?
Enterprise ZK changes the trust model: the 12-line GitHub Action runs on your infrastructure and pushes only the commit hash, so the service never has read access to your source repository. You’re paying for zero code exposure, not for extra features.
Do I need to install anything on developer machines?
No. You install the GitHub App once, and every commit to a monitored repository is anchored automatically each night. There are no CLI tools, no per-commit commands, and no changes to how your developers work.
How long until a timestamp is confirmed, and what do I get as proof?
Commits are batched nightly, and Bitcoin confirmation normally takes around 3 hours, so proofs are written a few hours after the batch. You receive a manifest and an immutable .ots receipt in a dedicated timestamps branch or shadow repository, plus access to PDF certificates and a CSV audit ledger.
Conclusion
Private-repo timestamping is priced against the cost of a dispute, not against the cost of a competitor’s feature list. The free tier proves the workflow on public code, Pro Agency ($49/mo) covers private repositories with automatic nightly Bitcoin anchoring, Enterprise ZK ($199/mo) removes third-party access to hashes entirely, and the Docker self-hosted license covers air-gapped environments.
If you want the managed path with nothing to install on developer machines, start with Timestamp GIT — install the GitHub App once and let the nightly batch do the rest. If you’re already evaluating alternatives, the related reading below goes deeper on specific scenarios.
Related posts
- OpenTimestamps Alternatives: Managed Git Timestamping
- Protecting Agency Code Deliverables With Blockchain Proof
- Git Commit Timestamp Proof for Patent Disputes