Access Broker Deployment

The Britive Access Broker is a lightweight Java service that runs inside your infrastructure and lets the Britive platform manage just-in-time access to resources that aren’t reachable as cloud applications — servers, databases, network devices, and Kubernetes clusters. The broker opens an outbound HTTPS connection to Britive, so no inbound firewall rules or public endpoints are required.

Deploy it once, then point any broker-based integration (Linux, Windows, databases, Cisco, VyOS, and more) at the broker pool it registers with.

How It Works

    flowchart LR
    subgraph YourInfra["Your Infrastructure"]
        Broker["Access Broker<br/>(runs in your env)<br/>Runs checkout / checkin routines against targets"]
    end

    subgraph BritivePlatform["Britive Platform"]
        SaaS["Britive SaaS<br/>&lt;tenant&gt;.britive-app.com"]
    end

    Broker -->|"outbound HTTPS:443"| SaaS
  

At startup the broker reads broker-config.yml, registers with the Britive platform using a broker pool token, and waits for checkout/checkin instructions. Network requirement: outbound HTTPS (port 443) to *.britive-app.com. No inbound rules needed.

Choose a Deployment Option