The first meaningful improvement on MFA in over a decade.

Threshold approvals and enterprise policy for shared privileged accounts: exchange admins, banking portals, and registrars.

  • Built on MPC
  • No shared secret
  • SOC 2 Type 2
AUTHENTICATOR treasury@acme 4 8 2 9 1 3 Threshold approval 2 OF 3 REQUIRED AW MC RH Copy code 482 913 acme-okta-login.co Verify it's you Enter your 6-digit code 482 913 Code captured

MFA still rests on a secret anyone can copy.

  • Phishable shared secrets

    A six-digit code typed into the wrong page works just as well for the attacker.

  • Codes copied across devices

    Shared accounts mean the same seed lives on phones, laptops, and password managers.

  • Costly offboarding

    When someone leaves, every account they could reach needs its seed rotated by hand.

  • Standing credentials

    Seeds sit on devices around the clock, waiting to be stolen.

No single party ever holds the full MFA key. Access requires a threshold approval.

Castle splits the key with multi-party computation. Shares combine only when your policy is met, and only long enough to produce one code.

Where the MFA key lives

TodayOne seed, copied to every device that needs a code.
With CastleKey shares that combine only when the threshold is met.

Technical deep dive

Request the Castle technical whitepaper

Architecture, threat model, and cryptographic design in depth. Reviewed and sent personally by our team.

Work email required.

Request received. Our team will review it and send the whitepaper to your inbox.

From request to code in one approval flow.

Start from the login you already trust.

Users sign in to Castle through your identity provider. Groups and roles flow in from SSO, so policy follows your org chart.

  • SAML and OIDC supported
  • No new passwords to manage

Works with

  • Okta
  • Microsoft Entra
  • Google Workspace
  • Any SAML or OIDC provider

Key shares in hardware. Nothing readable at rest.

Key shares live in AWS Nitro Enclaves and HSMs. Storage is zero-knowledge, so Station70 cannot reconstruct a key on its own.

Harden your most sensitive accounts.

See threshold approvals running against your identity provider in a 30-minute technical briefing.

Request the Castle technical whitepaper

Architecture, threat model, and cryptographic design in depth. Reviewed and sent personally by our team.

Request received. Our team will review it and send the paper to your inbox.

By submitting, you agree to be contacted by Station70. We never share your information.

Thank you. We will be in touch.

Your message is on its way to the Station70 team. Expect a reply within 1 business day.