Product architecture

Identity proves who you are. FirmBrowser governs what happens next.

A managed browser and secure access orchestration layer that controls the device, hides the password, protects the session and governs what users can do inside cloud applications.

Technical architecture overview — tap or click to view full size.

Layer 1 — Identity

Who are you?

  • Active Directory
  • Microsoft Entra ID
  • Okta
  • Google Workspace / Google Identity
  • Other SAML / OIDC providers
  • Federated identity services

FirmBrowser is designed to work alongside these identity platforms. Vendor names are shown for architectural context only and do not imply partnership or endorsement.

Authenticated user
Layer 2 — FirmBrowser

How may you access and use this app?

Managed Browser + Secure Access Orchestration Layer

  • Authentication orchestration
  • Password isolation
  • Managed browser
  • URL Rules
  • Element Rules
  • Credential Lockdown
  • Data movement controls
  • Audit & session evidence
Correct authentication path chosen
Layer 3 — Application

What can you actually do once inside?

Path A — Native SSO apps

FirmBrowser hands authentication to your approved identity provider, then continues applying browser and post-login controls.

Path B — Recipe-driven web apps

FirmBrowser executes an authorised App Recipe so the user never needs to know, type or store the credential.

Outcome: a controlled application session — governed, audited and low friction.
Recipe Library

A library of pre-built, verified App Recipes

Browse an expanding library of recipes for the applications firms use every day — pre-built, tested and ready to assign in seconds. If an app isn't in the library, we build a recipe for it.

The FirmBrowser Recipe Library — pre-built, verified and ready to assign. Tap or click to view full size.

Any app your firm uses — if it isn't in the library, we can build a recipe for it.

01Capability

Identity integration — FirmBrowser complements, it does not replace

FirmBrowser integrates with the identity platforms firms already run — Active Directory, Entra ID, Okta, Google Workspace and other providers. Your identity provider proves who the user is. FirmBrowser controls how browser-based applications are then accessed, used and audited.

Identity Provider
FirmBrowser
Policy
Cloud App
02Capability

Controlled access from approved devices

FirmBrowser helps prevent critical cloud applications being accessed from unmanaged, personal or unauthorised devices. Device posture is evaluated before an application ever opens.

User
Device Check
Policy Check
FirmBrowser
Cloud App
03Capability

Recipe Books — one per user

Each user receives a personalised Recipe Book containing only the authorised application definitions and policies their role requires. Access is centrally provisioned, centrally changed and centrally removed.

  • Role-based application sets
  • Central provisioning
  • Instant revocation on exit
  • No shared credential lists
  • Consistent policy per role
Recipe Books — one per user
04Capability

App Recipes and password isolation

An App Recipe is far more than a stored username and password: it defines how the app is reached, how authentication is performed, and what the user may do once inside. Each app can carry a unique, complex password that users never see, type, copy or store.

  • Automated login
  • Unique complex passwords
  • No password reuse
  • No password sharing
  • Reduced reset pressure
  • Reduced credential exposure
App Recipes and password isolation
05Capability

Automated login saves real time

Users click the application and FirmBrowser handles the login sequence. Across a day of repeated logins, MFA prompts, resets and lockouts, firms can recover a meaningful amount of productive time per user — in some cases over an hour per day.

Automated login saves real time
06Capability

Managed browser — the browser is part of the security boundary

If credentials are supplied automatically to sensitive cloud applications, the browser cannot be an uncontrolled environment. FirmBrowser turns the browser into a governed enterprise application-access environment.

  • DevTools disabled
  • Extensions centrally controlled
  • FirmBrowser extension enforced
  • Credential viewing prevented
  • Protected browser context
  • Policies users cannot change
Managed browser — the browser is part of the security boundary
07Capability

URL Rules — control where the application can go

URL Rules govern links and form destinations inside a browser-based application, so FirmBrowser can reshape application navigation without requiring the SaaS vendor to change anything.

  • Block sensitive destinations
  • Redirect to approved workflows
  • Prevent admin and billing paths
  • Prevent tenant switching
  • Contain the session
URL Rules — control where the application can go
08Capability

Element Rules — control what the interface offers

Administrators identify page elements and apply policy to them. The user sees only what their role requires — point, click, control.

  • Hide Settings
  • Remove Administration
  • Remove Forgot/Change Password
  • Remove Export
  • Disable Download
  • Remove Print
  • Hide Delete
  • Hide billing controls
Element Rules — control what the interface offers
09Capability

Credential lockdown and mail flow re-routing

Hiding a password is only half the job. Many SaaS apps still expose “Forgot password”. FirmBrowser can integrate with enterprise messaging controls so identified reset and recovery messages are diverted into a controlled security workflow instead of being handed to the user.

  • Reset paths removed in-app
  • Recovery mail intercepted
  • Security-team approval workflow
  • Prevents password-isolation bypass
Credential lockdown and mail flow re-routing
10Capability

Data movement controls

FirmBrowser helps control what can leave the browser.

  • Copy
  • Paste
  • Download
  • Export
  • Print
  • Screen capture
  • Session recording where required
Data movement controls
11Capability

Role-based app launcher

Users see only the cloud applications they are allowed to access.

  • Accounting
  • Tax
  • Payroll
  • Legal Practice
  • Documents
  • CRM
  • Financial Planning
  • Banking
  • Client Portal
  • Compliance
Role-based app launcher
12Capability

Audit and reporting

FirmBrowser records access and policy events to help owners, partners, managers, IT and compliance teams understand usage and risk.

  • User login
  • App launched
  • Device used
  • Access allowed or blocked
  • Copy/paste events
  • Download attempts
  • Print attempts
  • Export attempts
  • Workflow restrictions
  • Session recordings where enabled
Audit and reporting
13Capability

Session recording

For higher-risk workflows, FirmBrowser can support session recording so firms can review activity, investigate incidents, support compliance reviews and create evidence of controlled access. Presented as an optional compliance and investigation feature — not employee surveillance.

Session recording
14Capability

Admin control plane

A single admin dashboard for users, roles, identity providers, apps, device policies, Recipe Books, URL and Element Rules, credential policy, risk alerts, audit logs, session recordings, reports and compliance evidence.

  • Users
  • Roles
  • Identity providers
  • Apps
  • Device policies
  • Recipe Books
  • Rules
  • Audit logs
  • Session recordings
  • Compliance evidence
Admin control plane
15Capability

Deployment model

FirmBrowser can be deployed as a managed secure browser access environment for firms that rely on browser-based cloud applications.

Deployment model

See how FirmBrowser controls the browser.

A tailored demonstration for your firm's cloud application stack.