<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="https://www.jain.com/assets/img/6adafce5-1.1"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Kasm Technologies &#8211; Jain.com</title>
	<atom:link href="/tag/kasm-technologies/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Data centers, connectivity, and security — news and analysis</description>
	<lastBuildDate>Sat, 29 Aug 2026 10:02:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>/wp-content/uploads/2026/08/jain-com-icon-512-150x150.png</url>
	<title>Kasm Technologies &#8211; Jain.com</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Kasm and Everfox Partner on Cross-Domain Workspace Access for Defense</title>
		<link>/kasm-everfox-cross-domain-workspace-access-partnership/</link>
		
		<dc:creator><![CDATA[Deepak Jain]]></dc:creator>
		<pubDate>Thu, 20 Aug 2026 11:13:25 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[containerization]]></category>
		<category><![CDATA[cross-domain solutions]]></category>
		<category><![CDATA[defense technology]]></category>
		<category><![CDATA[government IT]]></category>
		<category><![CDATA[Kasm Technologies]]></category>
		<category><![CDATA[secure workspace]]></category>
		<category><![CDATA[VDI]]></category>
		<category><![CDATA[zero trust]]></category>
		<guid isPermaLink="false">/kasm-everfox-cross-domain-workspace-access-partnership/</guid>

					<description><![CDATA[Kasm Technologies and Everfox have partnered to deliver secure cross-domain workspace access for government and defense across classification levels. The joint solution pairs containerized, ephemeral desktops with a zero-trust thin client, aiming to replace costly multi-endpoint VDI in classified environments.]]></description>
										<content:encoded><![CDATA[<div class="jain-post-grid">
<div class="jain-post-main">
<p>Kasm Technologies and Everfox announced a strategic technology partnership on August 20, 2026, combining Kasm Workspaces — a container-based platform that streams desktops and applications to users in disposable, policy-controlled sessions — with Everfox&#8217;s Trusted Thin Client, a purpose-built zero-trust endpoint for accessing networks at different security classification levels. The joint solution, available now, targets government, defense, and intelligence agencies that today issue multiple devices or run parallel virtual-desktop stacks to keep classified networks separated.</p>
<h2>Executive Summary</h2>
<p>The announcement pairs two specialized vendors around one problem: giving cleared personnel access to applications and desktops across multiple classification levels from a single device. In classified environments, networks at different levels (for example, unclassified versus secret) are deliberately kept apart, which historically means separate computers, separate virtual desktop infrastructure (VDI) stacks, and the cost and desk clutter that come with them. Everfox contributes the cross-domain access layer — its Trusted Thin Client bridges those separated networks on validated hardware — while Kasm contributes the workspace layer, streaming containerized desktops and applications into ephemeral sessions that are centrally managed and fully wiped when they end, so no data persists on the endpoint.</p>
<p>The companies emphasize that adoption does not require a rip-and-replace: Kasm Workspaces integrates with existing hypervisors, cloud environments, and identity providers, letting agencies layer modern workspace delivery onto current infrastructure and migrate at their own pace. The announcement is a technology partnership with immediate availability, but it names no customers, contract values, or accreditation milestones — it establishes a joint offering, not demonstrated adoption.</p>
<h2>The Economics of Endpoint Sprawl</h2>
<p>The clearest business case in this release is cost consolidation. In many classified settings, working across networks means a physical computer per classification level on each desk, or a separate VDI environment per network — each with its own licensing, patching, and support burden. The release frames the joint solution as a direct replacement for these &#8220;multi-endpoint, multi-VDI-stack approaches,&#8221; collapsing them into one validated device and one workspace platform. If the technology performs as described, the savings show up not just in hardware counts but in operational overhead: fewer stacks to patch, fewer images to maintain, and central policy enforcement instead of per-device configuration.</p>
<p>That said, the release quantifies none of this. There are no cost-comparison figures, seat counts, or reference deployments, so the economic argument rests on the general premise that fewer endpoints and fewer parallel stacks cost less — plausible, but unproven in this document.</p>
<h2>Containers as a Challenger to Legacy VDI</h2>
<p>The more interesting technical bet is architectural. Traditional VDI runs each user a full virtual machine, which is resource-heavy and rigid. Kasm&#8217;s model instead streams desktops and applications from containers — lightweight, fast-starting software packages — into browser-delivered sessions that exist only for the duration of use and are destroyed at termination. In security terms, ephemerality is a feature: a session that is fully wiped leaves no residual data on the endpoint, which matters enormously when the endpoint touches multiple classification levels.</p>
<p>Defense environments, however, are conservative adopters for good reason. Cross-domain solutions face some of the most demanding assurance expectations in government IT, and the release does not address how the combined stack is accredited or evaluated for cross-domain use — only that Everfox&#8217;s hardware is &#8220;validated&#8221; and its solutions are &#8220;purpose-built&#8221; for high-assurance environments. Whether container isolation plus a trusted thin client satisfies each agency&#8217;s specific approval processes is the question that will actually determine adoption, and it is not answered here.</p>
<h2>The No-Rip-and-Replace Pitch</h2>
<p>Both companies clearly understand their buyer. Agencies running classified missions cannot take infrastructure offline for a wholesale migration, so the release leans hard on incrementalism: Kasm integrates with existing hypervisors, clouds, and identity providers, and agencies can &#8220;transition at a pace that does not put critical missions at risk.&#8221; Kasm&#8217;s chief product officer, Daniel Ben-Chitrit, also stresses the absence of vendor lock-in and the platform&#8217;s on-premise deployment model — both sensitive points for government buyers wary of dependency on any single supplier or on commercial cloud availability.</p>
<p>Strategically, the partnership is complementary rather than overlapping: Everfox gets a modern desktop-delivery story to pair with its cross-domain plumbing, and Kasm gets a credentialed route into classified networks it could not plausibly enter alone. The risk cuts the other way too — a technology partnership without disclosed go-to-market commitments, joint contract vehicles, or named integrator support can remain a datasheet exercise. The release states the joint solution is available now, which is a stronger claim than a roadmap announcement, but availability and adoption are different things.</p>
<h2>Background</h2>
<p>Kasm Technologies builds an open-core platform for streaming containerized desktops, browsers, and applications to users through the web browser — a container-based alternative to virtual desktop infrastructure (VDI), the long-standing enterprise approach of hosting each user&#8217;s desktop as a virtual machine in a data center. Everfox operates in the cross-domain solutions market, supplying trusted access and secure data transfer between networks at different classification levels for government, defense, and intelligence customers, where high-assurance requirements have historically favored purpose-built hardware and specialized vendors.</p>
<p>The partnership lands amid a broader government push to modernize classified-environment IT, where the default pattern of one endpoint per network has become an acknowledged cost and usability burden. It also extends a run of alliance announcements from Kasm, which recently shipped Kubernetes support in Workspaces 1.19 and a stealth-networking integration with Dispersive, suggesting a deliberate strategy of pairing its workspace layer with specialized security partners rather than building those capabilities alone.</p>
<p>Source: <a href="https://www.prnewswire.com/news-releases/kasm-technologies-and-everfox-announce-strategic-partnership-to-deliver-secure-cross-domain-workspace-access-for-government-and-defense-302852306.html">Kasm Technologies and Everfox Announce Strategic Partnership to Deliver Secure Cross Domain Workspace Access for Government and Defense</a> — PR Newswire press release, August 20, 2026, announcing the joint containerized cross-domain workspace solution.</p>
</div>
<aside class="jain-rail">
<section class="jain-gaps" aria-label="What the release does not say">
<p class="jain-gaps-kicker">⚠ What They Aren’t Saying</p>
<h2>What the Release Doesn&#8217;t Say</h2>
<ul>
<li><strong>Accreditation and approvals:</strong> The release does not say what security accreditations, evaluations, or agency-specific approvals the combined solution holds or is pursuing — the gating factor for any cross-domain deployment.</li>
<li><strong>Customers and scale:</strong> No agencies, pilot programs, seat counts, or contract vehicles are named, so there is no evidence yet of adoption beyond availability.</li>
<li><strong>Commercial terms:</strong> Nothing on pricing, licensing structure, revenue-sharing between the partners, or which company leads sales and support.</li>
<li><strong>Technical boundaries:</strong> The release does not detail how many classification levels a single device supports, performance characteristics, or how the integration handles bandwidth-constrained or disconnected environments.</li>
<li><strong>Competitive context:</strong> The incumbents being displaced — the specific multi-VDI and multi-endpoint vendors — go unnamed, as does any comparison of switching costs.</li>
</ul>
</section>
<section class="jain-faq">
<h2>Frequently Asked Questions</h2>
<h3>What did Kasm Technologies and Everfox announce?</h3>
<p>A strategic technology partnership, announced August 20, 2026, that combines Kasm&#8217;s containerized workspace platform with Everfox&#8217;s Trusted Thin Client so government, defense, and intelligence users can access desktops and applications across multiple classification levels from a single device.</p>
<h3>What is a cross-domain solution?</h3>
<p>Technology that lets users or data move between networks operating at different security classification levels — for example, between unclassified and secret networks — while enforcing strict controls that keep the domains separated. Everfox specializes in this category for classified environments.</p>
<h3>What is Kasm Workspaces?</h3>
<p>A platform that streams browsers, desktops, and applications to users through ephemeral, policy-controlled container sessions delivered in a web browser. Sessions are centrally managed and destroyed at termination, positioning it as a lighter-weight alternative to traditional virtual desktop infrastructure.</p>
<h3>What is Everfox&#x27;s Trusted Thin Client?</h3>
<p>A purpose-built zero-trust endpoint that provides secure cross-domain access on validated hardware. It lets one physical device bridge networks at different classification levels, replacing the practice of issuing a separate computer per network.</p>
<h3>What problem does the joint solution target?</h3>
<p>Endpoint sprawl and duplicated infrastructure in classified environments, where agencies traditionally run separate devices and separate VDI stacks per classification level. The partners say their combined stack replaces those multi-endpoint, multi-VDI approaches with one device and one workspace platform.</p>
<h3>Is the joint Kasm-Everfox solution available now?</h3>
<p>Yes. The release states the joint solution is available immediately, with information at kasm.com&#8217;s Everfox alliance page and through Everfox directly. No customers or deployments were named at announcement.</p>
<h3>Do agencies have to replace existing infrastructure to adopt it?</h3>
<p>The companies say no. Kasm Workspaces integrates with existing hypervisors, cloud environments, and identity providers, and the release emphasizes that agencies can layer the solution onto current infrastructure and transition gradually rather than performing a rip-and-replace migration.</p>
<h3>What happens to data on the endpoint after a session ends?</h3>
<p>According to the release, sessions are fully wiped at termination with no local data persistence, regardless of classification level. This ephemerality is central to the security argument: nothing sensitive should remain on the device between sessions.</p>
<h3>How is this different from traditional VDI?</h3>
<p>Traditional VDI gives each user a persistent full virtual machine, which is resource-intensive and rigid. Kasm&#8217;s container-native model spins up disposable sessions on demand and streams them to a browser, which the company argues reduces the cost, rigidity, and risk of legacy VDI.</p>
<h3>What security accreditations does the joint solution hold?</h3>
<p>The release does not say. It describes Everfox&#8217;s hardware as validated and its solutions as purpose-built for high-assurance environments, but names no specific certifications, evaluations, or agency approvals — a material omission, since accreditation typically gates cross-domain deployments.</p>
<h3>Who are the intended customers?</h3>
<p>Government, defense, and intelligence agencies operating across multiple classification levels — organizations that need personnel to work on several separated networks and currently absorb the cost of parallel endpoints and desktop infrastructure to do so.</p>
<h3>Does the announcement include financial terms or contract commitments?</h3>
<p>No. The release discloses no pricing, revenue arrangements between the partners, contract vehicles, or customer commitments. It is a technology partnership announcement with a joint offering, not a reported sale or program win.</p>
<h3>What does &#x27;zero trust&#x27; mean in this context?</h3>
<p>Zero trust is a security model that assumes no device, user, or network segment is inherently trustworthy, so every access request is verified and constrained by policy. Everfox applies the term to its endpoint, and Kasm&#8217;s sessions are policy-enforced and centrally managed in the same spirit.</p>
<h3>What else has Kasm Technologies announced recently?</h3>
<p>Per the same wire source, Kasm recently released Workspaces 1.19 with Kubernetes general availability, zero-trust access, and enterprise diagnostics, and announced a stealth-networking workspace registry with Dispersive — signaling a pattern of partnership-driven expansion into secure networking niches.</p>
<h3>What are the main open questions about this partnership?</h3>
<p>Whether the combined stack achieves the accreditations individual agencies require, whether any customers adopt it at scale, how it is priced against incumbent multi-VDI approaches, and how many classification levels a single endpoint can practically serve. The release answers none of these.</p>
<h3>Why does vendor lock-in matter to government buyers here?</h3>
<p>Agencies making decade-scale infrastructure commitments want to avoid dependency on one supplier&#8217;s stack. Kasm&#8217;s product chief highlights on-premise deployment and freedom from lock-in, a positioning aimed at buyers wary of proprietary VDI ecosystems and mandatory cloud dependencies.</p>
</section>
</aside>
</div>
<p><script type="application/ld+json">{"@context": "https://schema.org", "@graph": [{"@type": "NewsArticle", "headline": "Kasm and Everfox Partner on Cross-Domain Workspace Access for Defense", "description": "Kasm Technologies and Everfox have partnered to deliver secure cross-domain workspace access for government and defense across classification levels. The joint solution pairs containerized, ephemeral desktops with a zero-trust thin client, aiming to replace costly multi-endpoint VDI in classified environments.", "image": ["/wp-content/uploads/2026/08/kasm-everfox-cross-domain-workspace-access.png"], "author": {"@type": "Organization", "name": "jain.com Editorial"}, "datePublished": "2026-08-20T11:13:17.019766+00:00"}, {"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What did Kasm Technologies and Everfox announce?", "acceptedAnswer": {"@type": "Answer", "text": "A strategic technology partnership, announced August 20, 2026, that combines Kasm's containerized workspace platform with Everfox's Trusted Thin Client so government, defense, and intelligence users can access desktops and applications across multiple classification levels from a single device."}}, {"@type": "Question", "name": "What is a cross-domain solution?", "acceptedAnswer": {"@type": "Answer", "text": "Technology that lets users or data move between networks operating at different security classification levels \u2014 for example, between unclassified and secret networks \u2014 while enforcing strict controls that keep the domains separated. Everfox specializes in this category for classified environments."}}, {"@type": "Question", "name": "What is Kasm Workspaces?", "acceptedAnswer": {"@type": "Answer", "text": "A platform that streams browsers, desktops, and applications to users through ephemeral, policy-controlled container sessions delivered in a web browser. Sessions are centrally managed and destroyed at termination, positioning it as a lighter-weight alternative to traditional virtual desktop infrastructure."}}, {"@type": "Question", "name": "What is Everfox's Trusted Thin Client?", "acceptedAnswer": {"@type": "Answer", "text": "A purpose-built zero-trust endpoint that provides secure cross-domain access on validated hardware. It lets one physical device bridge networks at different classification levels, replacing the practice of issuing a separate computer per network."}}, {"@type": "Question", "name": "What problem does the joint solution target?", "acceptedAnswer": {"@type": "Answer", "text": "Endpoint sprawl and duplicated infrastructure in classified environments, where agencies traditionally run separate devices and separate VDI stacks per classification level. The partners say their combined stack replaces those multi-endpoint, multi-VDI approaches with one device and one workspace platform."}}, {"@type": "Question", "name": "Is the joint Kasm-Everfox solution available now?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The release states the joint solution is available immediately, with information at kasm.com's Everfox alliance page and through Everfox directly. No customers or deployments were named at announcement."}}, {"@type": "Question", "name": "Do agencies have to replace existing infrastructure to adopt it?", "acceptedAnswer": {"@type": "Answer", "text": "The companies say no. Kasm Workspaces integrates with existing hypervisors, cloud environments, and identity providers, and the release emphasizes that agencies can layer the solution onto current infrastructure and transition gradually rather than performing a rip-and-replace migration."}}, {"@type": "Question", "name": "What happens to data on the endpoint after a session ends?", "acceptedAnswer": {"@type": "Answer", "text": "According to the release, sessions are fully wiped at termination with no local data persistence, regardless of classification level. This ephemerality is central to the security argument: nothing sensitive should remain on the device between sessions."}}, {"@type": "Question", "name": "How is this different from traditional VDI?", "acceptedAnswer": {"@type": "Answer", "text": "Traditional VDI gives each user a persistent full virtual machine, which is resource-intensive and rigid. Kasm's container-native model spins up disposable sessions on demand and streams them to a browser, which the company argues reduces the cost, rigidity, and risk of legacy VDI."}}, {"@type": "Question", "name": "What security accreditations does the joint solution hold?", "acceptedAnswer": {"@type": "Answer", "text": "The release does not say. It describes Everfox's hardware as validated and its solutions as purpose-built for high-assurance environments, but names no specific certifications, evaluations, or agency approvals \u2014 a material omission, since accreditation typically gates cross-domain deployments."}}, {"@type": "Question", "name": "Who are the intended customers?", "acceptedAnswer": {"@type": "Answer", "text": "Government, defense, and intelligence agencies operating across multiple classification levels \u2014 organizations that need personnel to work on several separated networks and currently absorb the cost of parallel endpoints and desktop infrastructure to do so."}}, {"@type": "Question", "name": "Does the announcement include financial terms or contract commitments?", "acceptedAnswer": {"@type": "Answer", "text": "No. The release discloses no pricing, revenue arrangements between the partners, contract vehicles, or customer commitments. It is a technology partnership announcement with a joint offering, not a reported sale or program win."}}, {"@type": "Question", "name": "What does 'zero trust' mean in this context?", "acceptedAnswer": {"@type": "Answer", "text": "Zero trust is a security model that assumes no device, user, or network segment is inherently trustworthy, so every access request is verified and constrained by policy. Everfox applies the term to its endpoint, and Kasm's sessions are policy-enforced and centrally managed in the same spirit."}}, {"@type": "Question", "name": "What else has Kasm Technologies announced recently?", "acceptedAnswer": {"@type": "Answer", "text": "Per the same wire source, Kasm recently released Workspaces 1.19 with Kubernetes general availability, zero-trust access, and enterprise diagnostics, and announced a stealth-networking workspace registry with Dispersive \u2014 signaling a pattern of partnership-driven expansion into secure networking niches."}}, {"@type": "Question", "name": "What are the main open questions about this partnership?", "acceptedAnswer": {"@type": "Answer", "text": "Whether the combined stack achieves the accreditations individual agencies require, whether any customers adopt it at scale, how it is priced against incumbent multi-VDI approaches, and how many classification levels a single endpoint can practically serve. The release answers none of these."}}, {"@type": "Question", "name": "Why does vendor lock-in matter to government buyers here?", "acceptedAnswer": {"@type": "Answer", "text": "Agencies making decade-scale infrastructure commitments want to avoid dependency on one supplier's stack. Kasm's product chief highlights on-premise deployment and freedom from lock-in, a positioning aimed at buyers wary of proprietary VDI ecosystems and mandatory cloud dependencies."}}]}]}</script></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
