Project Solara: Microsoft’s Agent-First Chip-to-Cloud Platform (Not a Windows Variant)

ChatGPT · 2026-06-03T04:23:30-0400

Microsoft unveiled Project Solara at Build 2026 in San Francisco on June 2, presenting it as an early chip-to-cloud platform for enterprise-oriented “agent-first” devices that use AI agents, adaptive interfaces, Microsoft identity and management services, and partner silicon rather than conventional app-centric Windows PCs.
That is the plain product news. The more interesting story is that Microsoft is no longer treating agents as a feature bolted onto Windows, Office, or Azure; it is sketching a computing model in which the agent becomes the interface and the device becomes a managed endpoint for intent. Solara is early, concept-heavy, and full of unresolved questions, but it is also one of Microsoft’s clearest signals yet that the company thinks the next platform war may not be fought over apps at all.

Microsoft Puts the Agent Before the App

For most of the PC era, Microsoft’s power came from controlling the environment where applications lived. Windows was the platform, Win32 was the moat, Office was the proof of gravity, and the desktop metaphor trained generations of users to think in files, windows, menus, and programs. Even when phones and tablets weakened that model, Microsoft still largely described productivity in terms of applications that could be modernized, synced, cloud-connected, or infused with Copilot.
Project Solara cuts at that history in a subtle but important way. Microsoft is not saying that apps disappear tomorrow, or that Windows becomes irrelevant, or that every worker will soon speak to a plastic puck on a counter. It is saying that there are categories of work where launching an app may be the wrong abstraction, and where a device built around a specialized agent could be more useful than another screen running another grid of icons.
That is a significant shift because it moves the software frontier away from “which app do I open?” and toward “which outcome am I trying to produce?” In Microsoft’s framing, agents become both a programming unit and an interaction unit. They are not merely chatbots sitting beside traditional workflows; they are expected to coordinate across services, remember context, delegate subtasks, and present an interface only when one is needed.
The company’s language around Solara is deliberately expansive. It imagines devices that are small or large, fixed or mobile, personal or professional, and tuned for retail, healthcare, hospitality, industrial work, field service, legal, finance, and enterprise productivity. This is not the pitch for a single gadget. It is the pitch for a substrate.

The Android Base Is the Quietest Rebuke to Windows

The most revealing technical detail is not the phrase agent-first. It is that Project Solara’s device-side foundation is Microsoft Device Ecosystem Platform, an enterprise-grade operating system built on AOSP, the Android Open Source Project. Microsoft cannot simply call it Android in the consumer sense, and Solara is not a Google-certified Android product line. But the choice of an Android-derived base is impossible to ignore.
For Windows watchers, this lands with a thud and a shrug at the same time. A thud, because Microsoft is proposing a new class of managed, intelligent business devices without centering Windows as the device OS. A shrug, because Microsoft has spent more than a decade learning that specialized hardware categories often need power efficiency, mobile silicon support, sensor integration, and OEM flexibility more than they need desktop compatibility.
This is the pragmatic Microsoft of 2026, not the Windows-or-nothing Microsoft of 2006. If the job is to build portable, wearable, stationary, or ultra-mobile agent appliances, AOSP gives Microsoft a mature hardware compatibility story and a large pool of embedded-device know-how. Windows brings enormous value to PCs, workstations, and cloud-connected productivity, but it is not automatically the right answer for a smart badge, a counter display, or a task-specific field device.
That does not make Solara anti-Windows. It makes it post-monoculture. Microsoft’s platform strategy increasingly looks like a stack of identity, management, security, cloud services, agents, and developer tools that can sit across Windows, Android-derived systems, browsers, and edge hardware. The operating system still matters, but the point of control migrates upward.

Enterprise Control Is the Price of Admission

Microsoft’s Solara pitch is aimed squarely at enterprise buyers, and that is not an accident. Consumer AI gadgets have already demonstrated how quickly “ambient assistant” turns into “untrusted recorder” when privacy, identity, and data boundaries are vague. In a workplace, the tolerance for ambiguity is even lower.
So Microsoft is front-loading the parts that CIOs and security teams want to hear: Intune management, Entra ID sign-in, Windows Hello for Business authentication, enterprise policies, privacy controls, and clear indicators when devices are listening or recording. The company says Solara devices should be manageable like PCs and mobile devices are today. That phrase is doing a lot of work.
It means Microsoft knows the dream of agent-first hardware will die in procurement if these devices look like unmanaged IoT curiosities. A retailer cannot scatter AI-enabled displays across stores unless it can enroll them, patch them, audit them, lock them down, and retire them. A healthcare organization cannot trial bedside or hallway assistants unless it can reason about access controls, data handling, and physical privacy. A field-service company cannot hand workers an agentic device that becomes another shadow IT endpoint.
The challenge is that enterprise manageability is easier to promise than to perfect. Agents complicate the old device-management model because they do not merely display data; they act on it. A compromised laptop is bad. A compromised agent endpoint that can retrieve customer records, open tickets, summarize internal documents, and initiate actions across systems is a different category of risk.

Just-in-Time UI Is the Most Ambitious and Most Fragile Idea

Solara’s most intriguing software concept is Microsoft’s notion of just-in-time UI. The idea is that an agent-first device should not require every developer to handcraft a full application interface for every screen size, input method, or form factor. Instead, the agent can adapt the presentation to the context: voice when voice is natural, touch when touch is useful, visuals when visuals clarify, and a generated or semi-generated layout when the task demands it.
This is both obvious and radical. It is obvious because responsive design has been straining for years under the weight of too many screens, too many workflows, and too many device categories. It is radical because Microsoft is suggesting that the interface itself becomes more fluid, more contextual, and less manually authored.
The company is careful not to claim that fully generative UI is ready to replace structured design. In fact, its own framing places Solara somewhere between traditional responsive layouts and a future where AI can generate interfaces frame by frame. That restraint matters. It suggests Microsoft understands that business users do not merely need a clever interface; they need a predictable one.
Predictability is the hard part. A dynamically adapted interface can reduce development cost, but it can also confuse training, documentation, accessibility testing, compliance reviews, and support. If the same agent presents different flows on a smart display, a badge-like wearable, and a desk device, IT departments will ask how those experiences are validated. If the interface changes because the model infers context, auditors will ask what governed that inference.
The promise is a world where specialized devices no longer require specialized app ecosystems. The risk is a world where every interface becomes a negotiation among model behavior, developer intent, device constraints, and enterprise policy. That may be manageable, but it is not magic.

The Hardware Concepts Are a Map, Not a Product Line

Microsoft has shown concept reference devices for Solara, including stationary and portable directions developed with silicon partners. Qualcomm is tied to a portable-device concept, while MediaTek is associated with a stationary device concept. These are not launch products, and Microsoft is right to describe them as exploratory.
That distinction matters because the history of AI hardware is already littered with overpromised objects. Voice assistants became kitchen timers with cloud dependencies. Smart displays often became photo frames with subscriptions. Recent AI-first gadgets have struggled when they tried to replace the phone without matching its utility, battery life, app ecosystem, or user trust.
Solara’s enterprise focus gives Microsoft a better opening. A device does not need to replace a smartphone if it lives at a checkout counter, a clinic station, a warehouse aisle, or a hotel front desk. It only needs to solve a specific workflow better than the combination of a PC, a tablet, a shared login, and a stressed employee.
That is where reference designs make sense. Microsoft is not trying to sell the world a single “AI device.” It is trying to make it cheaper for partners to build many constrained devices around known security, identity, agent, and hardware patterns. If successful, Solara could become less like Surface and more like an ecosystem recipe.
Still, hardware has a way of humbling platform visions. Battery life, thermals, microphones, cameras, screens, sensors, durability, repairability, supply chain cost, and deployment logistics will determine whether these devices are useful in the real world. An elegant agent architecture cannot save a badge that dies mid-shift or a display that cannot survive a retail floor.

The Pilot List Shows Where Microsoft Thinks Agents Can Earn Their Keep

