Code is invisible.
Every programmer has stared at code that should work and doesn't. The loop looks right. The logic reads fine. And yet - wrong answer. The problem isn't that you can't read code. It's that reading was never the right tool: code is a process, and you were shown a photograph.
Flame started with one idea: what if you could watchthe process? Not a video of someone else's explanation - your own code, executing, step by step: every call opening a frame, every branch choosing a path, every swap moving a value through memory.
That's NeonFlow, the engine at the center of everything we build. Around it we built the rest of a classroom: problems with hidden tests, batches, submissions, and the teacher's superpower - replaying a student's exact run to see where their thinking diverged from the machine's.
What we believe
- Seeing beats memorizing. You don't memorize how quicksort partitions once you've watched it happen.
- Real execution only. Tests actually run. Output is actually produced. A green check means it worked - never that a demo pretended it did.
- Setup is the enemy. The gap between wanting to code and running code should be one browser tab.
We're small, early, and shipping fast.
Watch your first program run