Try Access Dealer free for 30 days — no credit card. Business email required.

Architecture deep dive

How Access Dealer works.

Follow a privileged request from approval to outbound brokered session, recording, expiry and audit evidence.

No credit card · Business email · Limited trial capacity

Access DealerRequestsSessionsRecordingsEntitlements
JIT request queue3 pending
RequesterTargetDurationStatus
alice@acme.examplePostgreSQL owner · acme-prod-db45mApprove
ben@acme.exampleKubernetes edit · payments30mPolicy ok
vendor-7RDP · web-0190mReview
Approvals / ChatOps

alice@acme.example requests acme-prod-db for incident INC-1042.

ApproveDeny
$ access-dealer connect acme-prod-dbrecording: transcript + keystrokesexpires in

Architecture

Built so operators cannot read your secrets.

The broker dials out over mTLS. Each tenant has a dedicated database and per-tenant envelope encryption. Sessions are recorded without exposing vaulted secret values to operators.

Dedicated database per tenantPer-tenant envelope encryptionNo operator read path
Your adminsAccess Dealer (your tenant)Your networkBrowserCLISlack / TeamsControlplaneRelayTenant DBone per tenantRecorderKeyhierarchyNo inbound rulesBrokerTargetsSSH · RDP · DBsKubernetesoutbound mTLS · 443
Policy and session flowOutbound broker tunnelTenant-isolated data

Click the architecture nodes

Click the SVG nodes or use the keyboard buttons to inspect each part of the access path.

Envelope encryption key hierarchy

1

Master key

Key material is sealed under a master key outside the tenant database.

2

Per-tenant key

Each tenant key is separate from every other tenant's key.

3

Data keys

Data keys encrypt records with AES-256-GCM and are wrapped by the tenant key.

4

Encrypted records

Operators never receive vaulted secret values through the application path.