AgentHub Connect · Governance Console

Governance and monitoring of AI agents

AgentHub Connect is the console that manages Wiven agents on your infrastructure. You see what each agent does, you decide what it is allowed to write to your software, and you set its cost.

AgentHub Connect · demo
Loading demo…

Do you want to see it connected to your own software? Let's reserve 20 minutes

In short

An AI agent doesn't stop at simply providing a response: it reads documents, calls tools, and suggests entries in your business applications. AgentHub Connect routes each of these entries through a human decision or a pre-defined rule. It logs each execution without retaining the processed content and pauses an agent as soon as it exceeds its budget. The console runs on your local machine.

Nothing is written without a decision.
  • Your infrastructure
  • Human validation
  • Journal with no content
  • Emergency stop
// why a frame

An agent takes action. We need to know who authorized it, what it did, and what it cost.

A chatbot generates text that someone then proofreads. An agent handles the process independently: it retrieves an invoice, locates the supplier in the ERP system, and then generates the accounting entry. The time savings are significant, and it asks questions that a manager, financial officer, or auditor would eventually ask.

40 %

agentic AI projects abandoned by the end of 2027

That's the forecast of Gartner (June 2025), due to costs, poorly established value or insufficient risk controls.

CHF 250,000

a fine for the person responsible

The nLPD penalizes natural persons who intentionally fail to inform others of an automated individual decision (Articles 21 and 60 of the LPD).

2.12.2027

European AI Act: High-risk systems

Date of application of the obligations for the systems in Annex III, after the postponement adopted in 2026. Human control is required there (art. 14).

01

Who decided?

An entry in the accounting system or a closed ticket in the system must be able to be linked to a specific person or rule, along with its reason.

02

What happened?

What documents, what tools, what data, and above all where to: a template on your machines, a business software, or an external service.

03

How much does it cost?

A looping agent or a misconfigured external model can consume a month's budget overnight. We need a cap that takes action, not just a report that observes.

04

What does the law say?

The new Data Protection Act (nLPD) requires that the data subject be informed of an automated individual decision that significantly affects him or her, and that he or she be given the right to request a review by a person (Art. 21). It also provides for a record of processing activities (Art. 12).

// the journey of a writing

The agent makes the proposal. The gateway writes it down only after a decision.

In AgentHub Connect, an agent never has direct access to your software. They go through a gateway that only exposes the granted tools, keeps access secrets to the vault, and only writes once a decision has been made.

01

The agent reads

A supplier invoice arrives. The agent analyzes it using a template running on your infrastructure.

02

He consults

It queries the ERP through the gateway, tool by tool, for example to find the supplier.

03

He proposes

He submits the accounting entry. It waits in the validation queue.

04

You decide

A person validates, corrects, or rejects the request, or a self-validation rule applies. Only then does the gateway write.

Each step is recorded in the journal: who, what, where to, how many.

// in action

Three moments where the console takes back control.

A document to approve, a budget running out, an agent to stop immediately. This is what your teams see in AgentHub Connect.

AgentHub Connect · example
agentagent-factures → MS.ERP
pieceSupplier invoice F-1042
RisingCHF 1,284.60
account6500 · Office expenses · VAT 8.1 %
Statusdecision pending
To validateEdit and then confirmRefuse with reason
decisionvalidated by the financial manager
executionwritten by the gateway
newspaperProposal imprint retained · Content not stored
agentmonitoring agent
monthly ceilingCHF 120.00
alert threshold80 %
end-of-month projectiona trend, not a guarantee
alertalert threshold reached
ceilingRun refused · Agent put on pause
resumeautomatic when the budget allows, dated
■ Emergency stop · test agent
test agentONstopped
billing agentON
support agentON
calls in progressinterrupted
pending writingsfrosts
raisedby owner only · logged
general shutdowncut off all agents at once

Illustration screen: amounts, agents and account names are examples.

// Part 1 · Governance

Governance: who decides, and on what basis

AI agent governance is the set of rules that define what an agent is allowed to do, who authorizes it, and how it is verified. In AgentHub Connect, these rules are not a separate document: the console applies them itself.

01 · validation

No writing without a decision

Any action an agent wants to perform in a business application enters the validation queue. There are three choices: validate and execute; reject, with a logged reason that the agent also sees; or modify and then validate. In this case, the corrected version is executed, and the original proposal remains in the log. A request without a decision expires instead of executing by default.

02 · rules

Self-validation rules, if you wish.

For repetitive and low-risk transactions, an administrator can create a rule: one agent, one tool, a maximum amount per transaction, and a maximum number and total per day. Within these limits, the transaction is executed immediately and logged like any other. Without a rule, everything goes through a single person.

03 · register

A processing register per agent

Each agent carries their own record, completed according to the guidelines: purpose, legal basis, data subjects, and retention period. An agent without a record cannot be activated. These sections include some of those from the register of processing activities required by the nLPD (New Federal Act on Data Protection).

04 · stop

Pause, emergency stop, general stop

Pausing an agent prevents new runs and tool calls, with a logged reason. An emergency shutdown also interrupts its current calls and freezes its pending entries; only the owner can undo it. A full shutdown shuts down all agents at once.

05 · roles

Roles and an identity

We connect via WivenLLM, which identifies the person. Rights follow distinct roles, for example owner or auditor, so that the person who controls is not the one who operates.

06 · History

A history that cannot be erased

Every change to an agent is dated and attributed: a pause decided by a person, an automatic pause because the limit is reached, an automatic resumption when the budget allows again. In the event of an audit, you show the chronology instead of reconstructing it.

// Part 2 · Monitoring

Monitoring: what your agents are doing, live

Monitoring AI agents answers a simple question: is each agent doing its job right now, and at what cost? An agent failure is rarely obvious. More often than not, it continues running while producing errors, or it stops communicating without anyone noticing. We have described this risk here.

