About Hexis
Hexis is a Git-backed platform for managing AI skills, tools, and context in one place. It layers a user-friendly interface on top of Git's core versioning and pull request workflow, so non-technical staff can participate without learning Git. The system connects to any AI agent via MCP and is available as an open-source project.
Review
Hexis addresses a real operational gap: distributing and governing AI agent capabilities across a company. The tool's pitch is straightforward, and the demo is accessible at demo.bevel.software. It is currently in its early launch phase, with the team actively responding to user questions on Product Hunt.
Key Features
- Centralized repository for skills, tools, and knowledge, managed through a clean UX over Git.
- Access control per person, team, or agent, with admins approving changes and reviewing submitted skills.
- MCP-based consumption, allowing any compatible agent to pull skills directly.
- Group-based governance where each team can maintain its own versions of skills, with user-friendly PR approvals.
- Unique skill name enforcement at creation, with path-based fallback for edge cases.
Pricing and Value
The launch page lists Hexis as free and open source. There is no mention of paid tiers or enterprise licensing in the provided material. The value lies in removing the Git learning curve for non-developers while keeping Git's versioning and review mechanics intact for those who need them.
Pros
- Git as the source of truth means versioning and PR reviews are already familiar to dev teams.
- File-based access management goes beyond what plain GitHub or GitLab offers.
- Switching between different AI agents is simplified because skills are stored externally.
- Self-hosting is possible, as the team points to a demo before asking users to deploy their own instance.
Cons
- Skill name conflicts across groups are handled by appending numbers, which could create confusing duplicate entries.
- No reviews or third-party validation exist yet, so real-world reliability is unproven.
- It is not well suited for solo developers or small teams that already manage a handful of skills directly in a repo without needing governance layers.
Hexis fits organizations where multiple teams share agent skills and need formal review cycles without forcing everyone into Git. It also suits admins who want granular control over what each agent can access. For individual practitioners or tiny teams, the overhead of group-based governance likely outweighs the benefit.
Open 'Hexis' Website
Your membership also unlocks:
