Live Nov 18 · Cohort 3Nov 18, 19:00 MSK — free hands-on AI agents live workshop · Live Cohort 3 starts Nov 23Join Nov 18 Live →Cohort 3 (Nov 23)
InfrastructureAPI / Product · ActionableHabr AI→ original

Microsoft Patents Training AI on Idle GPUs, With Payment for the Work

Microsoft has filed a patent application for a platform that splits neural network training into micro-tasks and hands them out to the idle GPUs of home PCs and laptops. The client monitors GPU load, temperature and memory, and pauses as soon as you launch a game. Servers double-check the results, and owners are paid in points that can be exchanged for money or AI services. So far it's only a patent, with no timeline or pricing.

AI-processed from Habr AI; edited by Hamidun News
Microsoft Patents Training AI on Idle GPUs, With Payment for the Work
Source: Habr AI. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceHabr AI ↗
Editor-in-Chief
Key metric #1The application was filed in April 2025 and published by the USPTO on November 5, 2026
Key metric #2An extra 250 W for 4 hours a day comes to about $10.50 a month in electricity
Key metric #3The main risk is errors on home hardware, which is why re-verification is needed

Imagine this: you close a game and go off to dinner, and meanwhile your graphics card is crunching a piece of someone else's neural network. You come back, the game launches as usual, the fans are quiet, and points have trickled into your account. That is roughly the scheme Microsoft describes in its patent application Opportunistic Micro-training on Edge Devices Using Spare GPU Utilization.

The application was filed by Microsoft Technology Licensing in April 2025 and appeared in the USPTO database on November 5, 2026. For now it's only paper: the company has named neither a launch date nor pricing.

What problem it solves and how it works

Model training runs up against the shortage and cost of GPUs in data centers. Meanwhile, millions of people have powerful graphics cards at home that sit idle for most of the day. The patent proposes pooling them together.

The scheme looks like this. Training servers slice a large job into many micro-tasks and send them over the internet to PCs, laptops and even smartphones. The client app constantly tracks GPU load, occupied video memory, chip temperature and power consumption. If you start a game or a render, the load is reduced or the computation pauses. If the card starts to get very hot, the same thing happens.

Result verification is described separately. Home computers are not protected against random computational errors the way server hardware is. So the platform's servers re-check what they receive from users, so that an error on one laptop does not corrupt the main model.

Internal points are credited for the work. According to the authors, they can be exchanged for real money, licensed software or free access to commercial AI services. In spirit, it's Folding@home, only commercial and aimed at machine learning tasks.

Will it pay off for the GPU owner

Let's work through an example. Suppose a computer under load draws 250 W more than usual for four hours a day. That is 0.25 kW × 4 hours × 30 days = 30 kWh a month. At a rate of $0.35 per kWh (as in some regions of the US and Europe), the electricity bill rises by $10.50 a month.

On top of that you have to add wear on the graphics card and fans. For participation to make sense, payouts must cover both the electricity and the depreciation. There are no rates, so it is impossible to calculate the benefit today. Even the PC owner cannot estimate what points they would get for 30 kWh.

What matters here for developers and product managers

First, a caveat. The description of the patent known to us does not answer the main engineering question: how to train a large model when GPUs are connected by ordinary home internet. Classical training requires fast data exchange between cards, while home connections have high latency and low speeds. So the "micro-tasks" of the title most likely refer to small-scale fine-tuning or to subtasks that parallelize well. This is our interpretation, not a statement from the application.

The practical takeaways are these:

  • Don't build such a service into your plans. A patent is not a product, and many applications remain just applications.
  • If you are building a desktop app with background GPU load, take the scheme from the patent as a checklist. Monitor load, VRAM, temperature and power, and immediately yield resources to priority processes.
  • Any computation on untrusted clients needs to be verified. Spot recomputation on the server is usually cheaper than a poisoned or corrupted model.
  • Founders should watch the GPU rental market. If a major player seriously launches a distributed pool, it will put pressure on cloud compute prices. For now the signal is weak.

There are also open questions that the patent application, as retold, does not answer. What data and model weights will end up on other people's computers? How will they be protected from extraction? What about legal liability if a card fails? The answers will determine whether the idea becomes a service or remains a pretty diagram in the USPTO database.

Bottom line: Microsoft has shown that it thinks of millions of home GPUs as one more resource for AI. For the industry this is an intriguing signal of the hunger for compute, but not a reason to change anything in your plans today.

Story

Key Questions Answered

What problem it solves and how it works?

Model training runs up against the shortage and cost of GPUs in data centers. Meanwhile, millions of people have powerful graphics cards at home that sit idle for most of the day. The patent proposes pooling them together. The scheme looks like this. Training servers slice a large job into many micro-tasks and send them over the internet to PCs, laptops and even smartphones. The client app constantly tracks GPU load, occupied video memory, chip temperature and power consumption.

What are the key details on Will it pay off for the GPU owner?

Let's work through an example. Suppose a computer under load draws 250 W more than usual for four hours a day. That is 0.25 kW × 4 hours × 30 days = 30 kWh a month. At a rate of $0.35 per kWh (as in some regions of the US and Europe), the electricity bill rises by $10.50 a month. On top of that you have to add wear on the graphics card and fans. For participation to make sense, payouts must cover both the electricity and the depreciation. There are no rates, so it is impossible to calculate the benefit today.

What matters here for developers and product managers?

First, a caveat. The description of the patent known to us does not answer the main engineering question: how to train a large model when GPUs are connected by ordinary home internet. Classical training requires fast data exchange between cards, while home connections have high latency and low speeds. So the "micro-tasks" of the title most likely refer to small-scale fine-tuning or to subtasks that parallelize well. This is our interpretation, not a statement from the application.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…