Encrypted data an attacker records todaycan be opened on Q‑Day.
Harvest now. An attacker can record your encrypted data as it crosses networks you don’t own, cheaply and without a trace.Decrypt later. The attacker only has to wait for Q‑Day, the day a quantum computer can unlock that data, and research keeps moving that day closer.2–4On the record. The White House warns of adversaries “collecting United States information now, and decrypting it later.”1Years of your data, exposed at once.
And suddenly, the liability is yours.
- TodayCapturedAn attacker copies your encrypted data off the network, unnoticed.
- For yearsStoredYour data sits in the attacker’s archive, waiting for Q‑Day.
- Q-DayDecryptedA quantum computer breaks today’s key exchange.5 Years of your recorded data become readable to the attacker at once.
You don’t need a quantum computer to stop this. The attacker does.
Unfortunately, if an attacker already has a copy of your data, no one can protect that copy, not even us.Everything you send after you switch to PacketLoq can be protected.
Every day your links run without PacketLoq adds to the attacker’s archive. Switch to PacketLoq, and let the attacker record. On Q‑Day, the recording still won’t open.
Q‑Day only decides when the attacker can open the recording. Executive Order 14412 warns that adversaries may already be collecting encrypted data to decrypt later.1 Quantum experts surveyed by the Global Risk Institute put the chance of Q‑Day within ten years at 28–49%, the highest in the report’s history.4
Executive Order 14412 requires post-quantum key establishment on high-value and high-impact federal systems by December 31, 2030, and directs a rule holding covered federal contractors to NIST’s standards by the same date.1
In 2025, Google’s Craig Gidney cut that estimate about twentyfold, with better math, not better machines.2 A quantum computer attacks the key exchange, not the AES‑256 that encrypts the data.
The secret never crosses the wire.
IPsec and TLS start every connection by agreeing on a key in the open. That method was invented in 1976 for computers that have never met. Your two sites already know each other, so PacketLoq skips that step, and the attacker has no key exchange to record.
- 1The key is placed in advance.It’s loaded at both ends, so it never travels over the link.
- 2Session keys stay inside the link.Nothing is negotiated in the open.
- 3Keys rotate on their own.Every gigabyte by default (customizable), with old keys erased from memory.
- A recording holds nothing to break
- No handshake for a quantum computer to attack
- Still safe after Q‑Day
PacketLoq’s approach is its own invention.Patent pending in the US, Canada and the EU.
The difference is the first two frames.
The same site-to-site link, recorded on IPsec and then on PacketLoq.
| No. | Source | Protocol | Info |
|---|---|---|---|
| 1 | 203.0.113.4 | ISAKMP | IKE_SA_INIT key exchange payload |
| 2 | 198.51.100.9 | ISAKMP | IKE_SA_INIT key exchange payload |
| 3 | 203.0.113.4 | ISAKMP | IKE_AUTH |
| 4 | 203.0.113.4 | ESP | SPI=0x8f2a1c04 encrypted |
| 5 | 198.51.100.9 | ESP | SPI=0x1d77b930 encrypted |
| … | ESP | every packet that follows |
| No. | Source | Protocol | Info |
|---|---|---|---|
| 1 | 203.0.113.4 | UDP | 9876 → 9876 Len=1422 |
| 2 | 198.51.100.9 | UDP | 9876 → 9876 Len=1422 |
| 3 | 203.0.113.4 | UDP | 9876 → 9876 Len=1422 |
| 4 | 198.51.100.9 | UDP | 9876 → 9876 Len=1422 |
| 5 | 203.0.113.4 | UDP | 9876 → 9876 Len=1422 |
| … | UDP | every packet that follows |
Your options for Q‑Day, compared.
Everyone else hardens the handshake. PacketLoq removes it.
Everyone else adds something
- 1Post‑quantum key exchangeA handshake that’s still recorded
- 2Post‑quantum pre‑shared keysStatic keys, changed by hand
- 3Hardware link encryptorsA new box at every site
- 4Key‑delivery servicesSomeone else in your key loop
- 5Quantum key distributionSpecial hardware and dedicated fiber
PacketLoq
Nothing to record, keys that rotate on their own, on hardware you already own.
1 No key exchange to record · 2 No new hardware · 3 No outside key service · 4 Works over any network · 5 Keys rotate on their own. Tap a row for details.
Categories, not vendors. “Varies” means it depends on the product and how it’s set up.
Why not just turn on post‑quantum IPsec?
Keep it. It comes in two forms, and PacketLoq runs under either.
A post‑quantum key exchange is harder to break, but it’s still sent, and still recorded.
Post‑quantum pre‑shared keys are the closest to our approach. But they’re static and handled by hand, and one major vendor’s guide says they don’t scale well across many sites.6 PacketLoq rotates keys on its own, under the VPN, router or firewall you already have.
Find the link you’re responsible for
PacketLoq protects links where you control both ends: your own sites, servers and cloud instances, or a partner under contract. For strangers on the open internet, keep TLS.
Protects links in any of these layouts
- Site to site
- Hub and spoke
- Mesh
- Client to server
Select your industry
Branch to core, and data center replication
Payment instructions and account records cross circuits you don’t own and must stay confidential for decades.
You own both ends, so PacketLoq fits without anyone else signing off.
- Confidential for7–30 years
- Sits underneathYour IPsec site-to-site
- Runs onServers you already run
Start with one branch link and a packet capture.
Talk to us about a pilotBetween hospitals, imaging and the data center
Patient records move between your sites all day and must stay private for a lifetime.
PacketLoq logs every key operation for your auditors.
- Confidential forA patient’s lifetime
- Sits underneathYour site VPN, on any circuit
- Runs onServers you already run
Prove any link is encrypted, from the appliance.
Talk to us about a pilotControl center to plant, substation or wellhead
Control protocols were built without security, and a private line doesn’t help if someone can tap it.
PacketLoq works at Layer 3, so the plant doesn’t change.
- Confidential forThe life of the plant
- Sits underneathYour control traffic, unchanged
- Runs onHardware the size of a paperback
Start with one control link and a packet capture.
Talk to us about a pilotCloud to cloud, and cloud to data center
Provider encryption stops at the edge of each cloud, so many teams pay a third party to bridge them.
PacketLoq runs the same on every provider, under your interconnect or in place of it.
- Confidential forYears
- Sits underneath, or can retireThird-party interconnect
- Runs onInstances you already run
Paying to bridge two clouds? Run the comparison.
Talk to us about a pilotSite to site, and ground segment to spacecraft
These links need key custody you can account for from generation to destruction.
PacketLoq separates red and black, keeps keys on a crypto ignition key, tracks each key by serial number, and speaks CCSDS for spacecraft.
- Confidential forDecades
- Sits underneathYour existing site-to-site encryption
- Runs onAir-gapped hardware
Your assessors can export the full key audit trail.
Start a conversationAny link where you control both ends
Retail, logistics, law, media, education, managed service providers: any business that runs links of its own.
If you control both ends, the link crosses a network you don’t own, and the data must stay secret for years, PacketLoq fits.
- Confidential forAs long as you need
- Sits underneathWhatever protects the link today
- Runs onServers you already run
Tell us about the link. We’ll tell you if it fits.
Talk to us about your linkOne binary, on servers you already run.
PacketLoq sits at the edge of each site. Everything behind it stays the same.
- Running in an afternoon
- Keys you control, custody you can prove
- Invisible to your applications
- Cryptography your auditors already trust
Built from experience. Shaped by what’s at stake.
PacketLoq is a small, senior team based in Seattle and working remotely.
Our founding engineers come from satellite ground systems and defense communications. Our product and go-to-market leaders have taken cloud platforms to market at scale.
PacketLoq began with a slow link: large transfers between two of the founders’ own sites slowed to a crawl. Fixing it meant rethinking how data in transit is protected.
- Based inSeattle, Washington
- What we buildEncryption for data in motion
- PatentPending in the US, Canada and the EU
- Team biosAvailable to customers and investors under NDA
- Design partnersTaking a small number now. Get in touch
- Talk to us[email protected]
Bring us a link and a packet analyzer
Tell us about one link: what it carries, its throughput and what sits at each end.