Protect your whole organization —
with work accounts, not personal Gmail
Browser security for every browser you manage. Employees sign in with their work e-mail or your own single sign-on, you push the extension from the tools you already use, set the policy once, and see who is protected and who is under attack — without ever seeing what anyone browses.
14-day full-strength trial for the whole organization · no card · per-seat pricing after
Up and running in three steps.
No agents to deploy, nothing to migrate. Create the organization, bring your people in, push the extension to their browsers.
- 1
Create the organization
Sign in with your work e-mail, name the organization and add your company domain. You are the owner. Nothing about your personal Google account is involved.
Getting started → - 2
Invite — or auto-join by domain
Paste a list of addresses with a role, or verify your domain with one DNS record and let anyone at @yourcompany join as an employee the first time they sign in.
Inviting people → - 3
Push the extension, set the policy
Require the extension, push it as a managed install, lock a setting pack, decide the work-account rule on company devices. Then see coverage and threats across the organization.
Policies →
Sign-in that fits your company. Not the other way round.
One login box for everyone. The domain of the e-mail decides how a person signs in — nobody picks a provider, and a personal Google account is never accepted for a company address.
Work e-mail code
Your employee types their work address and receives a 6-digit code and a one-click link at that address. Valid for ten minutes, single use. Works the moment your domain is verified — no identity provider needed.
- Nothing to configure, nothing to install on your side
- Same flow on the web dashboard and in the browser extension
- Can stay on as a break-glass fallback once SSO is live
Your single sign-on
Plug in the identity provider you already run. OKY uses standard OpenID Connect, so your MFA, device rules and off-boarding apply automatically. Map a group to the OKY admin role and you are done.
Any other OpenID Connect provider works too — you paste an issuer URL, a client ID and secret.
What your admins see. And what they never do.
The corporate dashboard answers three questions: who is protected, who is being attacked, and what needs a decision. It does not see anyone's browsing.
Coverage
Seats used, who has the extension, who lost it, who signed in with a personal account on a company device — and who is still unprotected.
Threats
Threats blocked today, this week, this month — phishing pages, fake logins, malicious downloads, scam addresses. Filter by member, type or period. Export as CSV.
Members
Everyone in the organization with their role, coverage and last activity. Invite, remove, promote. Pending invites in one list.
Audit log
Every invite, role change, policy edit and sign-in method change, with who did it and when. Exportable.
Managed deployment
Push OKY to your team's browsers from Workspace, Intune, Jamf or GPO — a managed install cannot be removed by the member. The dashboard generates the configuration for each platform. On machines you do not manage, OKY tells you when someone's protection disappears, and can pause their dashboard until it is back.
Your own API keys
Bring your organization's own keys for the reputation and AI services behind OKY's checks. Every scan by your people then runs on your accounts and quotas — add, test, rotate, remove in one place.
Three roles. Clear lines.
Every membership carries one role. Owners run the company account, admins run security, employees are protected. Roles are scoped to your organization — nothing leaks between companies.
| Capability | Owner | Admin | Employee |
|---|---|---|---|
| Own dashboard, scans, connected accounts | ✓ | ✓ | ✓ |
| Organization overview, coverage, member list | ✓ | ✓ | — |
| Invite and remove members, admin ↔ employee | ✓ | ✓ | — |
| Domains, sign-in method (SSO), policies | ✓ | ✓ | — |
| See a member's threats (never clean pages or browsing) | ✓ | ✓ | — |
| Audit log and CSV exports | ✓ | ✓ | — |
| Promote or demote owners, billing and seats, delete organization | ✓ | — | — |
At least one owner always remains. Full detail in the roles guide →
We onboard pilot organizations by hand.
Tell us your domain and who should own the account. We create the organization, verify the domain with you, invite the owner and stay on the line while the first employees sign in and install the extension. Public-sector and regulated teams: ask us about data residency and self-hosting.
- Day 1 Organization created, domain verified, owner signed in with a work e-mail code.
- Day 2 Policy set: required extension, locked setting pack, managed deployment pushed. First employees auto-join.
- Week 2 Owner reviews the org overview: coverage, threats blocked, who still needs the extension.
Questions teams ask first.
Everything else is in the corporate docs.
We're just one
message away.
Questions, ideas, or a threat you want checked? Reach out and we'll show you exactly how OKY fits into the way you already work — in your browser, and across your whole organization.