Secret Codes is where I keep the small tools I've built for myself — a public availability shadow (free/busy from my calendar, no event details), an MCP endpoint (so agents can read the same shadow on my behalf), and a couple of QR utilities (make a code for any URL). Nothing here is trying to be a product. It's open source, self-hosted, and runs without trackers, cookies, or accounts. You're welcome to fork it.
Built and maintained by Mariatta in Vancouver, BC.
The site is named in tribute to Darren Hayes's 2011 album Secret Codes & Battleships — a record that has stayed with me for years. The themes that run through it (signals, grids, things waiting to be decoded, holding on to what matters) felt like the right shape for a folder of personal tools.
Don't give up — on secret codes.
The visual language leans into the album's nautical-cipher mood without leaning on it. Two ground tones do the quiet work: battleship-night navy (the ink) and cipher-paper cream (the page). Two signal colors are reserved for the moment something is found: maritime signal red for calls to action and decoded gold for success.
Type pairs Fraunces (a soft, optical-sized serif) for the personal voice with JetBrains Mono for the machine-readable layer — coordinates, codes, small labels.
Secret in italic Fraunces, with the C·O·D·E·S spelled in spaced monospace beneath — the personal voice and the machine voice on top of each other. To the left, a small cipher grid with two cells filled in red and two in ink: a hint that something is being plotted.
A literal battleship board. The grid is labelled A–H across the top and 1–8 down the side. The hits spell out an S on the left and a C on the right — Secret Codes, plotted. One hit on the C is the red signal (the cell that "found" something), and a small crosshair below marks where the next decode will land.
"Secret Codes" written in Fraunces with the same name underneath in morse — ... . -.-. .-. . - -.-. --- -.. . ... — split by a slice of red in the underline. The easter egg, for when the name should look like the thing it describes.
Found something broken, want to report a bug, or just want to say hi? Open an issue on GitHub — that's the only inbox for this site. The rest of me is in the footer if you'd rather use a different channel.