Vizini started as a personal proof-of-concept: "Could I design an encryption system that intentionally breaks predictable block patterns by using an index of keys and changing keys between each block?"
The result was surprisingly effective — so effective that I decided to share the alpha version publicly. Rather than relying on a single shuffled alphabet, Vizini uses a "keyring" of 256 shuffled keys. The sequence of which key gets used at each block is derived from the content itself, making pattern recognition practically impossible.
At its core, Vizini is based on an 8-bit substitution cipher — a design choice made intentionally. While simple 8-bit substitution ciphers are notoriously vulnerable to pattern recognition and frequency analysis, Vizini flips this weakness on its head by constantly switching between 256 shuffled keys in a non-linear, content-driven sequence. This completely defeats the classic attack vectors these ciphers usually succumb to.
My wife (who does cryptanalysis for fun) and a few members of the hacking community have taken swings at trying to crack it. The general consensus so far? It’s almost as effective as using a one-time pad — which is exactly the kind of outcome I love to see.
Beyond just building an "unusual" encryption tool, Vizini exists to get people thinking about ways to further obfuscate encrypted data, and how these ideas might be applied to other cipher methods or inspire new experiments. It’s not about chasing profit or building a commercial product; it’s about curiosity, freedom, and pushing the edges of what encryption can look like.
The system supports an optional password on top of the key file. There is a known bug affecting how this optional password is handled (it loses the first character), so it's still functional but not entirely correct. Given the sheer scale of the keyspace (which is astronomically large), the password is arguably just one more thing you can forget (or lose) — rather than a core security requirement.
Vizini is fully portable — it doesn't need to be installed and will happily run directly from a USB thumb drive. It creates (or appends to) a vizini.log file in the same folder as the program, which records filenames, keys, and passwords used. This feature exists for those of us with "Swiss cheese" memory, helping you keep track of which original files you’ve encrypted, their corresponding encrypted outputs, and which keys and passwords (when applicable) were used — all without guesswork. And if you don't want it, the log can be easily deleted at any time.
Vizini is a personal passion project, maintained in my spare time with occasional help and moral support from close friends and my wife. Updates happen when life allows.
If you're looking for a polished, enterprise-grade encryption suite, look elsewhere. But if you're interested in experimental cryptographic concepts and want to see a different approach in action — welcome to Vizini. Thanks for visiting — and for thinking outside the block.
Q — Why does it say I can “decrypt” a file that hasn't been encrypted yet?
A — Because you CAN. What it will do is effectively encrypt the file in reverse (so “encrypting” the resulting file will effectively decrypt it). This was an intentional design feature.
Q — What happens if I use the wrong key to decrypt?
A — The program will run normally, but the output will be unreadable.
Q — What happens if I use the wrong password when decrypting?
A — The program will run normally, but the output will be unreadable.
Q — How strong is this encryption?
A — Cryptographic strength can be tricky to calculate. Because the program will always run, attempts at cracking (even if they also have the same program) would need to be manually checked to see the results, and they cannot ever be sure if they got an incorrect result or have successfully decrypted the file to find the contents were encrypted (layered encryption).
Q — How many keys are there?
A — It would be an understatement to say that there are more possible keys than there are insects on the planet. The number is more than one hundred thousand digits long. To get the exact number of valid keys, solve this equation: (256!)^256.
Q — What happens if I lose my key file, can you recover it for me?
A — No. Your files are YOUR responsibility, including your keys.
Q — Can I share my key(s)?
A — It's yours, do whatever you want with it. If you're intending to send encrypted files to other people, then they'll need the key you used to decrypt those files, right?
Q — Why does it create a log?
A — For users who have Swiss-cheese memory. If you don't want it, delete it.
Q — Where can I get private keys?
A — Use the Key Cutter program found below and randomly generate as many as you like.
Q — Can Vizini be audited?
A — Yes! The entire source code is available on GitHub for anyone to inspect. We encourage audits and feedback. Security through transparency is a core principle of this project.
Q — Is Vizini meant to replace other encryption tools like GPG?
A — No. Vizini is an alternative approach, not a drop-in replacement. It offers a unique model and experimental design for those interested in exploring different cryptographic paradigms.
Q — What operating systems are supported?
A — Vizini is compiled for Windows and runs well on Linux using Wine. There is no official macOS support. If it works for you, great — but there’s no dedicated support for Apple’s locked ecosystem.
Q — Is there a command-line version?
A — No. Vizini is a graphical tool only. There is no console version at this time.
Q — Can I use this for highly sensitive or life-critical data?
A — No security tool is foolproof. You should carefully evaluate whether Vizini fits your specific security model before using it for highly sensitive or life-critical data.
This file has been encrypted using Vizini with a private key (no password). The file type is unknown — part of the fun is figuring that out, too.
The key used for this challenge was intentionally deleted. There is no recovery option, no backup, and no internal storage of the original filename or other metadata. Vizini treats filenames as arbitrary — because for its purpose, they are.
You may use any hardware, software, or approach you can get your hands on.
Collaboration is encouraged; team up, share ideas, or go it alone if you prefer.
The first person or team to successfully decrypt and return the original file to team@vizini.app will earn eternal bragging rights (and probably a few stunned head nods from the rest of us).
Includes Any.keÿ, Car.keÿ, House.keÿ, Music.keÿ, Sample.keÿ, and Skeleton.keÿ — all zipped to preserve special characters.
Download 6_Sample_Keys.zipIf your system supports it, you can also download individual keys below. (Not recommended on Windows.)
Hey! I'm Tumblefluff — creator and maintainer of Vizini; creative autistic weirdo, lifelong tinkerer, puzzle solver, maintenance technician, CAD designer, hobbyist coder, and encryption enthusiast. I love fixing things that are broken, turning weaknesses into strengths, and exploring ideas that live a bit outside the mainstream.
I lend moral support, and provide cryptanalysis. While I prefer to stay behind the scenes, I'm always nearby helping shape ideas.