Microsoft’s early pilot roster reportedly includes AccuWeather, Best Buy, CVS Health, Levi’s, Target, and others. That list is more revealing than a generic promise of “enterprise adoption,” because it points to environments where frontline workflows, customer interaction, and operational knowledge intersect.
Retail is the obvious proving ground. Store associates constantly move between inventory lookup, customer questions, returns, product guidance, promotions, staffing issues, and internal policies. A properly constrained agent endpoint could help workers retrieve information without abandoning the customer or logging into a shared terminal. A poorly constrained one could hallucinate product availability, mishandle customer data, or become another device nobody remembers to charge.
Healthcare is more delicate. CVS Health’s presence on the pilot list suggests interest in workflows where information retrieval and guided interaction could matter, but healthcare environments carry higher privacy, regulatory, and safety expectations. An agentic device in that setting must be useful without becoming an unreliable clinical intermediary. The difference between administrative assistance and medical advice must be bright enough for users, patients, and compliance teams to see.
AccuWeather hints at a different class of use case: domain-specific agents tied to real-time data and decision support. Weather is operational infrastructure for logistics, events, travel, insurance, public safety, and field work. A Solara device could make sense where an agent needs to surface changing conditions, explain risk, and support action in a particular physical environment.
Best Buy and Target also suggest that Microsoft wants partners who understand device deployment at scale. These are not boutique lab environments. They are messy, distributed, staff-intensive operations where the gap between demo and daily use becomes visible quickly.

The Agent Dispatcher Is Where the Platform War Begins

Microsoft says there will not be a single dominant agent. That is probably correct, and it is also convenient. A world of many specialized agents creates exactly the kind of coordination problem that a platform company wants to solve.
Solara’s extensibility story is about letting organizations bring their own agents, while Microsoft works on technologies such as an agent dispatcher and an agent task manager to coordinate which agent should handle which work. That sounds plumbing-like, but it may be the most strategically important layer in the whole project. Whoever controls agent routing controls user attention, workflow priority, data access, and the practical definition of competence.
The old app launcher was neutral only in the most superficial sense. App placement, default file associations, notifications, search ranking, and integration privileges all shaped behavior. An agent dispatcher could be even more consequential because users may not know which agent did what, or why one agent was chosen over another.
For enterprises, that creates an attractive possibility: policy-driven orchestration across approved agents, with audit trails and permissions. For developers, it creates a familiar anxiety: will their agent be discoverable, callable, and trusted inside Microsoft’s ecosystem, or will Microsoft’s own agents enjoy the best seats in the house?
This is where Solara intersects with the broader Copilot economy. Microsoft has spent years embedding Copilot across Windows, Microsoft 365, GitHub, security products, and Azure. Solara appears to widen that ambition from software surfaces to physical endpoints. The agent is no longer just in the sidebar; it may be the device.

Windows Is Not Being Replaced, but Its Center of Gravity Is Moving

Every Microsoft platform announcement eventually turns into a referendum on Windows. Solara deserves a more precise reading. It is not a Windows replacement, because it is not aimed at the same general-purpose PC workloads. It is also not irrelevant to Windows, because it signals where Microsoft believes value is moving.
The PC remains the best machine for complex creation, administration, development, analysis, gaming, and legacy compatibility. Windows remains the place where Microsoft can put Copilot in front of hundreds of millions of users. But Solara suggests Microsoft sees a growing class of endpoints where the PC is too much machine and the phone is the wrong machine.
That matters for Windows enthusiasts because the same agent model will likely feed back into Windows itself. If Microsoft learns how to manage agent identity, just-in-time UI, multimodal interaction, and delegated tasks on Solara devices, those lessons will not stay confined to AOSP-based endpoints. They will inform Windows, Microsoft 365, Edge, Teams, and Azure.
The more interesting question is whether Windows becomes the flagship agent environment or one node in a broader agent fabric. Microsoft would probably argue it can be both. But historically, when a company’s strategic layer moves upward, the OS becomes less of a kingdom and more of a territory.
For sysadmins, that means the Windows estate may be joined by a new class of Microsoft-managed, non-Windows agent devices. These endpoints may appear in Intune, authenticate through Entra ID, and touch the same corporate data as PCs, but they will behave differently and require different assumptions. The management plane may look familiar. The risk model will not.

The Security Model Has to Govern Action, Not Just Access

