DEV Community

Tommy
Tommy

Posted on AI-assisted

Put your files anywhere. Keep the only key.

Europe is busy discovering data sovereignty. We built a €5 key around it, and we didn't do it for Brussels.

Europe has spent the last year talking about data sovereignty. In November 2025 the member states signed a Declaration for European Digital Sovereignty. In June 2026 the Commission proposed a Cloud and AI Development Act. Law firms now write long notes about the US CLOUD Act, and analysts have a word for clouds that call themselves sovereign while someone else keeps the keys: sovereignty washing.

Good. We're glad the conversation is happening. But we didn't build Crypt-in because of any of it, and we won't change it to fit whatever a regulation says next year.

The idea fits in one line: if a file is encrypted and only you hold the key, it can live anywhere. On a US cloud. On a friend's NAS. On your worst competitor's server. They hold bytes. You hold the key.

How we built it

Crypt-in is file encryption where the key lives on a small USB dongle. The dongle is an ESP32-S3, a chip that costs about €5.

  • The keys are born in your hands. At first boot the dongle generates its own keys from hardware entropy. The firmware ships with no keys and no identity. We have never seen anyone's 24-word recovery seed, and we can't.
  • Activation can be anonymous. No email, no name, no tax ID if you don't want to give them.
  • We can't switch you off. Opening your files never needs our server and never expires. The licence pays for encrypting new files. If we disappeared tomorrow, every file you've already encrypted would still open.
  • Buy the chip anywhere. Any ESP32-S3 with native USB, at least 8 MB of flash and two USB-C ports can become a dongle. We don't care where it came from.
  • Pull it out and it locks. Unplug the dongle and the session closes in under 5 seconds.
  • Tampering shows. Every .crin file, header included, is authenticated with AES-GCM. Change one byte and the file refuses to open.

So the encrypted file can travel anywhere: Gmail, Google Drive, a USB stick, a NAS. One of the use cases on our site is two twin dongles, one with you and one with a partner abroad, sending accounts over ordinary email that only the two of them can open.

We attacked it before you did

A product that asks you to trust nobody shouldn't ask you to trust us either. So we gave an AI attacker our client source code, the tools, admin rights and a real dongle, and ran three sessions. Every finding is published, the open ones too, and the edited transcript is on GitHub: cryptin-redteam-2026-08.

It was our own test, run with an AI. It is not an independent audit, and we say so on every page.

What it does not do

This section is as long as the one above, on purpose. A sovereignty pitch that hides its limits is just marketing.

  1. Names and sizes are visible. Whoever stores your .crin files sees the file name, its exact size, and which dongle encrypted it (the dongle's public key sits in the header). They can't see the content. For an encrypted folder, they can't see the names of the files inside.
  2. They can delete your files. Holding the key gives you control over who reads, not over whether the file still exists. Keep two copies in two places.
  3. They can hand you an older version. An older .crin of the same file, encrypted by the same dongle, still opens without a warning.
  4. The original stays on your PC. The app writes the .crin next to the original and doesn't delete it. Opening a file writes it in clear on your disk while you work.
  5. The beta is a beta. Today there's a free developer beta (until 31 March 2027): you flash your own board. Its firmware is a -dev build. The eFuses aren't burned, so someone holding the dongle can read its flash. And a PC where you've unlocked the dongle with your PIN can still ask it for the key. Production dongles derive and use the file key inside the chip, and close both doors.
  6. It's a €5 chip, not a secure element. That's a choice: cheap, replaceable, sourced anywhere. It also means we rely on the chip's own protections, not on certified tamper-resistant hardware.
  7. Lose both, lose everything. Lose the dongle and your 24 words, and your files are gone. Nobody can recover them, us included. That's what sovereignty costs.
  8. Windows 11 (64-bit) only, for now. Linux has a command-line tool for x86-64. macOS is planned, with no date.
  9. About GDPR. If a laptop with encrypted client data is stolen and the key wasn't compromised, Article 34(3)(a) can spare you from notifying each client. Whether you still have to notify the supervisory authority is a separate question: ask your lawyer, not a file-encryption vendor.

Where it's going

Today: personal file encryption. Next, a shared vault for a small office network, then encrypted virtual disks. The only date we commit to is the ready-made Kit: April 2027, €55 with six months of licence, then €30 a year to keep encrypting new files.

We don't sell shares, and we never will. An investor can share in the profits, never in the control: nobody can buy a say in how Crypt-in handles your keys. And no hero is coming to save anybody's data. Just a small Italian shop building a key you can hold in your hand.

Where do your most sensitive files live today, and who holds that key?

→ Developer beta, free: cryptin.lake8.dev/beta/
→ The Kit, in plain words: cryptin.lake8.dev/start/

Top comments (0)