re 2.: I agree that there's a trend with OpenAI/Anthropic are adding Airweave-like connectors to ChatGPT and Claude Desktop. Imho this a good thing for us because it's showing the utility of our use case
Yes thats an accurate description. I'd add the nuance that our retrieval is designed to give agents the right actionable context to perform work on users' workspaces, and not necessarily to synthesize a final answer for a human end-user. But ofc you can use it for that.
1. thanks for the feedback, testing it on a smartphone and changing that asap.
2. What about the pricing do you find complex? And what would make it easier to understand for you? Just want to add that you can just get an API key by using the free developer version or local instance (API-key is shown immediately in the top-right panel). You can also create more in your org settings
and ofc, feel free to reach out if your team needs help with setup
@btown: Biggest difference: Airweave is infra for devs, i.e., connectors, sync, indexing (semantic + keyword), and a retrieval API/MCP designed with LLMs in mind as the consumers. You bring the agent/UI. Onyx is an end-to-end search app that owns the agentic reasoning layers that orchestrates their search. You can think of Airweave as a dev tool that you would use if you were building an agentic application, where Onyx is a good example of one.
On permissioning: we default to per-user syncs that adopt the permissions of the syncing user and mirror source ACLs (e.g., Drive items a user owns or that are sharedWithMe). In practice, founders avoid leaking private docs by either (a) having each user sync their own corpus, or (b) using a centrally-scoped token limited to Shared Drives/team folders and excluding personal “My Drive.” You can also keep separate collections and only expose cross-user search behind your own checks. We’re exploring richer org-level RBAC mapping on a per-customer basis (e.g., mapping Drive/SharePoint groups to index ACLs), but the above works today.
the custom priced tier has usage based pricing. Admittedly, we’re still trying to nail down the unit economics of it all, which is pretty tricky in our case. That’s partly why wanted to release the free dev tier and cheap pro tier, so people can get started with building lightweight projects already. But I 100% agree that the next step is a self-serve PAYG tier.
it's currently guided by community feedback, github issues, and user talks. and we rely on private e2e test suites for maintaining quality as we scale coverage