Getting started
What krupiq is, what it needs, and how to protect your first endpoints in under an hour.
Updated
krupiq is an anti-ransomware platform for the enterprise. A lightweight agent on every endpoint detects encryption the moment it starts, isolates the affected host in under a second and restores the touched files from immutable copies. The krupiq console gives security teams and executives live status, controls and audit-ready evidence in one place.
This page takes you from nothing to a protected pilot group.
Before you begin
- A krupiq console tenant. It is provisioned during onboarding and reached through your customer portal.
- An enrolment token from the console (Settings → Agents → Enrolment). Tokens are scoped to a site and expire after 30 days.
- Endpoints running Windows 10 or 11, Windows Server 2016 or later, a supported Linux distribution, or macOS 13 or later.
- Outbound HTTPS (TCP 443) from endpoints to your console address. No inbound ports are required.
1. Download the agent
Get the archive for your platform from the download page and verify its SHA-256 checksum against the value shown there. Each archive contains the installer and a short README.
2. Install on a pilot group
Start with ten to fifty endpoints that represent your estate: a few laptops, a file server, a domain controller. Install silently with your enrolment token:
# Windows
msiexec /i krupiq-agent-3.4.0.msi ENROL_TOKEN=<token> /qn
# Linux (Debian/Ubuntu shown; RPM packages behave the same)
sudo KRUPIQ_ENROL_TOKEN=<token> dpkg -i krupiq-agent_3.4.0_amd64.deb
# macOS
sudo installer -pkg krupiq-agent-3.4.0.pkg -target / && sudo krupiqctl enrol --token <token>
The agent needs no reboot. Within a minute the endpoint appears in the console with status Protected.
3. Run a simulation
Open a protected endpoint in the console and choose Run simulation. The agent performs a harmless encryption drill in a sandboxed folder. You should see the attack confirmed, the host isolated, the files rolled back and a one-page incident report generated, all within a few seconds. Release the isolation from the same screen.
4. Roll out
Deploy to the rest of the estate with your software distribution tool (Intune, SCCM, Jamf, Ansible or similar). The deployment guide covers silent installs, proxies, offline endpoints and upgrades.
Next steps
- Architecture: what runs where and what data leaves the endpoint.
- Detection and response: how the three Chimera engines decide and act.
- Compliance and reporting: the evidence the console produces.