Six primitives. No folders. No tags. Just structured thinking that compounds over time. Built for engineers who value clarity over flexibility.
Technical people don't think in "notes." They think in hypotheses, tests, and outcomes. These six primitives map directly to how engineers actually work.
Something you believe but haven't verified
"Redis will handle our read volume at scale"
A deliberate test to validate an assumption
"Load test Redis with 10k concurrent reads"
A choice with context and trade-offs recorded
"We'll use Postgres over MongoDB because..."
Something that didn't work, with analysis
"The caching layer added latency instead of reducing it"
A validated insight from experiments or failures
"Our bottleneck is network I/O, not database queries"
An open problem you're actively thinking about
"Should we rewrite the auth system or patch it?"
The constraints are the product.
This is not a project management tool. Use Linear or GitHub Issues.
Low-signal, high-volume noise. Not thinking.
Hoarding is not thinking. Extract the insight as a Conclusion.
Encourages volume over clarity. Not supported.
Leads to over-categorization and maintenance burden. Use full-text search.
Forces premature structure. Everything is flat with links.
No free tier bait-and-switch. No dark patterns. Cancel anytime.
Try the mental model
The full experience
And that's intentional
Team features would change:
This is individual memory, not collaboration software. Your thinking is yours.
Export everything in open formats anytime. Your data is yours. No lock-in, no hostage situations.