§1
Signed receipts
A verifier can check a receipt's signature and bound fields against the selected signing key.
Security
We sell governance. So here is ours.
See how GateCore checks routed requests and produces signed records your team can inspect.
REQUEST CONTROLS AND VERIFIABLE EVIDENCE
What a signature can establishCheck the record.
Check the record.
Know its limits.
A valid signature establishes integrity under the signing key. It does not establish a real-world delivery or a compliance outcome.
Open the signed sampleSample data is fictional
Fail-closed posture
Required checks come before execution.
Configured fail-closed paths refuse a request when a required check cannot complete.
The rule
One failure, one outcome.
- Unverifiable input is refused, not given the benefit of the doubt
- A degraded component stops rather than running weaker
- A partial failure keeps none of what succeeded
Why it's the default
The expensive failure is a fast, wrong yes.
A slow no costs a retry. A confident, wrong yes costs money and trust.
The evidence chain
Inspect the controls. Verify the record.
Ed25519 signatures and SHA-256 hash chains, deliberately unoriginal. Every signed format is versioned, so the algorithms can evolve without breaking today's receipts.
§2
Hash-chained ledger
Hash-chain checks expose inconsistent changes to the recorded chain. Independent anchors provide a reference for checking its integrity.
§3
Consent & lead evidence
Content hashes and request records. Confirm retention requirements and provider-side filtering for the integration.
Use signed receipts and audit records to review routed requests and their recorded outcomes.
Isolation & identity
A caller proves what it is. It never decides what it's trusted to do.
Multi-tenant systems fail quietly at the boundary. Identity, trust, and access never come from the caller.
01
TENANT ISOLATION
Adversarially tested. Public responses never reveal whether a resource exists.
ENFORCED
02
RATE & SIZE LIMITS
Rate-limited and size-capped at edge and application.
DUAL-LAYER
03
AGENT IDENTITY
Resolved server-side. A caller says what it wants, never who it is.
SERVER-RESOLVED
Perimeter & credentials
Operator access requires a signed-in session and per-route authorization.
The operator console and its credentials are the highest-value target we run. This section describes sign-in for GateCore staff on our own console. It is not customer single sign-on.
Production access
Operator sign-in, then per-route authorization.
- The operator console requires a signed-in operator session (WorkOS) and per-route authorization checks.
- Host access is tailnet-only: SSH is closed to the public internet at the cloud firewall
- Databases and internal services are never exposed to the internet
Secrets & credentials
Nothing plaintext, nowhere.
- Secrets are encrypted at rest
- No plaintext credential exists in the codebase
Supply-chain risk, handled
The quietest attack surface, kept deliberately small.
Six controls, exercised in CI on every change rather than audited once.
01
STATIC WEBSITE
Static HTML. No package manager, no build step, no dependency tree to poison.
02
4 RUNTIME DEPS
The operator console runs four. Adding one is a reviewed decision.
03
IGNORE-SCRIPTS
Disabled for every npm install. Install scripts never execute.
04
LOCKFILE-EXACT
CI installs exactly what the committed lockfile says.
05
7-DAY COOLDOWN
Updates wait seven days, then land as one human-reviewed batch.
06
PINNED PYTHON
Pinned per-service requirements. CodeQL on every pull request.
Full dependency review 2026-07-11: zero advisories, production and full tree.
Internal security assessments in 2026-07 and 2026-08 (staging), with findings tracked to closure. No third-party audit or certification. Provisional patent filed 2026-07-24.
FOUND SOMETHING? Reports go straight to the founder: security@gatecoreai.com. Full terms: security.txt.
Certifications
Implementation evidence and certification status.
Inspect the receipt format and verifier, then ask for deployment evidence during your security review. Technical verification and third-party certification are separate.
Signed receipt verificationIMPLEMENTATION
Hash-chained settlement ledgerIMPLEMENTATION
Public key endpointIMPLEMENTATION
SOC 2 Type IINOT CERTIFIED
Third-party certification, if obtained, would be separate from the technical controls described here.
Get started
Bring your security team. We like it when they're picky.
Bring your hardest questions. Every answer points at something you can check yourself.
Request a demo