OpenCrew
BuildingAn operating system for running a company solo.
Then I build another one. Founder of OpenCrew and SOMA. Ex-ML research at Cluely and Visa. Every company below is designed to keep running when I walk away.
Each system is wired to run without me.
An operating system for running a company solo.
A verified-human layer for the internet.
A coding companion people actually install.
From "Running an agency, a startup, and a supplement brand at 22."
If something needs my daily attention, it's broken. The loop keeps turning without anyone touching it.
Perfectionism is the enemy of running multiple things. Each bar is a release.
The portfolio looks wide, but I say no to ten times more than I say yes to.
Every figure is sourced in the content files. Superscripts are footnotes.
1. npm registry. The final build footnotes each number with source and date.
Everything I can do, one layer at a time. Scroll to pull it apart, then hover a layer.Everything I can do, one layer at a time. Tap a layer to open it.
Six layers, from writing code to running companies. Filter by mode to see which layers I use to build, think, grow or run.
Every version of me that shipped something.
The journal. Open a letter to read it here.
The difference between a tool and an operating system.
Read the letter →Building a dev tool that people actually want to use.
Read the letter →Somehow it keeps working.
Read the letter →Fill in the form. It lands in my inbox as a proper email.Pick a topic and write to me.
NOTE 01. Three keys are hidden across both sides of this site. One is on these sheets. Engineers find it. Managers ask someone where it is. Also: hold P to peek at the other side.
Learning the machines before they learn me.
An alt identity, learning in public. The goal: be the person who can protect frontier AI. Three keys lead there.
An alt identity, built in public. The goal: become the person who can protect frontier model weights, run AI inside trusted hardware, and prove a computation happened correctly and privately. Three keys lead there. Every instrument here is something on the syllabus.
Copper, jade and crystal. One is on Kartik's side. One only shows up if you're paying attention. One is right in front of you, doing nothing to hide.
Most visitors find zero. That's fine. Most visitors also skip leg day.
Every square is a day I studied. Below it, the exact topics I'm on and what comes after. All of it reads the checkboxes in my syllabus.
Each day I tick a topic, its square lights up and the note I wrote about it shows here.
All 31 modules and the five hard gates. Signals flow out of the stage I'm on. Hover to trace a module, click to open its topics. Dashed lines are hard gates.
Some modules are hard gates. Everything after them stays locked until the gate module is finished.
Each module shows its topic count, stage and what it unlocks.
Every module belongs to a key. The Forge is the shared foundation every key is cut from. Open a key to see its modules.
Where the three keys point: protect frontier model weights, run AI inside trusted hardware, prove the computation. Six levels, each one sealed until I learn it.
Each level hides a line. Every topic I learn decrypts one character. Click a level to see its topics.
I don't know yet exactly what this turns into. The trail is public though: I post what I learn on X, and the best of each week lands here.
Halliday would be proud. I'm mildly annoyed. Most people never get past the hero.
The full syllabus: 871 topics in 31 modules, in the order they depend on each other, plus the 170-topic Secure & Confidential AI track. It's what I study every day. Steal it.
Want bragging rights? Email me the passphrase ANORAK. Send it ↗