Password Manager Browser Extension

The right credential for the right domain.

Explore Dayrook’s implemented browser companion for the vault: domain-aware autofill, password generation and controlled access. Signed releases and supported browser versions still need confirmation.

Book a walkthrough Estimate platform pricing

Implemented client · check distribution ↗

Conceptual browser, protected vault, origin check, and approval gate connected in one controlled path.

Every access has a boundary

Useful access. Explicit control.

Match permitted items to the active domain and client context.

Illustrative workflow · explore the steps · no action is executed

Register and unlock

Bind the extension to a trusted user session, device identity, password-manager policy, and encrypted cache.

Confirm this step for your release, permissions and environment.

Put the approved credential in the correct domain context.

Bind extension access to an enrolled device, session policy, Vault grant, and revocation state.

Inside the workflow

The work this connects.

Browser coverage: Apply one password-manager policy model across browsers included in the verified release matrix.
Autofill and autosave: Offer scoped login use and encrypted item capture only after domain and access checks.
Password generator and TOTP: Create passwords and use permitted TOTP records without exposing seeds to logs or analytics.
Secure Send: Create and manage approved expiring shares from the extension workflow.
Encrypted offline cache: Permit policy-controlled read access and carefully governed queued writes while disconnected.
Sync conflict handling: Resolve version conflicts explicitly so an offline or concurrent change does not silently overwrite data.

Browser workflow evaluation

Evaluate the trust path before planning a browser rollout.

Review the intended origin matching, Vault scope, policy gate, revocation, and evidence flow against the browsers your technicians use.

This action reviews the implemented workflow and its release boundaries. It does not offer a public extension package or claim a signed release is available.

Review the extension workflow

Try one useful scenario

Credential custody and revocation

Fictional example: revoke a user while their client is offline, then attempt access before and after reconnecting. Test the approved offline expiry and confirm which cached items remain accessible.

Illustrative evaluation scenario, not a recorded product result.

What a useful result must show

Record who can decrypt each credential class, recovery authority, local expiry, domain-match result and the observed revocation boundary. Inspect what leaves the client for breach checks.

Get the evaluation worksheet →

Check the support boundaries

End-user encrypted vault items
Automation credentials authorized for execution
Recovery and offline access
Browser domain matching, biometric fallback and push privacy

The mobile app and browser extension are planned surfaces; signed distribution and a tested release are not evidenced here. A zero-knowledge claim for user vault items must not be generalized to automation credentials an executor is authorized to decrypt.

Check public evidence and availability →

Scope, availability and evaluation details

Browser support and store distribution vary by the applicable signed release.

Offline cache, reveal, fill, save, and export can be disabled or bounded by tenant policy.

The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →

Review full environment and integration scope

Browser-store distribution

Signed store releases require versioned manifests, permissions review, privacy disclosure, rollback planning, and deployed browser QA before public availability is claimed.

Digital Vault-bound sync

Autofill, autosave, generator, TOTP, secure send, and permitted offline state use Digital Vault APIs plus an extension-device verifier; conflict handling prevents silent overwrite.

The extension uses the same Vault collections, policies, trusted-device, MFA, audit, and revocation owners as the main workspace.

Questions, answered

Before you choose your next step.

Which browsers will be supported?

Chrome, Edge, and Firefox are the first target release paths. Safari is later, subject to platform capacity. Confirm the current signed release and browser QA status during evaluation before planning a rollout.

Can it work offline?

A policy-controlled encrypted cache can support offline access. Write behavior depends on tenant policy and explicit conflict handling.

Does autofill use loose URL matching?

No. Domain-aware rules and lookalike checks are part of the trust decision before credentials are offered.

Can an administrator revoke an extension device?

Target design: Revocation ends active sync authorization and is reflected in trusted-device and audit state.

Your next step

Check release availability before planning a rollout.

Confirm the signed extension, supported browser version and vault behavior. Use the current availability record to decide whether to include it in an evaluation.