I'll give my honest take, I think what you've done is taken dev-tools and given it a wrapper that most designers (including myself would love) I find myself in dev tools alot during QA refining the design, since rendering is never exact. And you've added MCP server integration which is great. But....
First 99$? that's steep my full seat of Figma is 160.0$, so I don't see the value. I do see the value in convienience so you may want to rethink the pricing structure. Second. It's a design tool, not SASS software, the website should speak to designers like me, not look like supabase. Great job, I wish you luck...ken. Kylex.io
The 'store everything vs. synthesize' axis is the interesting design question here. MemPalace bets that retrieval quality is the problem — keep everything verbatim, make it findable. That's a legitimate approach.
We went the other direction with Lodestar (launching tomorrow). The bet is that you don't need the transcript but you do need the decision layer. What was decided, why, what was rejected. Synthesized by an LLM at session end into a plain markdown file that commits to the repo.
The other structural difference: the file lives in the codebase, not on the machine. git clone on a new laptop and the context is already there. Different tradeoff than a local vector DB.
Curious whether MemPalace users find the verbatim storage approach holds up as session count grows — the retrieval quality question gets harder with more history.
