Commander on Besu

Run your network on Besu. Govern access with Commander.

Add Prividium Commander on top of your existing Besu instance to manage participant access and permitted contract actions. Retain your chain, applications and network governance while checking requests against configured permissions.

Request a walkthrough

Shared infrastructure. Defined participant permissions.

Bring institutions onto your existing network

Use Commander to manage participant access to a supported shared Besu instance. Institutions use the same underlying chain, with requests checked against their assigned roles and permissions.

Keep the infrastructure you operate

Besu continues to execute transactions using the network’s existing consensus and settlement model. Commander adds authorization to the request path.

See Commander on top of Besu

Illustrative deployments. Operators retain responsibility for node access, data visibility and network governance.

A participant submits a request
An institution’s application submits a contract instruction through Commander.
Commander checks permission
Commander checks whether the participant may invoke the requested contract function. An unauthorized request is refused at this layer.
Besu executes the authorized request
A permitted request proceeds to the existing Besu instance. Execution remains subject to the contract’s rules and the chain’s processing.

What Commander adds

Participant access and roles

Define who may access the environment and which contract actions each participant may request.

Contract and function permissions

Configure authorization for the contract functions your applications use. Permissions apply to requests passing through Commander. [1]

Visibility into authorization decisions

Review permission decisions at the authorization layer. Failures inside Besu’s nodes are outside that view.

What your network continues to operate

Nodes, applications and governance

Your network operators retain responsibility for Besu, deployed contracts, consensus and governance. Connect identity, applications and signing to the authorized request path.

Access paths and data visibility

Identify every route into the network, including direct node access. Commander does not govern requests that bypass its authorization layer. On shared infrastructure, confirm what participants and node operators can read; participant permissions do not create separate private ledgers.

[1] Prividium documentation: role and contract/function permissions.

Map Commander onto your Besu network

Bring your Besu setup, participating institutions and required contract actions. We will work through the permission model, access paths and integration work for your first workflow.