usealmanac.com

Launch HN: Almanac (YC S26) – AI that knows your company

kushagrchitkar · 59 points · 48 comments · 31. Aug. · Open original

Hi HN, I'm Kushagra, one of three founders of Almanac, a Hermes with a brain that knows everything about your company. We started our journey with setting up Hermes for our company, thinking it must be easy. We wanted an agent that would know every context about our company, so we could ask questions and get context-appropriate responses to. This started a very annoying and difficult journey. Setting up Hermes, getting it to talk right, building OAuth apps for every connector myself, then feeding it context myself, and ultimately struggling with Hermes's default memory. At the same time, we saw our YC batchmates struggling with the same problem, and we saw an opportunity. So we built Almanac. This is how it works. You sign up, you get a Hermes agent straight out of the box. You have a one-click connect to any account (Gmail, Calendar, Granola, PostHog, etc). You have personal accounts (only accessible by you) and also shared accounts (accessible by everyone in the company). The consequence being I can never see my cofounders' accounts. The “brain” of this agent is wikis. We pull in information from your connected sources, and start organizing this information in two wikis. A personal one, for you, which understands who you are, what your preferences are, the people in your life, and the things going on in your life. The second wiki is a company wiki, which includes what the company is, what you’re working on, what the roadmap is, and what the blockers of the company are. Your agent ultimately has access to these two wikis and the original accounts, which invoke the feeling of “it just knows you.” Here’s a demo: https://www.youtube.com/watch?v=ajXP5PHuK18 We're three cofounders, Rohan, Kushagra, and Divit, and we've been friends for 11 years, since studying for the IIT-JEE. We all did Electrical Engineering (Rohan at IIT Delhi, me at IIT Kharagpur, Divit at BITS Pilani, Hyderabad), and Rohan and I later went to Harvard, where this pre-compilation layer became our capstone thesis. We have built multiple products around the idea of a pre-compiled knowledge layer. Our main differentiating point is the way we approach memory and context in general. Most AI assistant tools treat memory as an afterthought. We have worked on wikis for AI for more than a year now, building products for Harvard and NASA. The one thing we have learnt is that one needs to spend a lot more compute upfront, in the pre-compilation of this knowledge base, to get it right. Having this pre-compiled knowledge base enables a lot of interesting ideas. First is a proactive agent. Since I have compiled what’s going on in both my company and my current life, Almanac can start completing tasks on its own. Concretely, we run a background worker which takes a look at tasks that could be completed, pings the main agent, who then pings me, suggesting which tasks it could automate. As a result, I wake up to proactive notifications which look like “I already prepared a draft of your fundraising pitch deck, want to take a look?” Second, long-horizon tasks. In our wikis, we maintain a section on ongoing projects, so Almanac can pick a task back up days later without losing the thread. Most agents are session-bound: they run once, finish, and forget. But a lot of real work isn't one shot; it plays out over hours and days with people in the loop. The clearest example is anything that involves waiting on a human, like scheduling a meeting, following up on a sales thread, or chasing a document. Almanac can send an email on your behalf, and because it's always on and remembers the project, it notices the reply four hours later and drafts the right follow-up in context. Since launching, we've seen a lot of use cases for Almanac. One person runs her dog-rescue operation through it: finding available fosters, tracking pickups, and sending reminders for consent forms. Another researches Polymarket strategies with Almanac, where its memory holds what past strategies were, proposes new ones, and compares them against what went right or wrong last time. Another builds marketing campaigns on it without having to re-explain the business and the whole campaign every single time. Regarding privacy and security, Almanac only accesses accounts you explicitly connect. Your OAuth credentials are held by our connection provider, not in Almanac’s database. We only store the wiki and the source behind its citations. So an email used as a citation may be retained as Markdown. We’re live: https://usealmanac.com. We have a 7-day trial on all of our plans. Happy to hear if people have done similar setups, and what new features they’d like in Almanac. If you’re a company that wants to get an agent that actually gets tasks done, I would love to talk: https://cal.com/team/almanac/demo.

Comments

5 preview comments · loading full thread
jedberg31. Aug.

There is a lot of competition in this space, both commercial companies and open source. It seems like the biggest advantage for using one of these and not Claude or Codex is that you can use multiple models. Otherwise, those two have all the same features, or probably will in the next week. Are you able to use multiple models? Or I guess the first question is, what model(s) are you using? At this point, many enterprises care so that should be front and center, especially if you're using models hosted in China, because a lot of non-Chinese companies care about that. You mention some things about unique ways to store memory. Do you have any data or use cases on how that improves performance? If you do, you should get those on your website too. I'm not sure you have a very strong answer to "Why not just run Claude or Codex on my laptop?" Sure, you provide compute, but so do they, and most enterprises and even regular people are getting desktops/droplets to run their agents now because of this problem. This is kind of solved already. Also there is a small nit with your website. The graphic next to "Proactively gets things done for you" gets bigger and smaller, so if you're trying to read anything below that, it keeps jumping up and down.

pelagicAustral31. Aug.

7-day trial seems kind of narrow for a product that needs to "build a memory", no?

logicallee31. Aug.

Congratulations on the launch! The demo in the video you linked looks awesome (though your video resolution is a bit low, some of the text is hard to read on screen, I suggest you record in higher resolution). I think you made a really good choice to have your connector provider handle OAuth credentials, since it is really hard to get security right on a multitenant app like yours, where some of your agents are doing work on customers' behalf and others are improving your product itself :). The design of your app interface also looks really great!

i18ner1. Sept.

Congrats on the launch, the approach of spending compute upfront is a compelling shift from what the current standard is. I am curious as to how you handle state invalidation and unseen side-channels during those long-running tasks, because if the agent pauses a task for X days, say waiting for an email reply, but the projects params changed offline or in a channel that the agent has no eyes on, how does the system realize that the pre-compiled context has now gone stale? Does that also mean that proactive actions always require a HITL?

dbbk31. Aug.

The website tells me absolutely nothing about what makes this new or unique