Decentralized digital sealing — content stays on your device; only SHA-256 fingerprints enter the pipeline.
Batches are written to a public Git ledger, anchored with OpenPGP detached signatures (SIP v1).
| Layer | Role |
|---|---|
| Backend | Stateless Go API: queue → batch → JSONL ledger on GitHub → GPG-signed receipts |
| Frontend | React client: local hashing, seal flow, client-side ledger + signature verification, PDF certificate |
| SDKs | Python (PyPI), Node.js, PHP, plus a standalone Go CLI for automation |
Adjust links if your repo names differ inside the org.
| Repo | Description |
|---|---|
| backend | POST /v1/seal, status + SSE, public config, Git + GPG worker |
| frontend | Vite + React 19 + Tailwind v4 — Forge, Verify, Explorer, certificates |
| sdk | Official clients: smart hashing, polling, retries, mock transports |
| ledger | Public append-only JSONL ledger (GitHub is the source of truth) |
- API health:
GET /healthz - Python SDK:
pip install seallayer— PyPI - Verification model: Signatures are verified client-side against the pinned public key and the ledger snapshot at
commit_sha.
- No raw file uploads to SealLayer for sealing — hashes only.
- Ledger is transparent; receipts link to verifiable Git commits.
- Run your own backend + ledger repo for full control.
Issues and discussions live in each repository. For security-sensitive reports, use the contact method listed on seallayer.com if available.
This README is rendered on the organization Overview via SealLayer/.github → profile/README.md.