Frequently asked questions.

Antivirus software and a firewall protect against different things than Syspeace does. Syspeace runs directly on the protected server and watches for repeated failed sign-in attempts and other suspicious authentication activity, then blocks the offending IP addresses — a layer of protection that sits in front of the sign-in surfaces those other tools don’t focus on.

See the product overview for how detection, blocking, management, and reporting fit together.

Syspeace Service follows the Windows Security event log for sign-in failures. This requires that Windows is actually configured to log those events — see Enable Windows audit logging for sign-in attempts for the steps.

Syspeace AB is a Swedish company. If you’re located in the US, Syspeace has an EIN from the IRS as well as a signed W-8BEN-E form.

For anything else, contact support directly.

New Syspeace accounts receive a full 30-day trial with no credit card required. The trial installs the same Syspeace Service and Syspeace Console used in a licensed deployment — there’s no separate “trial edition” with reduced functionality.

See the trial page for the full onboarding walkthrough, and what to review before relying on trial results for a production rollout.

No. Syspeace is not intended or supported for use on Windows client operating systems. The Syspeace End User License Agreement does not cover that scenario, licensed or not.

Syspeace is built for, and only supported on, Windows Server. See the version comparison for which Windows Server releases each Syspeace generation supports.

From the downloads page, which lists Syspeace v4 and Syspeace v3 packages with file size and SHA-256 checksum for each. See the version comparison if you’re not sure which generation fits your Windows Server version.

Compare the SHA-256 checksum of the file you downloaded against the value published on the downloads page for that exact package. See Verifying a downloaded installer checksum for the exact commands on Windows, macOS, and Linux.

Syspeace uses a floating license model: licenses are bought per computer per day, but are not tied to any specific computer. You’re free to move the Syspeace application between computers in your environment as needed, with no separate web-based deactivation or activation step.

When you register Syspeace for the first time, you receive a license key that you can reuse on all subsequent Syspeace installations. That shared key is what makes the floating license model work with minimal administration.

Syspeace licenses are version-agnostic — the same license pool works with both Syspeace v3 and Syspeace v4.

Syspeace is licensed per protected server, per day, with a discounted rate available for larger deployments. See the pricing page for current prices and the verification date — exact amounts are kept in one place there rather than repeated here.

Yes. Licenses are priced per day — you choose the start date and length in days for each license, not just fixed 30-day blocks. See the pricing page for the daily rate.

Yes. Add or reduce licenses to match your actual server count at any time — you’re not locked into a fixed quantity. You can also combine multiple licenses covering different server counts and date ranges to match changing requirements. See Pricing for how the flexible model works.

No. Licenses belong to your Syspeace account rather than being permanently assigned to individual server hardware. You can replace or upgrade a server without buying another license solely because the underlying hardware changed. See Pricing for the full licensing model.

No. You pay only for the servers Syspeace is installed on and protecting — not for the administrator computers used to access or manage them through Syspeace Console. See Pricing for details.

Automatic renewal is available and is opt-in per license — you can turn it on or off for each license individually, at any time. See Pricing for the full licensing model.

Yes, a discounted per-server rate is available for larger deployments. An eligibility threshold hasn’t been published — use the Syspeace license portal or contact support to confirm whether your deployment qualifies and get the applicable price. See Pricing for the current volume rate.

Syspeace v4 blocks directly through the Windows Filtering Platform (WFP), rather than by adding rules to Windows Firewall. This keeps blocking working even when Windows Firewall is disabled, or managed by another security product.

See the version comparison for how this differs from Syspeace v3.

Syspeace v3 blocks by adding a rule to Windows Firewall, or to IP Security Policy. If Windows Firewall is disabled, or managed by another piece of software, configuration may be required to switch blocking over to IP Security Policy instead.

Syspeace v4 changes this — see the version comparison for how v4 blocks directly through the Windows Filtering Platform instead.

Whether a successful sign-in resets the record of prior incorrect sign-in attempts is configurable in the Syspeace settings.

Nothing in particular. Connections from a blocked address are simply dropped, which usually just gives the attacker a generic connection error. Beyond that, the attacker is not made aware of Syspeace, or that they have been specifically blocked.

Syspeace blocks IP addresses, not individual attackers. IP addresses are reassigned periodically, so the address behind today’s attack could belong to a legitimate customer tomorrow. If an address is seen returning as an attacker, a stricter rule can be used to extend how long it stays blocked, or the address can be added to a local blocklist.

Maximum block duration differs by version — see the version comparison for the current figures.

When a block contributes to the Global Blocklist, Syspeace sends:

• The local IP address and hostname of the protected server
• The IP address of the attacking address, and its hostname as resolved by DNS
• A traceroute from the server to the attacking address
• The point in time the attack happened
• The version of Syspeace and of Windows in use
• The Syspeace account ID

This information is used to identify addresses attacking many computers, whether within one Syspeace account or across many, so the Global Blocklist can warn other Syspeace installations before they’re targeted too.

Syspeace Console is typically installed on an administrator’s own workstation, separate from the protected server — that’s what the trial onboarding describes. There’s no technical requirement forcing that separation, though.

This detail matters when contacting support: always mention whether Service and Console are on the same or different machines, since it affects how an issue is diagnosed.

The Syspeace relay is what Syspeace Console uses to reach every paired Syspeace Service, without needing direct network line-of-sight to the server. Both the protected server and the administrator’s workstation need outbound internet connectivity for this to work.

Exact connection details (ports, protocols) aren’t published publicly here — see Troubleshooting Console-to-Service connectivity if a service isn’t showing up as expected, or contact support.

Your Syspeace version, the Windows Server version, whether Service and Console run on the same or different servers, a description of the issue with the exact error message if any, whether it’s reproducible, recent changes, relevant logs, and the timestamp with timezone. See Collecting information for a support request for the full checklist, and the support page to get in touch.

Syspeace’s Access Log, reports, and blocks are all timestamped. If a server’s or workstation’s clock has drifted, timestamps can look inconsistent even when nothing is actually wrong, which makes an incident harder to correlate. See Checking Windows time synchronization for how to check this, and always include the timezone alongside a timestamp when contacting support.

Syspeace v4 requires Windows Server 2008 R2 or later. Syspeace v3 supports Windows Server 2003 and later, so it remains the option if you’re still running Windows Server 2003 or Windows Server 2008.

See the full version comparison for everything else that differs, and the downloads page for installers.

Both Syspeace Service and Syspeace Console report their own version number. Include the exact version of each when contacting support — see Collecting information for a support request for the full checklist.