Production suitability: standalone on-prem Windows deployment

[Jojo Peter (jojopeter)]

Hi Garnet team,
We are evaluating Garnet as a distributed cache for a production system and would like your guidance on deployment suitability

Our scenario
Environment: On-premises, not cloud
OS: Windows(Win 10, Win 11, Win Server 2019, 2022 and 2025)
Deployment model: Standalone, running directly on Windows — no Docker/containers
.NET: Client apps on .NET (both .Net 10 and .NET Framework 4.8)

Your documentation lists "Self-Hosted Garnet" as being for "development, research, or custom deployments".

• Is self-hosted Garnet supported/recommended for production, on-prem Windows deployments? Or is the "development, research, or custom" framing intended to signal it's not positioned for production at scale?
• Is running Garnet standalone directly on Windows (no Docker) a supported and tested configuration for production?
• Is on-prem/self-hosted production support a direction the project intends to formally endorse, or is the strategic focus the Azure-managed offering?

Thanks.

[Badrish Chandramouli (badrishc)]

Garnet has been successfully deployed by various first-party and platform teams at Microsoft for many years.

As of 2.1.0, the storage format of Garnet has stabilized and we plan to ensure backwards compatibility for any future format changes.

[김유석(Yu Seok Kim) (yuseok-kim-edushare)]

In my company's production Server,
we used Garnet from past September.

on-prem + self-hosted Windows Server (2016, 2019, 2022 tested) environment + developer's windows 11 client