The strongest version of Project Solara is not an AI kiosk. It is a governed action endpoint: a device that knows who is present, what agents are allowed, what data may be accessed, what actions require confirmation, and what telemetry must be retained. That is a much harder problem than building a voice interface.
Traditional endpoint security focuses on identity, device health, network access, application control, data loss prevention, and patching. Agent-first devices add intent interpretation and task execution to the mix. The system must decide not only whether a user can access a service, but whether a requested action is appropriate, authorized, reversible, and accurately understood.
Consider a retail associate asking an agent to “fix this return,” a nurse asking for “the latest patient note,” or a field technician asking to “order the part and close the job.” Each request may involve multiple systems, sensitive data, and business rules. The agent must know when to act, when to ask, when to refuse, and when to escalate.
That makes auditability central. Enterprises will need logs that explain what the user asked, what the agent interpreted, which systems were touched, what data was retrieved, what action was taken, and whether a human approved it. A transcript alone will not be enough. A black-box model summary will not be enough either.
Microsoft’s advantage is that it already owns much of the enterprise governance stack. Its burden is that customers will expect Solara to inherit that seriousness from day one. In consumer AI, delight can paper over rough edges. In enterprise AI, rough edges become tickets, incidents, and legal reviews.

Developers Get a New Surface and a New Dependency

For developers, Solara dangles a tempting proposition: build an agent once and let it surface across many devices, modalities, and contexts. If just-in-time UI works well enough, the same underlying agent could support a desk display, a handheld device, a wearable, and a wall-mounted assistant without requiring a separate full application for each one.
That could lower the barrier to specialized enterprise software. Many internal tools never become elegant apps because the target user base is small, the workflow is narrow, and the development cost is hard to justify. Agents may change that math by making the conversational and procedural layer more reusable.
But developers should also notice the dependency being created. If Solara’s agent shell, dispatcher, UI adaptation, identity layer, and management policies mediate the user experience, developers are not merely shipping software to a device. They are participating in Microsoft’s orchestration environment. That can be powerful, but it can also be constraining.
The old app-platform bargain was familiar: accept the SDK, follow the design language, obey the store or deployment rules, and gain reach. The agent-platform bargain is less settled. Developers will need to understand how agents are registered, invoked, ranked, permissioned, tested, monitored, and updated. They will need to know how much control they have over interface generation and how much the platform reserves for itself.
The most successful Solara developers may not be those who build the flashiest assistants. They may be the ones who understand enterprise workflows deeply enough to constrain agents into reliable, auditable tools. In the agent era, boring may be a feature.

The Demo Is Easy; the Shift Work Is Hard

Project Solara’s real test will not be whether Microsoft can produce a compelling Build demo. It will be whether the devices remain useful at 3:17 p.m. on a busy retail floor, during a shift change, with background noise, partial connectivity, an impatient customer, and an employee who has no interest in debugging the future of computing.
That is where many AI visions become ordinary IT problems. Speech recognition struggles with accents and noise. Cameras and microphones raise consent issues. Connectivity fails in corners of buildings. Shared devices create authentication friction. Employees find workarounds. Managers demand metrics. Security teams ask for logs. Finance asks whether the device saved enough time to justify its purchase.
Solara’s enterprise-first posture gives Microsoft a fighting chance because it starts from the premise that deployment is part of the product. The inclusion of Intune, Entra ID, Hello for Business, and physical privacy controls is not decorative. It is the minimum required to make an agent device plausible in a managed environment.
Even so, Microsoft will need to prove that agents improve workflows rather than simply changing the shape of friction. If a worker has to repeat a request three times, confirm every action manually, and then check the result in a traditional system, the agent has not replaced the app. It has become a slower front end.
The winning use cases will likely be narrow at first. They will involve constrained data, repeated tasks, clear escalation paths, and measurable time savings. That may sound less glamorous than “the next computer,” but it is how new enterprise platforms become real.

The Solara Bet Comes Down to Trust at the Edge

Solara is Microsoft’s bet that agentic computing needs dedicated places to live. Not every agent belongs in a browser tab, a Teams chat, or a Windows sidebar. Some belong where work physically happens, embedded in the environment, tied to identity and policy, and ready to act within boundaries.
That is a compelling idea because the app-centric model has obvious limits in frontline and operational settings. Many workers do not sit in front of a PC all day. Many tasks do not justify a full application session. Many workflows cross too many systems for a single app to feel natural. If agents can reduce that complexity, they could make computing less like navigation and more like collaboration.
But the word trust will decide whether Solara becomes a platform or a curiosity. Users must trust the device not to spy on them. Workers must trust the agent not to embarrass them in front of customers. Developers must trust the platform not to bury their agents. Administrators must trust the management model. Executives must trust the economics.
Microsoft has been here before in different forms. It has chased new device categories, new interaction models, new runtime abstractions, and new ecosystem plays. Some became foundational; others became footnotes. Solara’s difference is that it arrives when AI has given the industry a plausible new interface, while enterprise customers are still trying to separate useful automation from expensive theater.

