We workbelow thesurface.
An independent technology collective exploring the systems, protocols, and infrastructure beneath the digital world.
- hex
- 0x68
- dec
- 104
- oct
- 0150
- ascii
- h
We operate in the margins.
rev 2026.10
About
Name
0x68 - independent technology collective
Synopsis
0x68[--systems][--infrastructure][--security][--research]
Description
We study the layers most people never look at: kernels, protocols, networks, and the infrastructure that quietly holds everything else up.
0x68 is a small, independent collective. We take systems apart to understand them, build tools when the existing ones fall short, and publish what we learn. There is no product here and nothing to sign up for. Just the work.
Principles
Systems over appearances.
How a thing works matters more than how it looks from the outside.
Reliability over hype.
Proven and understood beats new and fashionable. Boring is a feature.
First principles.
Read the spec, the source, and the packet capture before the summary.
Open knowledge.
What we learn gets written down and shared. Knowledge kept private decays.
See also
Where we look
Four areas hold most of our attention. They overlap constantly, and the interesting problems tend to live where they meet.
- 0x00
Systems
Operating systems, low-level computing, and software architecture.
kernelsmemorycompilersABIs
- 0x01
Infrastructure
Distributed systems, reliability, automation, and observability.
consensusnetworksfailuretooling
- 0x02
Security
Defensive security, protocols, and system hardening.
threat modelscryptographyhardening
- 0x03
Research
Experiments, tools, and unconventional technical ideas.
prototypesmeasurementodd questions
Field notes
Write-ups from the bench: experiments, investigations, and things we had to learn the hard way. Nothing is published yet. The entries below are in preparation.
The failure domains missing from your diagram
Shared power, shared DNS, shared people. Mapping the dependencies nobody draws.
Hardening a static site with nothing but headers
A working Content Security Policy for a site with no server, and the reasoning behind each directive.
Reading a TCP handshake one byte at a time
Three packets, forty-odd header fields, and what each one is actually for.
Have something worth discussing?
Questions, corrections, research you think we should see, or a problem nobody else wanted to look at. Plain text is preferred.
Channel
not yet open
A public address will be listed here once it is ready. Until then there is no form to fill in and no inbox behind this page.