... building NeoCMS a CMS designed from scratch for the AI era Hey everyone We're building NeoCMS a content management system designed from the ground up for AI-first workflows. The problem Every CMS today stores content as HTML blobs messy markup with inline styles that AI can't reliably read, edit, or generate. When platforms bolt AI on top, it's a wrapper guessing its way through unstructured content. It breaks things. It hallucinates layouts ... ... trusted to ship production pages. What NeoCMS does differently We threw out the HTML blob

... progress. Not even we can read it. How it works: Password-derived public-key cryptography runs entirely in the browser End-to-end encryption by default on every plan not a premium add-on The server stores only encrypted blobs it can never decrypt What you get: Habits & streaks build consistency and track your check-ins Reflections journal on your progress privately Goals & milestones set targets and track meaningful progress Schedule / calendar plan your habits around your life ... ... events Groups Two format options: JSON single .json file with all selected data CSV (zip) a .zip containing one .csv per data category, plus a metadata.json The noteworthy part given our zero-knowledge architecture: the server sends the encrypted blobs

... history into every prompt. It's slow, expensive, and most of it isn't even relevant. So I looked at what's out there. Mem0, Zep, Supermemory. They all do basically the same thing: take text, embed it as blobs, throw it in a vector database. It works, sort of. But there's no structure. You can't look up a specific piece of knowledge. You can't version it. You can't organize it. And they charge ... ... operation on YOUR API key because they're running LLM completions for every read and write. I built HyperStack and took a different approach. Instead of blobs

... said , but: - What s this user s communication style? - How advanced are they in this domain? - What are their stable preferences? - What events in their history actually matter? In other words: I wanted something that looked less like a blob of text and more like a structured, typed profile that evolves over time. So I pivoted GetProfile AI to become exactly that. From profiling API to LLM proxy with memory GetProfile originally started as an AI-powered profiling API: send ... ... overwritten, memories can be summarized and pruned, and the profile stays in sync with how the user actually behaves. The key difference from many other solutions is that the profile is structured. Instead of storing raw text blobs

... might notice the same patterns almost everywhere: Blue + purple gradients: It s the unofficial uniform. If your logo doesn't have a neon-ish gradient, then you're not a SaaS. Rounded geometric logos: Circles, dots, abstract blobs...lovely, but indistinguishable. Overused tech fonts: A variant of Inter or a slightly modified SF Pro. Clean? Yes. Memorable? Not really. Taglines that all say the same thing: The AI platform that boosts productivity. Your all-in-one workspace. Do more with ... ... that reflects reality and is unique, and then build an identity based on it. Don t rely on playfulness alone A few years ago, a playful identity really stood out, but today, half the SaaS world is using friendly blobs