The Practical Reading for WindowsForum Readers

For Windows users and administrators, the correct response is neither panic nor hype. Solara is early, but it is a useful marker of Microsoft’s direction: agents are becoming infrastructure, and Microsoft wants its identity, management, cloud, and developer platforms wrapped around them before rivals define the rules.

Project Solara is an early platform effort, not a finished consumer product line, and its first wave is aimed at enterprise pilots rather than home users.
Microsoft is using an AOSP-based device foundation through Microsoft Device Ecosystem Platform, which suggests specialized agent hardware may sit outside Windows while still relying on Microsoft services.
The platform’s enterprise pitch depends on Intune, Entra ID, Windows Hello for Business, privacy controls, and policy enforcement becoming credible safeguards for agentic endpoints.
The most important software idea is just-in-time UI, which could reduce the cost of supporting new device types but will need strong rules for consistency, accessibility, and auditability.
Early pilots with companies such as Best Buy, CVS Health, Levi’s, Target, and AccuWeather point toward frontline, retail, healthcare, and operational workflows where dedicated agent devices may make more sense than another PC or tablet.
The biggest unresolved issue is not whether Microsoft can build an agent device, but whether enterprises can safely govern agents that retrieve data, interpret intent, and take action across business systems.

Project Solara should be read as a thesis about where Microsoft thinks computing is going: away from the app as the default unit of work and toward agents as managed, policy-bound intermediaries between people, data, and action. The hardware may change, the reference designs may never ship in their current form, and the early pilots may expose more friction than magic. But if Microsoft can make agent-first devices trustworthy, manageable, and genuinely useful in the places where work happens, Solara may become less a side project than a preview of the post-app edge.

References

Primary source: thewincentral.com
Published: 2026-06-03T06:20:33.263425

Microsoft Project Solara Unveiled at Build 2026 - WinCentral

Microsoft reveals Project Solara, a new platform for AI-powered agent-first devices, at Build 2026. - Read in on WinCentral

thewincentral.com
Official source: commandline.microsoft.com

Composing a new platform for agent-first devices - Command Line

New interaction technology enables new types of computers. Learn more about Microsoft’s Project Solara.

commandline.microsoft.com
Related coverage: business-standard.com

https://www.business-standard.com/technology/tech-news/microsoft-bets-on-ai-agents-not-apps-and-dynamic-ui-with-project-solara-126060300327_1.html
Related coverage: thurrott.com

Build 2026: Microsoft Project Solara Envisions a Future of Agent-First Devices

During the Build 2026 keynote, Microsoft technical fellow Stevie Bathiche introduced Project Solara, a new software platform for agent-first hardware.

www.thurrott.com
Related coverage: gigazine.net

Microsoft has announced 'Project Solara,' a new platform for AI agent-dedicated devices, creating an agent-centric system using an Android-based OS rather than Windows.

At its developer event, ' Microsoft Build 2026, ' held in San Francisco, USA on June 2, 2026, Microsoft announced ' Project Solara, ' a new device platform that operates primarily with AI agents. Microsoft positions Project Solara not merely as an OS, but as a 'chip-to-cloud' platform spanning...

gigazine.net
Related coverage: thenextweb.com

Microsoft unveils Project Solara: an OS for agent-first devices

Microsoft's Project Solara is a new platform for devices that run AI agents instead of apps. Two concept designs, a badge and desk device, are piloting with Best Buy, CVS, Levi's, and Target.

thenextweb.com

Related coverage: techtimes.com

Microsoft Unveils Project Solara: AI Agents to Replace Platforms, OS via Chip-to-Cloud Tech

Microsoft’s massive plans for AI agents have been unveiled during Build 2026, including the new Project Solara.

www.techtimes.com
Related coverage: arstechnica.com

Microsoft's Project Solara is an Android OS designed for agents instead of apps

Microsoft missed the boat on apps, so get ready for agents.

arstechnica.com
Official source: news.microsoft.com

Microsoft Build en directo

El lugar donde seguir en tiempo real las últimas noticias a medida que se anuncien desde el Microsoft Build, los días 2 y 3 de junio de 2026.

news.microsoft.com
Related coverage: stuff.tv

Microsoft shows off Project Solara smart badge and smart display concepts as AI-first hardware | Stuff

Microsoft is building an AI agent-first platform called Project Solara, and is showing off some interesting hardware designs.

www.stuff.tv
Related coverage: techbuzz.ai

https://www.techbuzz.ai/articles/microsoft-unveils-project-solara-os-for-ai-agent-gadgets
Official source: techcommunity.microsoft.com

https://techcommunity.microsoft.com/t5/s/gxcuf89792/attachments/gxcuf89792/SPBlog/8498/1/Omdia-WP-Microsoft-AI-in-SharePoint-Mar-2026.pdf
Official source: download.microsoft.com

https://download.microsoft.com/download/2/4/A/24A36661-A629-4CE6-A615-6B2910A1367A/Integrated%20Development%20Environment%20Build%20Process.pdf
Official source: local.microsoft.com

https://local.microsoft.com/wp-content/uploads/2024/05/Microsoft-datacenters-in-New-Zealand.pdf
Official source: cdn-dynmedia-1.microsoft.com

https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/bade/documents/products-and-services/en-us/education/Modern-Work-Plan-Comparison-Enterprise-5-1-2026.pdf

Navigation section

Project Solara: Microsoft’s Agent-First Chip-to-Cloud Platform (Not a Windows Variant)

The Ghost of Windows Phone Still Haunts the Room​

AOSP Is the Pragmatic Choice Microsoft Once Would Have Resisted​

The Agent Shell Is the New Start Menu​

The Concept Hardware Tells Us What Microsoft Is Really Testing​

Windows Is Not Being Replaced, but It Is Being Repositioned​

The App Gap Becomes an Accountability Gap​

Microsoft Is Chasing the Post-Smartphone Opening Everyone Else Can See​

The Developer Story Is Still the Missing Middle​

Security Will Decide Whether Solara Is a Platform or a Pilot​

Windows Users Should Watch the Boundary, Not the Branding​

The Solara Bet Comes Down to Five Hard Realities​

References​

AI

Microsoft Puts the Agent Before the App​

The Android Base Is the Quietest Rebuke to Windows​

Enterprise Control Is the Price of Admission​

Just-in-Time UI Is the Most Ambitious and Most Fragile Idea​

The Hardware Concepts Are a Map, Not a Product Line​

The Pilot List Shows Where Microsoft Thinks Agents Can Earn Their Keep​

The Agent Dispatcher Is Where the Platform War Begins​

Windows Is Not Being Replaced, but Its Center of Gravity Is Moving​

The Security Model Has to Govern Action, Not Just Access​

Developers Get a New Surface and a New Dependency​

The Demo Is Easy; the Shift Work Is Hard​

The Solara Bet Comes Down to Trust at the Edge​

The Practical Reading for WindowsForum Readers​

References​

Similar threads

The Ghost of Windows Phone Still Haunts the Room

AOSP Is the Pragmatic Choice Microsoft Once Would Have Resisted

The Agent Shell Is the New Start Menu

The Concept Hardware Tells Us What Microsoft Is Really Testing

Windows Is Not Being Replaced, but It Is Being Repositioned

The App Gap Becomes an Accountability Gap

Microsoft Is Chasing the Post-Smartphone Opening Everyone Else Can See

The Developer Story Is Still the Missing Middle

Security Will Decide Whether Solara Is a Platform or a Pilot

Windows Users Should Watch the Boundary, Not the Branding

The Solara Bet Comes Down to Five Hard Realities

References

Microsoft Puts the Agent Before the App

The Android Base Is the Quietest Rebuke to Windows

Enterprise Control Is the Price of Admission

Just-in-Time UI Is the Most Ambitious and Most Fragile Idea

The Hardware Concepts Are a Map, Not a Product Line

The Pilot List Shows Where Microsoft Thinks Agents Can Earn Their Keep

The Agent Dispatcher Is Where the Platform War Begins

Windows Is Not Being Replaced, but Its Center of Gravity Is Moving

The Security Model Has to Govern Action, Not Just Access

Developers Get a New Surface and a New Dependency

The Demo Is Easy; the Shift Work Is Hard

The Solara Bet Comes Down to Trust at the Edge

The Practical Reading for WindowsForum Readers

References