Squyr Squyr. Bilateral Cryptographic Data Exchange
SESSION ACTIVE
SIGN IN ↗
Squyr. ✕
Home Technology Platform Demo
BILATERAL CRYPTOGRAPHIC INFRASTRUCTURE

Encrypt first.
Send second.
Trust no one in between.

Squyr is a bilateral cryptographic infrastructure for sensitive data — patient records, financial documents, identity proofs. Your data never leaves your server unprotected. Two locks on every piece of data. Both parties hold one key each.

● No master key ● No backdoor ● Ed25519
See the demo → Register Account
Safety deposit box
Two locks. Two keys.
Sender holds Key A — sealed
Recipient holds Key B — sealed
Both keys required to unlock

What Squyr Is

Squyr is a cryptographic protocol for healthcare data partnerships. Identifiers are hashed client-side using SHA-256. Tokens are encrypted with bilaterally-derived AES-256-GCM keys. Nothing personally identifiable ever crosses between parties.

Both parties contribute key material. Neither side can unilaterally decrypt the exchange. The primitives are standard: SHA-256, HKDF-SHA256, AES-256-GCM, Ed25519. All FIPS 140-2 compliant. All published RFCs. Compatible with standard identity infrastructure.

Squyr was developed by Silver Mountain Ventures, LLC to enable healthcare data partnerships at production scale while staying compliant with HIPAA, BAA constraints, and state-level health privacy regulations.

Download Whitepaper ↗

Every breach happens for the same three reasons.

Hospitals send patient records over email. Lenders exchange tax returns through portals built in 2009. Companies store Social Security numbers because "that's how verification works."

✗
Trusting the network.
TLS terminates somewhere. Email servers store copies. Faxes still happen.
✗
Trusting the vendor.
Portals, clean rooms, identity verifiers — every one holds a master key.
✗
Trusting the database.
Once data lands, someone owns the breach surface. Forever.
Squyr eliminates all three.
THE MOAT · §05

One trust root. Three capabilities.

Squyr isn't three separate products — it's one platform with three capabilities. Clone any surface, and the moat stays intact. The Ed25519 keypair that anchors PHI Shield also anchors Email Shield and SSN Shield.

One compliance posture. One audit chain. Three modules. All bilateral.

Ed25519 Keypair · shared trust root
SQUYR · Platform ● LIVE
Bilateral health data exchange
MAIL · Email Shield ● IN DEV
Pre-send DLP + bilateral encryption
VERIFY · SSN Shield ● IN DEV
Zero-knowledge SSN verification

Reference documentation

Non-proprietary. Freely shareable with security, legal, and engineering teams during partner evaluation.

DOCUMENTATION 8-Step Flow Technology · Interactive protocol breakdown. Data never leaves your server — client-side hashing, bilateral encryption, Ed25519-signed transmission. Explore → LIVE DEMO See it in your browser Real Web Crypto API operations on synthetic patient data. Five cryptographic moments. No network calls. Run demo → PDF Architecture Guide System overview, component architecture, integration patterns, and deployment considerations. Download →
Shield Products

Three Shields. One trust root.

PHI Shield, Email Shield, and SSN Shield — one Ed25519 bilateral keypair, one audit chain, all running through the same cryptographic infrastructure.

SSN SHIELD ● IN DEV
Identity verification without identity exposure. Zero-knowledge SSN verification — yes/no + cryptographic proof, your company never sees the number. Patent-pending.
● No SSN stored Explore →
PHI SHIELD ● LIVE Bilateral health data exchange. Client-side hashed. Patient records hashed client-side with SHA-256, encrypted with bilaterally-derived AES-256-GCM keys. Raw PHI never crosses the wire.
● HIPAA · BAA Explore →
EMAIL SHIELD ● IN DEV
Pre-send DLP + bilateral encryption. Document and message exchange with data loss prevention before transmission — encrypt with bilateral keys, recipient holds the only key that unlocks it.
● Bilateral AES-256 Explore →
HIPAA·FIPS 140-2·BAA Compatible·SOC 2 Type II Silver Mountain Ventures, LLC·15.3M+ T3 Records·2026–2046