Coorporate Hermes
Coming soon. We are finishing and testing it before open sourcing the solution.

A private corporate agent for teams that need AI with real control.

Coorporate Hermes is the enterprise edition maintained by Ampliia to operate agents, automations, cron jobs, skills, memories, and integrations in environments with hierarchy, sensitive data, auditability, and human approval.

GovernanceRoles, permissions, checkpoints, and decisions recorded in an audit trail.
KnowledgeMemories and skills separated into corporate, team, and user scopes.
OperationsProtected web panel, agent-assisted configuration, logs, cron jobs, imports, MCPs, and observability.
MigrationImports Hermes exports through quarantine, review, and corporate guardrails.

Why a corporate edition exists.

Traditional Hermes is excellent for individual productivity and local agents. In companies, the problem changes: who can edit global instructions, which files each team can access, which automations need authorization, and how to audit what happened.

Role-based administration

Users request dashboard access from authenticated channels. Administrators approve, revoke, and assign teams, roles, providers, keys, folders, and limits.

Layered knowledge

Corporate memories and skills apply to governed conversations. Teams have their own context. Users keep personal preferences without contaminating the organization.

Human-in-the-loop

Shared changes are proposed, reviewed, and approved before they alter files or affect other people's conversations.

Agent-assisted self-configuration

Authorized users can ask the agent to configure itself from instructions. The agent reads the active governance context, applies only the changes that role permits, and routes shared changes through approval.

Practical architecture.

The architecture separates identity, knowledge, execution, and audit. The goal is to enable automation without losing administrative control.

Entry and identity

Users, teams, and rolesDashboard approval, revocation, admin, approver, operator, auditor, and team scopes.
Keys and providersCredentials are administered outside the prompt with operational visibility.
File accessAllowed folders by organization, team, or user.

Governed core

Hierarchical memoriesCorporate, team, and user memories with explicit precedence.
Hierarchical skillsSkills approved for the company, a team, or only a user.
Tools and MCPsTools are enabled by policy and reviewed before sensitive use.

Operations and audit

Authorized cron jobsCheckpoints by role or user before scheduled routines run.
ObservabilityOperational logs, audit events, and SIEM export.
Controlled migrationHermes exports enter quarantine before becoming corporate context.

How it differs from traditional Hermes.

Coorporate Hermes preserves the local agent experience while adding the controls required for multiple people, teams, and responsibilities.

From individual to organizational

Personal preferences remain available, but corporate and team knowledge goes through scope, approval, and audit.

From open files to governed access

The agent respects server folder policies before reading, writing, or using files as context. Team leaders can manage delegated team roots without becoming system admins.

From local automations to approved routines

Cron jobs and recurring actions can require authorization by role or user before execution.

Open-source attribution.

Coorporate Hermes is maintained by Ampliia as a corporate edition derived from the MIT-licensed Hermes project. The original Nous Research project is credited in the repository and license. The GitHub project is linked on this page and public availability depends on release timing.

Governance, security, and reference standards.

The platform is designed to align with recognized practices, without claiming automatic certification. The value is turning those standards into concrete product controls.

NIST AI RMF

Risk mapping, monitoring, governance, traceability, and improvement cycles for AI systems.

ISO/IEC 42001

Management controls for AI systems, with clear roles, documentation, evaluation, and human review.

ISO 27001 and SOC 2

Separation of duties, access control, logs, retention, review, and secure operations.

OWASP LLM Top 10

Guardrails against tool abuse, data leakage, improper execution, and unauthorized changes.

LGPD and GDPR

Minimization, purpose limitation, access separation, and care for personal data in memory, logs, and integrations.

Operational audit

Important events are recorded for review: denials, approvals, imports, cron jobs, dashboard actions, and knowledge changes.

Knowledge, skills, and teamwork.

The separation between levels prevents a personal preference from becoming a global policy and lets teams work with their own context without compromising the whole company.

Corporate

Memories, rules, and skills applied to every governed conversation. They only enter or change through authorized hierarchy and human approval.

Team

Knowledge and skills for departments, squads, or business units. Scope is limited to members and folders allowed for the team.

User

Individual preferences and shortcuts that do not alter other people's behavior or create new permissions.

Human approvalTeam scopeAllowed foldersTeam-lead file controlGoverned memoryApproved skillsControlled MCPs

Read the documentation before deployment.

The documentation covers administrative onboarding, Hermes export migration, memory and skill governance, cron jobs with authorization, observability, and secure operations.