Timestamp GIT

← All posts

2026-10-25

Git Commit Timestamp Service Pricing: Which Tier Fits Your Team

Git Commit Timestamp Service Pricing: Which Tier Fits Your Team
timestamp git blockchain proof

Git Commit Timestamp Service Pricing: Which Tier Fits Your Team

If you have started comparing git commit timestamp service pricing, you have probably noticed that most price pages tell you what a plan costs and almost nothing about what decision you are actually making. For a timestamping tool, the decision is not “which feature list is longest.” It is: how much of my repository surface needs coverage, how much source code am I willing to expose to a third party, and where does the software have to run to satisfy my security review?

This is a buying guide. It walks through Timestamp GIT’s four purchase paths — Open Source (free), Pro Agency ($49/mo), Enterprise ZK ($199/mo), and the Docker self-hosted license — and shows where each one pays for itself. If you want the underlying cryptography explained first, read What Does a Bitcoin Timestamp Prove About Your Code? — this article stays on cost and fit.

The Purchase Decision: What You’re Actually Buying

You are not buying Bitcoin transactions. You are not buying a protocol license. You are buying automated, court-ready proof of existence with zero developer overhead.

Timestamp GIT is a managed SaaS plus a GitHub App. You install the App once, point it at a repository, and every commit to that repository is anchored into Bitcoin automatically each night — hashes batched, Merkle-rooted, and committed to a Bitcoin block via the OpenTimestamps protocol. No developer runs a command. No one on your team needs to learn the protocol. The proof artifacts (.ots receipt files and manifest files) land in a dedicated branch or shadow repository, and verification happens through the product’s pages, badges, and REST API.

That framing matters for budgeting, because it means the cost of every tier is the cost of coverage and compliance, not the cost of engineering time:

  • Repo visibility coverage — public only, or private too?
  • Zero-knowledge posture — does the service ever see your source, or only hashes?
  • Audit artifacts — do you need downloadable CSV ledgers and PDF certificates for clients or auditors?
  • Placement — cloud, or your own Docker host?

Four paths answer those four questions:

Path Price Repo coverage Runs where
Open Source Free Public repositories Cloud (GitHub App)
Pro Agency $49/mo Private repositories Cloud (GitHub App)
Enterprise ZK $199/mo Private, zero read access Cloud + GitHub Action in your infra
Docker self-hosted License required (demo available) Your instance, your data Your infrastructure

Everything else — the three-step fingerprint → anchor → proof model, the nightly cron worker, the Merkle tree — is identical across tiers. For the why behind that model, the admissibility discussion and the automation walkthrough are the right follow-ups. Here, we talk money.

What You Get at Each Tier: Feature Breakdown

Open Source — free, public repositories

The free tier is a real tier, not a trial. It includes:

  • Installation of the GitHub App on your public repositories
  • Automatic nightly anchoring of commit hashes into Bitcoin
  • Verification badges you can embed in your README
  • Public status pages showing proof longevity, earliest anchor date, daily regularity, Bitcoin block and transaction data, and a calendar heatmap

For an open-source maintainer, this is straightforward reputation insurance: your public commit history stops being “a GitHub log someone could argue about” and becomes a Bitcoin-anchored record anyone can check against a badge in your README.

Pro Agency — $49/mo, private repositories

Pro Agency unlocks the same GitHub App workflow for private repositories, which is where client work, trade secrets, and pre-filing patent work actually live. On top of coverage it gives you the artifacts that non-engineers ask for:

  • Audit ledger as CSV — the full list of anchored proofs for the repository
  • PDF certificates — a per-date certificate you can attach to a delivery email, an invoice, or a dispute file

In Standard (GitHub App) mode, the App reads only the HEAD commit hash of your monitored repository. It writes the proof branch into the same repository or into a separate shadow repository, which means the GitHub permission model needs read-only access to the source repo and read-write access to the target repo. Nothing else is read. This is the tier most agencies and freelancers land on, because it directly supports the payment-dispute scenario.

Enterprise ZK — $199/mo, zero code access

Enterprise ZK changes where the hash is produced. A 12-line GitHub Action runs on your infrastructure and pushes only the commit hash to the Timestamp GIT API. Your source never leaves your environment, and the service holds no read permission on the source repository at all — only read-write on the target repository where proofs are written. All Pro features come along.

This is the tier for teams whose security review says “no third party has read access to source,” or whose compliance function wants the data flow documented as one hash, outbound.

Docker self-hosted license

For air-gapped and maximum-sovereignty environments, the whole application ships as a Docker image. 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 on first launch walks you through connecting your GitHub App and configuring the instance. Evaluation uses a time-limited demo license, requested through the Docker License page with your name, company, email, and optional phone number; a demo license file can be downloaded. Production requires a purchased license.

Cost/Benefit and ROI: When Does Each Tier Pay for Itself?

