Add an authenticator check to remote sign-in.
Bliss MFA brings authenticator codes to Windows Remote Desktop, with a local portal for configuring protected users and enrollment.
Start a verified-account 14-day free trial for one protected Windows/RDP account. No credit card required and no automatic charge.
Designed for your administrator
A guided path to protected access.
Configure locally
Create your appliance owner and enroll existing local Windows accounts through the browser portal.
Verify before enabling
Confirm a fresh authenticator code through the Windows client before turning on RDP protection.
Prepare recovery
Keep a tested recovery administrator available and protect appliance state with encrypted backups.
Planned client journey
From subscription to your first protected user.
- Create your account
Verify your email and choose your protected-user seats.
- Subscribe & download
Start the verified-account trial or choose a paid plan in the customer portal, then download the Windows package and generate activation details.
- Install & enroll
Run setup as an administrator, create your local owner, activate the license, and verify enrollment.
- Enable & test RDP
Confirm recovery access, enable protection, and test sign-in with your authenticator.
Free trial
Try one protected Windows/RDP account free for 14 days.
Create and verify your client account, then start your trial from the customer portal. No credit card required and no automatic charge. The trial starts only when you click the trial button in the portal. One trial is available per verified client account.
Upgrade to a paid plan any time and keep the same appliance and authenticator enrollment.
Subscription
Choose the seats you need.
per protected user, per month
Monthly subscription. Applicable taxes and the final total are shown at checkout. Installer downloads stay behind the customer portal.
Before you get started.
What do I need to install it?
A Windows machine with administrator access, an authenticator app, and a tested recovery account. The prototype has been exercised on Windows 10 Pro; broader Windows compatibility and the new clean-install package still need acceptance testing.
Where is my information stored?
Your appliance manages Windows users and authenticator enrollment locally. The hosted account portal manages subscriptions, licensing, and downloads. Windows passwords and enrollment keys are not collected by this page.
Does this use the WooCommerce checkout?
Bliss MFA uses a separate client account portal and Stripe subscription checkout. Your existing WooCommerce store remains available for its other products.
Can I deploy it to my whole team today?
This is a prototype preview. Public payment-to-activation, clean installation, and additional RDP acceptance checks must pass before general client rollout.
Windows local console
The revised dashboard lives inside the Windows application.
The updated Bliss MFA console is the local Windows application interface your team opens on the protected machine. It is not a WordPress dashboard, and it keeps customer setup and day-to-day MFA administration close to the appliance.
Account management and enrollment
Review protected accounts, manage authenticator enrollment, and guide users through onboarding from the local console.
Disabled or revoked account management
See disabled or revoked account states clearly so administrators can clean up access without guessing which record needs attention.
Recent authentication-management events
Recent authentication-management events help administrators understand what changed, when it changed, and what still needs follow-up.
Access to onboarding, administrators, audit and licensing
Jump to onboarding, administrators, audit, and licensing areas from the same local console.
Product updates
Bliss MFA updates stay controlled through the customer portal.
Keep installer downloads inside the customer portal. Purchase, trial, approved downloads and license actions all stay connected to your Bliss MFA customer account.
Existing installations need a one-time updater setup before this update path can be used. Tested migration instructions will be provided separately before we link customers to that setup.