Credentials. The .env file holds the admin password and encryption keys, so keep it out of version control.
Who it is forAn infrastructure engineer asked to give the company a governed home for AI skills.
The problemSkills shared through chat and copied folders have no review or audit trail.
The outcomeA self-hosted control plane where every change has an author, approver and undo path.
What you need first
- Docker and Docker Compose
- A domain for HTTPS deployments
- Admin email plus generated JWT and encryption secrets
Steps
- Download docker-compose.yml and .env.example for the release you want
- Set ADMIN_EMAIL, JWT_SECRET and SECRETS_ENC_KEY, generating secrets with the node crypto command in the README
- Set DOMAIN and run
docker compose -f docker-compose.yml --profile https up -d - Sign in as admin and connect your agents over MCP
Prompt for your agent
Deploy Bevel-Software/Hexis on <host> with `docker compose -f docker-compose.yml --profile https up -d`, sign in as admin, and add one skill. Verify the skill change is recorded as a commit in the backing Git repository.
Caveat. An agent can only do what the person running it can do, resolved per file, so permissions must be set before rollout.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Bevel-Software/Hexis and "Self-host a company skill and tool registry"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer