Stamp Your Deliveries

Do you deliver sensitive or critical code — or protect electronically what you sell? Struggling with timestamp APIs or complex tools?

Get legally qualified, eIDAS-compliant delivery proof in 15 minutes. Your source code never leaves your infrastructure in plaintext.

Get started →

1. Create your account

No email. No password. Your browser generates a cryptographic key stored only on your device.

No personal data collected — RGPD Article 25 by design.

STAMPED_TOKEN

(sign in to reveal)

STAMPED_REGISTRY_ID

(sign in to reveal)

STAMPED_ENCRYPTION_KEY

Generate locally — never transmitted to Stamped:

openssl rand -base64 32

⚠ Save this key securely. Stamped never sees it — lost key = lost access to your encrypted payload.

2. Add GitHub Secrets

Go to your repository → Settings → Secrets and variables → Actions → New repository secret

  1. Add STAMPED_TOKEN with the value shown on the left
  2. Add STAMPED_REGISTRY_ID with your registry UUID
  3. Run openssl rand -base64 32 locally and add the output as STAMPED_ENCRYPTION_KEY — this key never leaves your machine
# .github/workflows/stamped.yml
name: Stamp Delivery

on:
  push:
    branches: [ main ]

jobs:
  stamp:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: foreground-team/stamped-github-actions@v1
        id: stamp
        with:
          token: ${{ secrets.STAMPED_TOKEN }}
          registry-id: ${{ secrets.STAMPED_REGISTRY_ID }}
          encryption-key: ${{ secrets.STAMPED_ENCRYPTION_KEY }}

      - name: Print delivery proof
        run: echo "✅ ${{ steps.stamp.outputs.verify-url }}"

3. Add the workflow file

Create .github/workflows/stamped.yml in your repository:

  1. Go to your repository on GitHub
  2. Click Add file → Create new file
  3. Type .github/workflows/stamped.yml as the filename
  4. Paste the workflow on the left and click Commit changes

The action encrypts your repository with AES-256-GCM, uploads the payload, and acquires an eIDAS-qualified RFC 3161 timestamp.

Source: foreground-team/stamped-github-actions

⏳

Waiting for your first delivery…

Push a commit to trigger the workflow

4. Push a commit

Commit any change and push to your main branch. The GitHub Action will run automatically.

Expected time: ~30 seconds

  • GitHub Actions encrypts your repository
  • Stamped API receives the SHA-256 hash
  • Evidency TSA issues a qualified RFC 3161 timestamp
  • Your encrypted payload is locked in S3 Object Lock COMPLIANCE

✅ Your first delivery is stamped

You now have cryptographic, legally qualified proof of delivery.

Built for regulated industries

🔐 BYOK

Your encryption key never leaves your machine. Stamped only sees a SHA-256 hash.

📜 eIDAS Qualified

RFC 3161 timestamps from Evidency, ANSSI-listed TSP. Legally recognized in all 27 EU member states.

🇫🇷 French Sovereignty

Scaleway Paris infrastructure. Iliad group. Not subject to US CLOUD Act.

🔒 Immutable Storage

S3 Object Lock COMPLIANCE mode. Retention enforced at infrastructure level — no override possible.

👤 Zero PII

No email. No name. Opaque UUID identity only. RGPD Article 25 — privacy by design.

🔓 Open Standard

RFC 3161 standard. Verify independently with openssl ts -verify. No vendor lock-in.

🏥 DORA & NIS2

Supports audit requirements for healthcare, aerospace, and critical infrastructure operators.

✅ Verifiable Forever

Public proof URL. Anyone can verify authenticity and delivery time — without decrypting your code.