Skip to content

Mideye: On-Premises MFA for VPN & Apps

Mideye Server is an on-premises multi-factor authentication (MFA) platform. It integrates with your existing infrastructure to protect user logins with a second factor — without replacing your identity provider, VPN, or password system.

  • Adds a second factor to existing logins. Users authenticate with their password first, then verify with a push notification, SMS code, hardware token, or TOTP app.
  • Speaks protocols your infrastructure already uses. RADIUS for VPNs and firewalls. REST API for web applications. LDAP for user directories.
  • Runs on your infrastructure. Authentication decisions happen on your server, with your data, under your control.
  • Delivers OTPs through Mideye’s cloud services. SMS and push notifications are routed through Mideye Switch and Mideye Cloud — but your credentials never leave your network.

Setting accurate expectations:

  • Not a VPN. Mideye authenticates users; your VPN handles the tunnel.
  • Not an identity provider. Mideye adds a second factor to existing authentication, it doesn’t replace Active Directory, Entra ID, or LDAP.
  • Not a password manager. Users still need their primary credentials.
  • Not a single sign-on solution. Though it integrates with ADFS and other identity providers for federated MFA.

Mideye Server is designed for organizations that:

  • Need MFA for VPN, remote access, or network equipment (via RADIUS)
  • Want to add MFA to web applications (via REST API / Magic Link)
  • Require on-premises control over authentication decisions and user data
  • Operate in regulated industries where data residency matters

Mideye Server runs on:

  • RHEL / Rocky / Alma 8.x and 9.x (RPM)
  • Debian 11, 12, 13 and Ubuntu 22.04, 24.04 (DEB)
  • Windows Server 2016–2025 (MSI)
  • Docker / Podman (container image)

See Pre-install Checklist for hardware and software requirements.

Most MFA solutions today are cloud-only — your authentication data, user records, and login decisions are processed on the vendor’s servers. Mideye Server takes a different approach:

AspectCloud-only MFAMideye Server
Authentication decisionsVendor’s cloudYour server
User data locationVendor’s infrastructureYour database
Internet dependencyRequired for all MFAOptional — air-gapped TOTP works offline
RADIUS supportOften proxy-based or limitedNative RADIUS server + RADSEC
Data sovereigntyVendor’s jurisdictionYour jurisdiction
Vendor lock-inSDK/agent integrationStandard RADIUS — works with any VPN/firewall
Compliance postureDepends on vendor certificationsYour infrastructure, your auditors, your control

Mideye isn’t anti-cloud — it uses cloud services for SMS and push delivery. But the authentication engine, the credentials, and the decision-making stay on your premises. This is a fundamentally different trust model.

For a deeper comparison, see On-Premises vs Cloud MFA.

Mideye Server is licensed per user. Contact sales@mideye.com for pricing.

Trial licenses are available for evaluation.