IGEL
“The endpoint stops being the part you worry about.”
IGEL OS turns the hardware you already own into a locked-down, centrally managed endpoint for Citrix, Microsoft and any cloud-delivered workspace.
Why IGEL
Distributed work is not a phase anymore. People need to work from anywhere, and the organization still has to be able to manage and secure whatever they are working on.
Icon
Hardware agnostic
A Linux-based operating system for x86 machines, whatever the badge on the front. One managed OS across a fleet that was bought from four different vendors over six years.
Icon
Less capital spend
Hardware stops being the trigger for a refresh. Devices that would have been replaced carry on doing the job, which moves the cost from capital to a license you can forecast.
Icon
Harder to compromise
The operating system is read-only and verified at every boot. There is no local data to steal and very little surface to attack in the first place.
Icon
Easy to shape
Endpoints look and behave the way you want without touching the backend. The change is made centrally and lands on every device that matches the profile.
The architecture
IGEL calls this its Preventative Security Model. The idea is to stop a compromise being possible rather than to detect one after the fact.
Read-only by design
The operating system is locked at the system level, so an unauthorized change cannot run or persist. Integrity is checked at every reboot against a known-good state.
A small surface to attack
IGEL OS 12 carries only what the user needs to do the job. Identity, security and management tooling arrive as separate apps rather than bloating the base image.
A verified chain of trust
Each stage of the boot process cryptographically checks the next, starting from UEFI Secure Boot and the TPM on the hardware itself.
Nothing left on the device
Downloads, screenshots and cached files do not persist locally. A device that goes missing has nothing on it to extract, which shortens the conversation considerably.
One management console
The Universal Management Suite runs the fleet from a single web console, with a REST API underneath for the parts you want to automate.
Apps decoupled from the OS
New tooling is provisioned centrally without rebuilding and reimaging. The operating system and the things running on it stop being one brittle artifact.
What we will not claim
IGEL publishes some striking numbers for attack surface reduction and cost savings, and we are not going to repeat them here as if they were yours. What you save depends on the hardware you already have and how soon you would otherwise have replaced it. That is a calculation we are happy to do with your actual asset register before anyone signs anything.
Where it fits in the stack
IGEL is not a workspace. It is what the user sits in front of to reach one, which is why it matters most to the people already running Citrix or Microsoft at the other end.
Citrix
The endpoint for a Citrix estate
IGEL runs a dedicated program for Citrix environments. For us the value is simpler than the datasheet: the device stops being a variable when something goes wrong, because every endpoint is running the same verified image.
Microsoft
The endpoint for Microsoft workspaces
IGEL OS is built for SaaS, DaaS, VDI and secure browser environments, which covers most of what a Microsoft workspace actually is. It is also the reason a Windows 11 hardware deadline stops being a forced purchase.
Where it fits
IGEL earns its keep where devices are many, shared, mismatched or awkward to reach, and where what sits on the endpoint matters.
Icon
Healthcare
Shared clinical workstations in corridors and bays, used by whoever is on shift. Nothing persists on the device, and a machine in a public area stops being a records risk.
Icon
Credit unions and financial services
Branch and teller endpoints that have to be identical, auditable and quick to replace. A failed device is swapped and reprofiled rather than rebuilt.
Icon
Government and public safety
Shift work on shared terminals, with a locked operating system and a boot chain that can be evidenced when somebody asks how the endpoint is controlled.
Icon
Education
Labs, carts and classroom machines that take a beating and turn over constantly. Older hardware keeps earning its place for another few years.
Icon
Frontline and manufacturing
Shop floor and warehouse terminals in conditions that are hard on equipment, where repurposing what is already installed beats specifying new.
Icon
Shared-shift workplaces
Contact centers and hot-desked offices where the person changes but the desk does not, and the endpoint has to come up clean every time.
Why LKMethod
Deploying IGEL is not difficult. Deciding which devices it should go on, what the profiles look like, and how it behaves when the network is having a bad day is where the work actually is.
We own both ends
An endpoint project that ignores what it connects to fixes half the problem. We architect the delivery platform as well, so logon time and session experience get designed together rather than blamed on each other.
We start with your asset register
Which devices stay, which are genuinely finished, and what the license actually costs against the refresh you were about to fund. That is the first conversation, not the last.
We stay after the rollout
Profiles, firmware, app delivery and the fleet itself, run as a managed service by the people who designed it.
We are an architecture practice before we are a reseller. If your endpoints are fine and the problem is somewhere else in the stack, we would rather find that than sell you a fleet rollout.
Start with the estate you have
Tell us what is deployed, how old it is, and what people connect to. We will come back with what IGEL would change, what it would cost, and which devices we think are genuinely at the end of the road.