What’s next, and exactly where it stands.
Everything else on this site is built. Here’s what we finished most recently and what’s on the way, labelled honestly: built, early access, coming soon, or proposed.
What’s next.
Everything above this section is built. Here’s what we finished most recently, and what’s on the way, each labelled with exactly where it stands.
Built and tested like the rest of LayerT. LayerT runs in a test environment with dummy data. Production is not deployed.
A new browser gets no rules and no shared accounts until an Owner or IT Admin approves it on Devices.
People can set up LayerT themselves: they type their work email and sign in through your company’s own sign-in. No token to paste.
Each browser’s credential is tied to a key made in that browser that can’t be exported.
Stop a file by its name, or by the text inside a plain-text file of up to 1 MB. A file LayerT can’t read is stopped by a rule about file text.
A rule can act on text typed into the fields it names. It tells the person, and stops the text being sent with a form, a submit button or Enter.
A rule can apply to a directory group, or to everyone outside one.
On a form or paste rule, people can continue past a block by giving a reason. It’s recorded with their name before anything proceeds.
LayerT fills a sign-in form shown in a frame from the same site, and says which address the form belongs to.
An account can list the other sites it uses, such as a separate sign-in address.
A page lists what changed in LayerT, newest first, in plain words.
A warn rule shows your message with Go back and Continue. Continuing is logged.
Requests reach approvers by email, in Slack and in the browser, as well as in the console Inbox.
Seeing a stored password takes two approvers, one of them an Owner or Compliance Officer. It’s shown once.
Owners, Compliance Officers and the account’s owner hear straight away.
Filter by person, rule, account or date, export what you see, and mask values rule by rule.
Each quarter, account owners confirm who still needs access, seeing who actually used it.
Which shared-account sign-ins worked, and where the others stopped, in words.
Account ID, organisation ID and PIN fields, plus notes on each shared account.
In the toolbar popup, for the person signed in, if a code doesn’t go in by itself. Views are logged.
Bring shared accounts across from an export. The preview never shows a password.
See who reaches which account through which route, at a glance.
Codes a vendor emails to a shared inbox are filled in for whoever is signed in. Switched off in production until LayerT’s compliance review.
Read a team inbox in the console, with approval, a watermark and every email logged. Switched off in production until the same review.
Keep a vendor’s “remember this device” cookie, so people aren’t asked to verify every time.
What needs you, what’s live and what needs fixing, on one page.
Built. In use in the test environment; production is not deployed.
So people can’t remove LayerT from a managed browser. Built; switched on with the first production release.
Send a shared account through a gateway on a server you rent, so the vendor sees one address it can allow-list. Off for every account until you switch it on.
Rent a small server with a static IP, paste one command, and manage it from the console.
The vendor’s first sight of the session is the gateway, and a chip on the page names the gateway and the address the vendor sees.
The sign-in isn’t opened when its gateway can’t be reached, unless you set the account to go direct.
Built and tested; it has run in our test environment only.
LayerT in more browsers.
Exports are logged today. An alert would tell Owners as they happen.
A log whose history can be checked, not only protected by access control.
Today a Team Approver can decide requests across the organisation.
LayerT changing a shared password at the vendor by itself.
Want a say in the order? Request a demo and tell us what you need first.
Put a layer on the browser.
LayerT is pre-launch and taking demo requests. Tell us what you want to solve, and we’ll show you the product doing it.
