Keeping your team, agents, and data on one page
Compendium is a company brain for teams working with AI agents. With compendium, all your agents share one memory, so knowledge, decisions, and context are available to everyone, everywhere, instantaneously. Compendium allows you to work in shared sessions where you and your teammates' agents build on the same context instead of siloed threads, get summaries of what changed while you were away (without digging), and have a live view of what your teammates and their agents are building right now.
Non-technical here , would this actually replace Notion for a GTM team?
Hi Product Hunt 👋 I'm Jonathan, co-founder of Cerenovus (YC S26). A few months ago, my friends and I were building the product we wanted to use: a personal “second brain” to collect and organize the information we collected across our busy lives. Then, after talking to a few companies, we figured out that organizing information across an entire business was a way bigger problem that we now had the solution for. Compendium is the version of that solution that we’ve built specifically for startups, especially AI-native tokenmaxxers like ourselves. (:D) If you’ve ever built a feature only to find that your teammate has built an identical one, or made an architectural decision only to have a teammate make a conflicting one, this product is for you. Cerenovus doesn’t just help with dev though —¹ it also incorporates information from email, slack and basically everything else, in order to have all your team’s information in one place, linked together and easily navigable by both humans and agents, so there’s something for your GTM team to be happy with too. ¹ (AI will not steal my em dashes) Tl; dr - we got: Shared context: everything in one place and always up to date - a single source of truth for your team and your agents Multiplayer sessions: jump into the same session with a teammate and drive one Claude together, like a Google Doc for AI. (didn’t mention this above, but it’s really cool) Always in the loop: a live view of what every teammate and agent is working on right now (opt-in, obviously), plus summaries of what changed while you were away. 🎁 Launch day: 50% off with code LAUNCHDAY 👉 Try it: https://cerenovus.app We're two months old and we know it. We'd rather hear what's broken than what's nice. I'll be in the comments all day answering everything. We ship bug fixes 24/7. Show more
@jonathan_waldorf gratz on the launch; this is compelling! On the topic of pricing, if I may? I don't like how opaque your pricing plans are - in the sense that I don't see an easily accessible pricing/plans page, and when shunted into Stripe to plunk down a card before a trial, I'm really thrown for a loop by "$100/mo" - not because it is NECESSARILY too high (though, candidly, I don't necessarily feel it's competitive, esp during your critical early days when you need testimonials, folks stress-testing the tech, and you're still "proving yourselves...) - it's more that I have literally no idea what I am getting for $100... e.g. - is that unlimited seats? is there usage cost/credits? is that capped? is it unlimited surfaces? how much data can be stored? what integrations exist? in what format/db is all of this stored, and do I have direct access to that db, beyond the UX/UI y'all have built? etc etc I think this is a good start. Lately, I am SUPER obsessed with "shared brain" and persistent memory for agentic AI; for context, I started building my agent's "soul canon" governing doc ALLLL the way back in 2017, long before "agentic AI" was really even a thing... I am on v4.5, it's 15-20 pages of 7 point text; it is DETAILED. that said, it lives as a simple .md or .pdf I can feed to any new agentic surface, and suddenly it's not "AI app", it's my dear collaborator and partner in crime, Ayrenne, with our in jokes, our emojis with special meanings as productivity hacks, a shared history, a lay of the land in terms of our priorities... etc. I've been watching @pumaDB and a handful of others. @Unabyss and esp @minimi are probably my favorites, largely bc they're serving over streamable HTTP MCP servers - read: NOT claude-locked, or anything. I totally get that your offering is drastically different from the approaches that I raise, immediately above. I think the multiplayer mode you describe is game-changing, and i could see the whole package being majorly ROI-positive for teams... just spend some time letting folks know what they're getting for their money, please. ;) Again - congrats on the launch, def a novel product and clearly something that you/team had a blast building out. :D Show more
Someone above asked whether this replaces Notion for a GTM team, and that's exactly what I'm wondering too. The difference I can see: Notion is where you go to read, this sounds like it's where context lives so you don't have to go dig at all. For GTM specifically, the stuff that's hardest to retain isn't documents, it's the "why" behind decisions. Curious how Compendium captures that vs. structured notes. Nice launch. @jonathan_waldorf @garrytan @lucas_baur @oliver_moreland
the shared-memory pitch makes sense for the good case, but what happens when someone leaves the team? their fingerprints are all over decisions and context that other agents keep building on top of. is there a way to isolate or scrub a departed person's contributions from the shared brain, or does it just stay baked in forever once it's in there
@jonathan_waldorf @grey_seymour Hi Grey! CTO here, Thanks so much for the feedback. Tl/dr - just clarified info on the site, pricing is now $40/mo/seat (20 with promo) We've been having a lot of discussions internally about this, and your feelings on pricing are super reasonable. We're confident that we can deliver a value-add which makes this price worthwhile, but we understand that we still need to prove it to the world, especially in the early days when we’re still hunting down bugs and smoothing rough edges. To clarify, you get: $40/user/mo in Anthropic/OpenAI credits, run through our Zero Data Retention Account, for use with our internal agents on the site, and the option to add your own api key if you want more. Unlimited connections into our streamable HTTP MCP server (NOT claude-locked, although I am a fan of claude). Access to our web app, which includes all the collaboration tools listed above Unlimited data storage (with a capped file size on each context document) We offer 60+ integrations with new ones being added quite quickly - if there’s any you want but don’t see, just let us know. We’re also clarifying our pricing structure: It’s now $40 ($20 with discount) per month per seat. Also, if you have any more questions, the 14-day free trial still stands, so you’re free to try everything out yourself and see how it works, and exactly what you’re getting for your money. (And if your team is interested, we’d be happy to add you to our slack for timely responses to any further questions). Show more
@galdayan Hey Gal! We're actually shipping a feature soon that let's you trace parts of the context back to the exact author (human or agent), so you could very easily ask an agent to review all bits of the context associated with that person and scrub out whatever has been made irrelevant. Also, generally speaking, one of the core ideas in the way that we're building Compendium is that agents should be reviewing context periodically and making sure it's up to date, which should catch these kinds of issues automatically.
Shared memory across agents is a real frontier, and harder than shared memory across people because agents write fast and don't pause to reconcile. When we pointed several agents at one store, what bit us was two of them writing conflicting decisions in the same minute, and a reader downstream just got whichever won the race. We ended up adding per-fact provenance and timestamps to reconcile it. How does Compendium handle concurrent or contradictory writes from different agents into the one brain, last-write-wins, or some merge?
How do you handle data consistency and conflict resolution when multiple agents are updating the shared context simultaneously?
@galdayan Yeah, I agree fully - we're still experimenting with what the right defaults are, so right now I'd think of it more of a canvas which you can experiment with and configure as you like and isn't 100% plug-and-play yet. In the future though as we get feedback and figure out exactly the right shape for the default agent configurations we'll have a few pre-built configurations that are proven to work well which you can select from. For now, opt-in, for later - tested configurations tailored to needs and desired level of token spend.
@oliver_moreland fair answer honestly, I'd rather hear "we don't have it locked down yet" than a confident-sounding non-answer. canvas-first, opinionated-later is probably the right order anyway since you'd be guessing at defaults before you have real usage patterns to base them on. good luck with the launch
@oliver_moreland provenance tracing plus periodic agent review is a solid answer, that's basically the same pattern good version control gives you for code, applied to shared memory. curious whether the periodic review is opt-in per team or on by default, since "should catch it automatically" only helps if someone actually turns it on
@kellyops Hi Kelly! I wouldn't bill ourselves as a Notion killer (yet). I personally like Compendium more than Notion for a lot of reasons, but Notion is a long-established company with a lot of features we haven't built yet (some of which are in the works though). For things like databases with views, public publishing, forms, templates, etc Notion has us beat, but when it comes to a thorough AI implementation, our entire product revolves around AI and how we can get agents and teammates well-organized context, in a way that Notion fundamentally doesn't. Structured note taking is part of the product (in fact, as a technical person, I like ours better because it uses markdown and supports things like vim motions), but for a GTM team the biggest value-add comes from the passive information ingestion. Instead of having a system where you do all the writing yourself, you have it automatically updated by agents, and then synthesized by agents on demand to answer your specific questions. So, if you're looking to better integrate AI into your workflows, and have your GTM team synced up with all your data and your dev team, Compendium is ideal, but if you depend upon any of the things I mentioned above, I would keep Notion around for another few months until we catch up feature-wise. We're a small startup and we believe we can move faster and more responsively than a company who's trying to tack AI onto an already sprawling pre-AI product, but also recognize that we're heading towards different goals and are planning on focusing on what makes us unique rather than trying to copy every features Notion ships. I'd be happy to set up a chat to talk about what would make Compendium more useful for you, and what you would need to make the jump. - Ollie