nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cato Cloud
- Discussions
- Best Practices
API
- Discussions
- Best Practices
Idea Hub
Community Help
- Discussions
Cato Partners
Cato SWIFTs
Discussions
Categories
Groups
Help

ARM version?

Most of Cato's competitors now have native ARM versions of their VPN clients - but for Cato it's not even on the roadmap? I suppose the X64 version will not run in emulation mode on a Snapdragon based Copilot+ Windows computer?

Find more posts tagged with

Abuse

Comments

michaelsaw

Hi JM,

Currently, ARM support is not explicitly mentioned on the documentation.
Is there certain devices that you would require Cato Client to be supported on?
Do reach out to your assigned Cato Representative to discuss further. I believe a Feature Enhancement (RFE) may be required.

Cheers JM

Hi Michael,

No, I have never even seen one of those devices in real life - I don't have a business case to sway Cato product management one way or the other. But I wouldn't be shocked if suddenly some C-level comes asking us to support his/her new fancy AI laptop.

Cisco, Palo Alto, Ivanti, Fortinet, Check Point (and Microsoft) all have native ARM clients (check out https://windowsonarm.org/?category=4d119d55-783b-4c7d-ae24-8ed6f19c8ba4), so just was a bit surprised to find no mention of it at all in the Cato docs (or, indeed, the roadmap).

ItayPM

Hi JM,
I'm Itay, a product manager at Cato Networks.

Adding support for ARM is indeed on our long-term roadmap, possibly in early 2026.
Once we have more updates on this subject, we'll update the Roadmap page accordingly.

If this matter is important to you, I kindly suggest you reach out to your Cato representative so they may raise an RFE on your behalf.

Best regards, Itay

WPAjack

as a datapoint, we are using some Microsoft Laptops with snapdragon that I was wondering why the Cato Client wasn't being installed by the RMM.

michaelsaw

Hi WPAjack,

Would you share the laptop and snapdragon model to reference?
Alternatively, would you consider Cato Browser Access as a temporary workaround, for the time being?

Cheers

WPAjack

a couple of different Microsoft models

Surface Laptop for Business, Copilot+ PC - 13 Inch, Snapdragon® X Plus (8 Core), Platinum, 16GB RAM, 512GB SSD
Surface Laptop for Business, Copilot+ PC - 13.8 inch, Platinum, Snapdragon® X Plus (10 core), 16GB RAM, 256GB SSD

Surface Laptop for Business, Copilot+ PC - 13.8 inch, Black, Snapdragon® X Elite (12 core), 16GB RAM, 1TB SSD

and one Dell
Dell Latitude 7455, Snapdragon (R) X Plus X1P-64-100 (10 cores up to 3.4 GHz, NPU up to 45 TOPS)

I'm more interested in the pre-login functionality at the moment, to make sure that I always have connectivity to the domain controllers for GPO updates and the such. I have set up a laptop with the cato client set with pre-login functionality, already domain joined to our network, and then send the laptop to the end user for them to sign into the laptop for the first time. with the cato client, it can make that AD connection to the domain controller to set up the user profile on that first login. the Cato Browser Access wouldn't help us in this scenario, as far as I know.

I'm happy to see that client ARM support has now been added to the roadmap

It shouldn't be too much of a challenge though - I have been running a Dell Latitude 7455 (Snapdragon X Elite) as my daily driver for a couple of months, and the Cato x86 client works perfectly well under the Prism emulator. Only exception is auto-upgrade is not working for some reason.

KevinS

Any Update on the ARM-Client? We are facing issues with ressources not available on ARM-Clients with a very random behaviour.

What specific ARM clients are you using? Just a sample of one here, but on my Windows 11 on a Snapdragon X Elite computer I am seeing no such issues.

Einat

Native support for ARM is now available with Windows client v6.0, so easier to use on Snapdragon, Surfacr Pro etc.:

https://support.catonetworks.com/hc/en-us/articles/11276483327389-Summary-of-Cato-Windows-Client-Releases

While it was technically possible to run the client on ARM devices before (via emulation), version 6.0 provides native support for improved efficiency and performance.

The Cato Client for ARM at https://clientdownload.catonetworks.com/cato-client appears to be an older x86 version.

ddaniel

You can download the newer 6.x ARM client from the CMA at Access/ Client Rollout / Download Client (I do not have any ARM devices to test it on, but the clients in the CMS tend to be newer than the public download location)

WPAjack

I saw the same issue as JM.

I downloaded the ARM client based on the update in this thread, I thought I downloaded it through the CMA, not sure. It did install and work on one of my Snapdragon Surface Laptops but did show a 5.21 version which I thought was odd until I looked back on this thread.

downloading it again from the CMA shows a v6 version so I will test that now