Price the risk first. The three failure modes this product addresses — a non-practicing entity filing broad patents on technology you already shipped, a departing lead developer disputing when a feature was conceived, and a competitor’s “we developed this independently” claim — are all resolved in legal hours. A single month of any tier is a rounding error against that, which makes every tier cheap insurance. The real question is which insurance you need.

  • Open Source (free). Pays for itself the moment a badge in your README makes your project history independently verifiable. No credit card, no procurement conversation. If all your code is public, you can stop reading here and go install the App.
  • Pro Agency ($49/mo). At roughly $588 a year, this is typically less than an hour of legal consultation — and it is the tier that produces the PDF certificate an agency attaches when a client goes quiet on an invoice. One defended payment dispute covers a decade of the subscription. It also covers private repositories for multiple client projects, which is exactly the workload an agency runs.
  • Enterprise ZK ($199/mo). Around $2,388 a year buys you an auditable answer to “where does our source code go?” — the answer being “nowhere; only hashes leave.” Compare that to the internal cost of standing up your own timestamping pipeline, documenting it, and keeping a legal hold process around it, and the calculus is usually obvious. It is also the cheapest way to keep the automated nightly workflow while removing read access entirely.
  • Docker self-hosted. Here the license cost replaces a cloud dependency rather than adding one. The benefit is measured against what an exception to your data-residency or air-gap policy would cost — often far more than the license itself, because exceptions require review cycles every time they come up.

Worth knowing what you actually receive, regardless of tier:

# Anchored block info, commit counts, and a Shields.io-ready summary
curl -s "https://timestampgit.dev/api/statusSummary/acme/payments-service"

# Full audit ledger as CSV
curl -sL "https://timestampgit.dev/api/audit/acme/payments-service" -o audit.csv

# PDF certificate for a specific anchored date
curl -sL "https://timestampgit.dev/api/report/acme/payments-service/2026-10-24" -o certificate.pdf

Private repositories append an encrypted HMAC to status URLs, so only authorized users can read them — the HMAC is specific to the server instance.

Upgrade Path: Cloud vs Self-Hosted and When to Switch

The tiers are designed to be walked, not chosen once:

  1. Start with Open Source for public repositories. You get the GitHub App, nightly anchoring, badges, and public status pages with no commercial commitment.
  2. Move to Pro Agency on the day your first private client repository needs coverage, or when a client asks for a certificate of authorship rather than a link.
  3. Move to Enterprise ZK when a security review or compliance requirement forbids third-party read access to source. You install the GitHub Action; the service keeps read-write on the target repository only, and the source repository is untouchable from our side.
  4. Move to Docker self-hosted when you need air-gapped operation or full data sovereignty. The same setup wizard handles GitHub App connection and instance configuration.

One operational detail to plan around: the nightly worker batches pending hashes at midnight, builds the Merkle tree, and anchors the root — but Bitcoin confirmation normally takes around three hours. So proofs are written a few hours after the batch, not instantly. A tier change therefore takes effect with the next nightly run, and a same-day purchase will not retroactively stamp today’s commits.

The reassuring part is that upgrading never changes how you prove prior art. Every tier produces the same thing: a manifest of commit hashes, a Merkle proof, and an .ots receipt anchored in a Bitcoin block. The proof relies only on SHA-256 and Bitcoin block data — no proprietary format, no lock-in — and the verification page at /verification/{user}/{repo}/{date} computes the multi-level Merkle chain locally in your browser, so nobody sees what you verify.

FAQ

Can I switch between pricing tiers as my team grows?

Yes. You can upgrade from Open Source to Pro Agency when you need private repositories, or move to Enterprise ZK when compliance requires zero code access. Downgrades are also possible; your existing .ots proofs remain valid and verifiable forever.

What happens to my timestamps if I cancel my subscription?

Your .ots receipt files and Merkle proofs are stored in your repository (or shadow repo) and are independently verifiable against the Bitcoin blockchain. Cancelling stops new anchoring, but all past proofs remain mathematically valid and court-ready.

Is the free tier really free for public repositories?

Yes. The Open Source tier is free for public repositories and includes the GitHub App, automatic nightly anchoring, verification badges, and public status pages — no credit card required.

How does the Docker self-hosted license work?

You can request a time-limited demo license via the Docker License page. For production, a license is required. The Docker Compose setup uses image: rue1401/timestampgit:prod and image: valkey/valkey:8, and a setup wizard guides you through connecting your GitHub App.

Conclusion: Pick the Tier That Matches Your Risk Profile

Match the tier to the exposure, not to the feature grid:

  • Open Source — public code, open-source reputation, zero budget.
  • Pro Agency — private repositories, client deliveries, PDF certificates and CSV audit ledgers.
  • Enterprise ZK — compliance-heavy teams that cannot grant read access to source.
  • Docker self-hosted — air-gapped or data-sovereignty requirements.

Because Timestamp GIT is a managed GitHub App, every tier is priced on coverage and compliance rather than developer time. There is no CLI to learn, no manual step to forget, and no per-commit engineering cost hiding behind the subscription line.

Install the GitHub App and start on the free tier today, request a demo license if you need to evaluate the self-hosted path, and upgrade only when a private repository or a security review forces the question.

Related posts

EU label: AI-generated content