Health · billing agentlast 7 days
1,8 %24-hour chess
42 smedian duration
2 min 1095th percentile
readmymeIveitsdi

Example data

01 · Overview

A view that fits on a screen

Active, paused, or error-prone agents; recent failed or unresponsive runs; broken connectors; pending validations; open alerts. Recent runs scroll live. Each alert represents a problem, regardless of the number of repetitions: you won't be overwhelmed with fifty notifications for the same issue.

02 · journal

The Runs Journal

Each execution is logged with its time, trace, status (in progress, successful, failed, canceled, no updates), duration, number of documents and tokens, data categories affected, and cost. Filters retrieve all runs that accessed HR or health data in the past month.

03 · detail

A run in detail, step by step

Model calls, tool calls, anomalies: each step displays its duration, the data category involved, and its destination (no output, model on your infrastructure, business application). You see where the information went, without having to guess.

04 · no content

A journal that is not a copy of your data

The processed content (texts, documents, model responses) is not recorded in the log. Only its type, size, and a fingerprint are. The log proves what happened, by whom, and to where, without itself becoming a repository of sensitive data requiring protection.

05 · health

The health of each agent

Failure rates over 24 hours and 7 days, including runs with no response. Activity over the last seven days, median duration, and 95th percentile of runs. Connectors used, along with their calls and failures over 30 days. A drift is visible before it becomes an incident.

// budgetary safeguards

A ceiling that acts, not a report that observes

Each agent has a monthly limit, a limit per run, and an alert threshold, in francs. The safeguards act without waiting for anyone, but according to a rule you have set.

Monthly budget · monitoring agentceiling CHF 120.00
cost observedreserved by current runsalert threshold
■ Run refused · Agent on break · Alert open

Example data

  • Reservation before execution. Each run reserves its limit before starting. If there is no more space in the monthly budget, the run is refused, the agent is paused and an alert is opened.
  • Immediate pause in case of overrun. A run that is more expensive than expected or costs received late may cause the cap to be slightly exceeded: the agent is then put on pause without waiting.
  • Nothing is counted as zero by mistake. The prices of external models are entered in francs per million tokens, along with their country. An external model not listed in this table is never considered free: the agent is paused. A call counts as zero only if its host is among the models installed on your infrastructure, such as WivenLLM.
  • A transparent consumption pattern. Cost observed since the 1st of the month (Zurich time), portion reserved for ongoing runs, and end-of-month projection, presented for what it is: a trend, not a guarantee.

This is the technical translation of our pricing : external resources are billed back at cost, up to a limit that you set.

// where the console is running

From the model to the newspaper, all in your home.

AgentHub Connect runs on your infrastructure, alongside WivenLLM, which is also used to identify users. Calls to external models are only possible if they have been declared, along with their price and country.

LAYER 04
Your rulesvalidations, self-validation, limits, roles
LAYER 03
AgentHub Connectgateway, log, alerts, stop
LAYER 02
WivenLLMUser models and identity
LAYER 01
Your infrastructureYour data ends here
// connectors

Your software, behind a gateway

Agents access your business applications only through the gateway: tool by tool, with access secrets securely stored, and every call logged. The health of each connector is monitored every minute. A degraded connector is disabled for agents until it is restored, rather than allowing an agent to write to an unstable system.

Available in the current version of the console

GLPI · Teclib'’MS.ERP · Mediasoft

Planned

AbacusSAP Business OneProConceptImmomigMicrosoft 365 / SharePoint

For a complete list of the software our agents connect to, see the page Integrations.

// for whom

One console, four readings

Direction

Knowing what is automated, at what cost, and being able to stop everything with a single gesture.

Finance

Validate the proposed entries, set the ceilings, monitor consumption to the nearest franc.

Computer science

See failed runs, broken connectors, and the health of each agent, without digging through technical logs.

Data protection and auditing

Having access to the register by agent, the categories of data affected and a dated and attributed history, in read-only mode.

To learn more: The five safeguards to demand before letting an AI agent write to your ERP.

// regulatory guidelines

The texts that the console helps you respond to

These texts establish obligations. The console provides the means to fulfill them and to provide proof thereof; compliance remains the responsibility of your organization.

By sector: trustees · banks.

Frequently Asked Questions

What we are being asked about the governance of agents

What is AI agent governance?

This is the set of rules that define what an agent is allowed to do, who authorizes it, and how it is proven: validation of entries, self-validation rules, processing log per agent, roles, pause and stop, change history. In AgentHub Connect, the console applies these rules itself.

What is the difference between governance and monitoring?

Governance decides in advance what is permitted. Monitoring shows what is actually happening: runs, failures, connectors, costs, alerts. Budgetary safeguards link the two: a pre-established rule that is applied in real time.

Can an agent write anything in our ERP system on their own?

No, unless an administrator has created an auto-validation rule for that agent and tool, with a maximum amount per transaction and daily limits. Outside of these limits, each transaction requires human approval. It's always the gateway that makes the entry, never the agent.

Does the newspaper contain our documents?

No. The processed content itself is not recorded in the log: only its type, size, and a fingerprint are, along with the destination of each step. The log proves what happened without becoming a copy of your data.

What happens when an agent reaches their ceiling?

Each run reserves its budget before starting. If there is no more space, the run is rejected, the agent is paused, and an alert is opened. It resumes when the budget allows again, and each pause and resumption is logged.

Where does AgentHub Connect run?

On your infrastructure, alongside WivenLLM, which is also used to identify users, calls to external models are only possible if they have been declared with their price and country.

// sources
// demonstration

See the console on your own cases

In twenty minutes, we show you AgentHub Connect with an agent close to your needs: validations, log, limits and stop.