Live data from Hacker News

Show HN: Airweave – Let agents search any app

github.com

11–20 of 47 posts

Re: Show HN: Airweave – Let agents search any app

#11
Is chat always the best interface for all of these apps? I feel like search is the natural first step, but chat-based search has been around for a while. Feel like an MCP-based version of Glean/Onyx/Moveworks/Dashworks is interesting, but unsure how much better it makes the product. Curious to see why your product is better

Re: Show HN: Airweave – Let agents search any app

#12

How is this different from regular MCP servers?

Co-founder here. The platform provides MCP or REST endpoints on top of searchable information. The tool is specifically geared towards agents that want to perform actions on external systems (through an MCP server, for example) but get confused about which objects to interact with. Airweave provides a robust interface for this.

You can compare it to how coding agents like Cursor work. This is the usual pattern you see: - The first step is reading your prompt - Then it goes through all the attached files and searches your codebase - The last step is to make code file edits.

Non-coding agents that use "regular" MCP servers completely miss the second part. It's very hard to go from natural language instruction, to a chain of API calls that actually work and don't end up in hallucination

Re: Show HN: Airweave – Let agents search any app

#13

Is chat always the best interface for all of these apps? I feel like search is the natural first step, but chat-based search has been around for a while. Feel like an MCP-based version of Glean/Onyx/Moveworks/Dashworks is interesting, but unsure how much better it makes the product. Curious to see why your product is better

Co-founder here. The Airweave interface doesn't discriminate which downstream use case it's applied in. Most current developers don't build it for a chat interface at all actually. Instead they fold it into their agents to give them access to user data. At first sight enterprise search looks quite similar, but instead this is a building block for developers to set up integrations for their internal agent / agent product.

Re: Show HN: Airweave – Let agents search any app

#15
post #14

Pretty cool stuff. How does it deal with self-hosted data sources? can it run inside a VPC and talk to my RDS instances directly?

You can self-host Airweave on Docker or Kubernetes within your VPC. We eventually want to move towards AWS/Azure/GCP marketplace offerings that should make this easier for you. RDS should work - if you get an instance with PSQL/MySQL dialect.

Re: Show HN: Airweave – Let agents search any app

#16
post #5

this is so powerful - MCP on steroids :). what are the next use cases you're looking to build?

We're mostly focused on getting this right - better than any other tool atm. We are evaluating ideas like mapped RBAC, self-updating deep research and other tools for agent builders but it should first be very clear to us the devs actually need it :D

Re: Show HN: Airweave – Let agents search any app

#19
post #17

Pretty cool – when does it make sense to use this vs n8n?

n8n is a good example of a tool that Airweave can enhance. n8n allows (no-code) developers to set up pre-determined automations but as soon as you want to process non-deterministic text into action on an app, you will still need a way to search the app. Example: you have a n8n workflow that gets you on track with Linear tickets. You hook it into a text-based human interface in which the user says: "I just created a task about database migration on Linear, can you start doing the preparations for it?". Airweave can 1. find that damn ticket, 2. give additional context on database migrations based on what else it finds in the integrated systems.

Re: Show HN: Airweave – Let agents search any app

#20

Nice - does it have role based access controls built in?

I assume you're talking about the data layer (not the control plane)? We are currently in PoC phase for mapping the role graphs from source systems (Asana, Google Drive) to our internal role model, but this is still in the works. The way developers work around this atm is by configuring a connection on a subset of the source info. Example: only make Airweave sync info from the `Shared Drive/Marketing/Branding` path
Post reply on HN