Households and family offices that ask hard questions already have answers they trust: Okta for who gets in, Duo for making sure it is really them. Tidemere joins that system instead of asking anyone to manage one more password.
Serious households and family offices already run identity the way serious companies do: one directory of who belongs, one place to add a person, one place to remove them. The worst thing new software can do is sit outside that system with its own logins and its own forgotten-password flow.
Tidemere plugs into the directory instead. Okta decides who can sign in. Duo confirms it is really them at the moments that matter. And when someone leaves the organization, their access to Tidemere ends where everything else ends: in the one place the organization already controls.
Staff sign in to Tidemere with the account their organization already manages. There is no separate Tidemere password to create, remember, or reset, and no orphaned account waiting to be forgotten about.
The directory stays in charge. Add someone in Okta and they can sign in; choose which groups have access and Tidemere honors it; remove someone once and every connected application follows, the same hour.
On sign-in, or before a sensitive action, Tidemere asks Duo to confirm the person is who they claim to be, usually a single tap on their phone. The organization's own policy decides which actions warrant the prompt; Tidemere enforces it.
Tidemere never sees how the person verified. Duo reports only that the check passed. The security detail stays with the security system.
Okta and Duo connect to Tidemere the same way Google, Microsoft, and Notion do, because it is the only pattern worth trusting.
Your admin chooses exactly what each connection may see and do. Typically a name, an email address, and group membership. Nothing more is visible to us.
Every credential can be turned off at any moment from your own console, with no call to us required. If a connection ends, there is nothing left behind to retrieve.
Tidemere never sees or stores a password, for anything, ever. Keys are issued by your systems, to your rules, and they work only for what you granted.
From their own admin console, they register Tidemere as an application and choose which groups may sign in. Nobody at Tidemere touches your directory.
As a protected application, with your own policy for which actions require the prompt and how often.
Credentials that work only for what was granted, revocable from your own consoles at any moment. From then on, sign-in and verification simply work, and your directory stays the single source of truth.
No Okta or Duo yet? Tidemere also runs standard sign-in with its own verification for organizations that have not adopted an identity platform, and moves to this pattern when you do.
The fastest version of this conversation includes whoever runs your identity systems. They will have questions; we like those.