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.
jedberg
> that knows everything about your company
Given that I don't know everything about my 4-person company, and that I never knew everything when it was a 1-person company (guess which person is that), this sound like https://x.com/mitchellh/status/2044529496217555333 (apologies for twitter link)
bewareofscams
Looks identical to Claude Desktop connectors.
My Claude desktop app already talks to Jira, Slack, Outlook, GitHub, etc.
Grombobulous
The interesting tradeoff here is not just better retrieval, but whether the pre-compiled wiki makes behavior more predictable over long-running tasks. It would be useful to see comparisons against a plain markdown repo plus Claude/Codex: task completion, citation accuracy, stale-context failures, and the cost of keeping the wiki updated. Multi-model support and bring-your-own-key options also seem important for enterprises that don't want their company's context tied to a single provider.
paidx
Don’t have time to dig deep into it this afternoon, but want to comment to come back but also to suggest an expansion past your stated “one personal and one company” wiki.
I lead two different functional areas within tech and work in a larger tech platform for the parent company of a couple dozen operating companies.
All that to say “I would almost surely be better served by a hierarchy or general graph of wikis rather than just ‘me’ or ‘all 15K employees’.”
Even a 50 person company might benefit from “me”, “my team”, “my department”, and “whole company”.
sokoloff
7-day trial seems kind of narrow for a product that needs to "build a memory", no?
pelagicAustral
The website tells me absolutely nothing about what makes this new or unique
If AI has achieved anything it's a dramatic increase in documentation quality for the sake of training or instructions.
I'd argue that if documentation on how to operate your business can be used to feed an agent, your problem was never the ability to run operations and the ROI will amount to the ability to ask instead of doing. I don't know how much this is gonna go for, but you could probably have one of your existing staff just do basic documentation lookups too.
pluc
How do you manage permissions in the wiki? Does it require all content being available to everyone in the org or does it do some sort of vectorizing that is unique to every single user based on their perms? Whenever we've tried to build something similar, permissions is usually the first headache and is often why something like Microsoft's WorkIQ is appealing (if you're an O365 org).
comments (10)
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.
jedberg
Given that I don't know everything about my 4-person company, and that I never knew everything when it was a 1-person company (guess which person is that), this sound like https://x.com/mitchellh/status/2044529496217555333 (apologies for twitter link)
bewareofscams
My Claude desktop app already talks to Jira, Slack, Outlook, GitHub, etc.
Grombobulous
paidx
I lead two different functional areas within tech and work in a larger tech platform for the parent company of a couple dozen operating companies.
All that to say “I would almost surely be better served by a hierarchy or general graph of wikis rather than just ‘me’ or ‘all 15K employees’.”
Even a 50 person company might benefit from “me”, “my team”, “my department”, and “whole company”.
sokoloff
pelagicAustral
dbbk
noobcoder
I'd argue that if documentation on how to operate your business can be used to feed an agent, your problem was never the ability to run operations and the ROI will amount to the ability to ask instead of doing. I don't know how much this is gonna go for, but you could probably have one of your existing staff just do basic documentation lookups too.
pluc
willchis