Don’t have time go 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’.”

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.

> 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)

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).

The source-retention detail seems more important than the model list: if an email is compiled into a wiki and later deleted, or access is revoked, how quickly does that fact disappear from the personal or company wiki? Is the wiki rebuilt from current source state, or are removals handled as a separate event?

How are you different from the following cos?

OpenTag

Turnstone

Memory Store

Hyper

Hyperspell

Wato

Savant

Shepherd

Glen

OpenTag

Janet AI

screenpipe

Cerenovus

jo

Bond

Airweave

Mem0

Theta

Nessie

Mosaic

Onyx

Slite

Dashworks

Circleback

Stamp

Tasklet

Within

Khoj

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.

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

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

Really simple and well designed website for the brand identity. Logo, background, UI and FAQ all flows well. Feel like I trust the project without knowing much about it or having the usual “trusted by” section. Keep it up!

undefined

Given it has "logins" to tools without APIs (browser-based access), how do they handle 2FA, session persistence, and ToS violations for services that don't allow bot access?

Microsoft WorkIQ but for companies on a non-MS stack

Congrats on the launch! Really useful tool!

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!

[dead]