Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Clarification on target audience and positioning #5336

Discussion options

Hey everyone,

I’m currently exploring Hive and trying to better understand its positioning.

From the documentation, it seems primarily designed as a developer framework for building autonomous AI agents. However, I’m curious about the intended primary audience:

  • Is Hive mainly targeting developers building custom agent systems?
  • Or companies looking to directly automate business workflows?
  • Is there an enterprise or hosted model planned alongside the open-source core?

Understanding this would help new contributors (like me) better frame use cases and potential improvements.

Thanks in advance!

You must be logged in to vote

Hey @freirefernandam, welcome!

I've been exploring the repo for a while now and can share what I've picked up. Of course, I'm not a maintainer so take this as a fellow contributor's perspective.

From what I see, Hive is definitely developer-first. The whole "define goals in natural language, the system builds itself" approach is really about giving developers a framework that handles the hard parts - observability, failure recovery, graph generation - so they can focus on what they actually want the agent to do.

That said, it doesn't feel like just a toy framework. There's real enterprise thinking here - the cost controls, human-in-the-loop nodes, credential management, and the fact that ...

Replies: 3 comments

Comment options

Hey @freirefernandam, welcome!

I've been exploring the repo for a while now and can share what I've picked up. Of course, I'm not a maintainer so take this as a fellow contributor's perspective.

From what I see, Hive is definitely developer-first. The whole "define goals in natural language, the system builds itself" approach is really about giving developers a framework that handles the hard parts - observability, failure recovery, graph generation - so they can focus on what they actually want the agent to do.

That said, it doesn't feel like just a toy framework. There's real enterprise thinking here - the cost controls, human-in-the-loop nodes, credential management, and the fact that everything is self-hostable. The integrations being built (Stripe, HubSpot, Gmail, etc.) show they expect these agents to touch real business systems.

On the hosted/enterprise question - there are some clues. The team is YC-backed, there's a separate docs site at adenhq.com, and they're actively hiring. That usually signals commercial intentions alongside open source. But I haven't seen anything official about a hosted offering yet.

For me as a contributor, what's cool is that the framework is pretty modular. You can work on integrations, core improvements, or even documentation without needing to understand everything. The featured issues list in #4150 is a good starting point.

Anyway, hope this helps! I'm sure the maintainers can give you the official roadmap - this is just my read from poking around the codebase.

You must be logged in to vote
0 replies
Answer selected by TimothyZhang7
Comment options

My read is similar to the existing reply: developer-first framework, but with obvious signals that the intended use cases are not only hobby projects. The interesting tension is that the repo talks like infrastructure while a lot of the product surface points toward business workflow automation.nnWhat would help new contributors is an official positioning note that separates primary audience, secondary audience, and monetization direction. Even a short statement like framework first, hosted product later or open core with enterprise operations focus would remove a lot of guesswork.

You must be logged in to vote
0 replies
Comment options

Hey hi @freirefernandam , and @mubarakar95 Glad to meet u here , Its informative ur both conversations , and I m looking at Issue #2805. It's dedicated to adding new MCP Tools and Integrations, which is the perfect way to get familiar with the framework without diving too deep into the core engine logic first...

any one already done and what your POV on this ?

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /