Wednesday, October 21, 2026 AI news, turned into opportunities PDF newsletter
AI Opportunity Daily
Subscribe
DeepSeekGovernment AIInferenceData centres

Washington bans DeepSeek, DeepSeek gives away its engine, and Amazon's 'dark GPUs'

The US government ordered civilian agencies to rip out DeepSeek, reportedly including products built on it, just as DeepSeek open-sourced the software that runs its own cheap AI service. Meanwhile Amazon is taking delivery of billions of dollars of Nvidia servers it cannot yet switch on for lack of power. Together they show where AI's real constraints now sit: trust, cost and electricity.

Key takeaways

  • US civilian agencies must remove DeepSeek products, and reporting says the order reaches contractors and third-party tools built with DeepSeek, so anyone selling to government needs to know what models sit inside their stack.
  • DeepSeek's Apache-2.0 DeepInfer framework shows how it serves V4.1-Flash cheaply, but it is an offline, single-model release with self-reported performance and is not a full serving stack yet.
  • Amazon is accepting about $5 billion of Nvidia GB300 racks plus about $3 billion a month before power is ready, a sign that electricity, not chips, is now the bottleneck for AI capacity.
Story 1 of 3Policy4 min read

US orders civilian federal agencies to remove DeepSeek, reportedly including tools built on it

The Department of Homeland Security has ordered civilian federal agencies to stop buying DeepSeek products and remove those already in use, citing the risk that sensitive data could reach the Chinese government. The notice was made public this week through the Federal Register.

The US Department of Homeland Security (DHS) has ordered civilian federal agencies to stop buying products and services from Hangzhou DeepSeek Artificial Intelligence and to remove DeepSeek software already running on their systems. CyberScoop and Engadget reported the order on October 19, with the notice scheduled to appear in the Federal Register on Tuesday, October 20. According to CyberScoop, the letter was signed by Homeland Security Secretary Markwayne Mullin months earlier, meaning the ban has quietly been in force for some time and is only now public. Engadget reports that DeepSeek is also barred from federal contracts.

CyberScoop says the order relies on the federal supply-chain law that lets the government exclude risky technology, following a review by the Federal Acquisition Security Council. ITPro reports that the scope goes beyond DeepSeek's own apps: it covers "third-party products and services developed using its implementations" and applies to prime contractors and subcontractors serving agencies such as Treasury, State and Justice. Agencies that used DeepSeek are told to check whether they were compromised, monitor traffic and add logging. Agencies can ask for exceptions with a "compelling justification", but CyberScoop says requests must be filed 60 days in advance.

The stated reasons are data and malware risk. In the notice, DHS says DeepSeek stores data on servers in China, that its hosted service collects personal information when users create accounts, and that prompts and responses "may result in the transfer of sensitive data" to the Chinese government. Engadget quotes the notice as saying the models could "contain malware or other security vulnerabilities." ITPro notes DeepSeek is already restricted in Texas, New York, Virginia, Australia, South Korea and Taiwan, and by the US Commerce Department and Navy. The order landed days after DeepSeek released its V4.1-Flash-1017 model.

Several important questions are unanswered. Reports do not agree on which products count as "developed using" DeepSeek, and none of the coverage explains how agencies should treat DeepSeek's open-weight models when they run on a US company's servers with no data going to China. No removal deadline has been reported. DeepSeek had not publicly responded in the coverage we reviewed, and CyberScoop said DHS and CISA had not answered its questions. Readers should treat the contractor and third-party details as reported by ITPro until the full notice text is widely analysed.

The practical effect is that model provenance is becoming a compliance question. If you sell software, consulting or AI features to US federal agencies, or to companies that do, buyers will start asking which models are inside your product, where they run and who can see the data. That creates work for anyone who can inventory AI use, swap models without breaking products and document the result. It also sends a signal to other governments and regulated industries that already watch US procurement rules, including many in Africa that buy from US-based vendors.

Why it mattersThis moves AI model choice from an engineering preference to a procurement and compliance issue, and the reported reach into contractors and third-party tools means the effect spreads well beyond government offices.

👀 What to watch

Whether DHS publishes guidance on self-hosted open-weight DeepSeek models, whether contractors receive removal deadlines, and whether other governments copy the third-party wording.

3 opportunities from this story

1

AI model inventory audits for government suppliers

Medium⏱ 2–3 weeks💰 Fixed fee per audit, with an optional quarterly re-check retainer

Offer a fixed-price audit that lists every AI model, API and library a company's products and internal tools depend on, flags DeepSeek or other high-risk sources, and produces a clean report a procurement officer can read. Many small and mid-sized software vendors have no idea which models their own tools call. The new order, as reported, makes that ignorance a contract risk.

Best for
Freelance developers, security consultants and small IT agencies
First step this week
Write a one-page AI inventory checklist (APIs, SDKs, model files, browser extensions, no-code automations) and run it free on one client's stack.
Open the full playbook
Launch steps
  1. Build a checklist and a simple report template
  2. Write scripts to scan code repos and dependency files for model names and API endpoints
  3. Run a free pilot and turn it into a case study
  4. Pitch firms that list government or regulated-sector clients
Tools
GitHub code searchDependency scanners such as SyftA spreadsheet or Notion report template
Risks

You are not a lawyer, so avoid giving legal opinions on what the order covers; state findings as facts and refer interpretation to counsel. Scope can creep, so price by system count.

2

Model-swap service: replace DeepSeek without breaking the product

Medium⏱ 1–2 weeks💰 Project fee per integration, plus hourly support

Some products quietly route work to DeepSeek because it is cheap. Offer to switch those calls to an approved alternative, re-test output quality and cost, and document the change. The buyer gets a compliance fix plus a before-and-after cost comparison, which is easier to approve than a vague 'AI review'.

Best for
Developers and AI automation freelancers who already work with LLM APIs
First step this week
Build a small test harness that runs the same 50 prompts through two models and compares quality, latency and cost.
Open the full playbook
Launch steps
  1. Create a reusable evaluation harness
  2. Offer a model-routing layer so future swaps are one config change
  3. Publish a short guide on switching models safely
  4. Reach out to SaaS founders selling to public-sector buyers
Tools
OpenRouter or a similar model routerPromptfoo for evaluationsLiteLLM
Risks

Replacement models may cost more or perform worse on some tasks; agree success criteria up front and show the cost trade-off honestly.

3

AI vendor questionnaire kit for procurement teams

Low⏱ 1–2 weeks💰 Paid template download, plus workshops for procurement teams

Package a ready-to-use questionnaire, scoring sheet and policy template that procurement and IT teams can send to AI vendors: which models they use, where data is processed, how they handle model changes. Government departments, banks and NGOs in Kenya and elsewhere often copy US practice, and few have a template ready.

Best for
Compliance consultants, procurement trainers and policy writers
First step this week
Draft a 25-question AI vendor questionnaire and ask three procurement officers for feedback.
Open the full playbook
Launch steps
  1. Draft questions on model provenance, hosting location and data retention
  2. Add a simple scoring rubric
  3. Sell the kit online and offer a half-day workshop
  4. Update it as new rules appear
Tools
Google Docs or WordGumroad or Paystack for paymentsCanva for the scoring sheet
Risks

Templates are easy to copy and rules change quickly; keep it updated and sell the workshop and updates rather than the file alone.

Story 2 of 3Tools4 min read

DeepSeek open-sources DeepInfer, the engine behind its cheap V4.1-Flash service

DeepSeek released DeepInfer, which it calls the inference framework that powers its production services, under the permissive Apache 2.0 licence. It runs DeepSeek-V4.1-Flash on Nvidia SM100 GPUs and Huawei Ascend 950 chips, though this first release covers offline use only.

On Tuesday, October 20, DeepSeek published DeepInfer on GitHub and announced it on X. The README describes it as "the high-performance inference framework that powers DeepSeek's large-scale production services." Inference is the work of actually running a trained model to answer requests, and it is where most of the ongoing cost of an AI service sits. DeepInfer is released under Apache 2.0, which allows commercial use and modification. The Next Web reported more than 8,000 GitHub stars by Tuesday afternoon; when we checked, the repository showed about 12,000 stars and 1,100 forks.

For now DeepInfer supports a single model, DeepSeek-V4.1-Flash, and two kinds of hardware: Nvidia SM100-class data-centre GPUs and Huawei's Ascend 950 chips. It needs Linux, Python 3.12, and CUDA 13 on Nvidia or CANN 9.2 on Ascend. Features include custom kernels, ways to split work across many chips, speculative decoding (drafting up to five tokens ahead by default and checking them in one pass), asynchronous scheduling, and structured output that forces answers into a regex, JSON schema or grammar. Deterministic, repeatable outputs are available on Nvidia only.

The README says DeepInfer was built mainly on vLLM, the popular open-source serving engine, with inspiration from SGLang and Nvidia's TensorRT-LLM. The Next Web reports that vLLM thanked DeepSeek and said it would improve its own V4.1-Flash support using ideas from DeepInfer. DeepSeek said it is sharing its production stack "to help the community lower compute costs, reduce energy use, and make AI more affordable." It also released deepseek-recipe, a tool that matches how its official API turns text into tokens. The release came a day after the US order banning DeepSeek from civilian federal agencies.

There are clear limits. This release covers offline inference and leaves out three things a production service usually needs: a KV cache system, separation of prompt processing from answer generation, and load balancing across replicas. The README says most of the engine work for that separation is already done but not released. Benchmarks appear only as charts measured on 4 SM100 GPUs for prefill and 64 for decode, which is far beyond a small team's budget. The Next Web, citing Bloomberg, notes there is no independent benchmarking yet, so speed and cost claims are DeepSeek's own.

The significance is less about who can run it tomorrow and more about what it reveals. AI labs usually guard serving tricks closely because they decide margins. Publishing them lets hosting companies and large self-hosters copy DeepSeek's methods, which could push the price of running open-weight models down further. The Next Web notes that open-weight models already account for 23% of spending on Vercel's AI Gateway. For builders, the near-term value is learning: the code is a free, real-world textbook on cheap inference, and experts who can explain and apply it will be in demand.

Why it mattersIt hands the wider community the methods behind one of the cheapest AI services in the market, which could lower hosting prices for open-weight models and makes Huawei chips a first-class target for serious open-source serving software.

👀 What to watch

Whether DeepSeek releases the missing serving pieces, whether independent benchmarks confirm the gains, and how quickly vLLM and hosting providers absorb its techniques.

3 opportunities from this story

1

Plain-English DeepInfer explainer course

Low⏱ 1–2 weeks💰 Free posts to build an audience, then a paid mini-course or sponsorships

Most developers will never run DeepInfer on 64 GPUs, but many want to understand speculative decoding, expert parallelism and structured output. A short, practical course or newsletter series that walks through the real code and explains each trick in plain language fills that gap. Interest is high right now and will fade, so speed matters.

Best for
Developer educators, technical writers and YouTubers
First step this week
Read the README and write a 1,500-word 'what each DeepInfer feature does' post this week.
Open the full playbook
Launch steps
  1. Map each feature to a simple analogy and diagram
  2. Publish a free explainer post and video
  3. Build a 5-lesson paid course on cheap inference techniques
  4. Promote in developer communities and on X
Tools
GitHubExcalidraw for diagramsSubstack or YouTubeGumroad
Risks

The code may change quickly and competing explainers will appear; focus on lasting concepts, not version-specific commands.

2

Inference cost comparison service for startups

Medium⏱ 2–3 weeks💰 Fixed fee per report, or a share of documented savings

Startups using open-weight models often overpay by sticking with one host. Offer a report that compares hosted APIs, GPU rentals and self-hosting for a client's real traffic, using published prices and a small test run. DeepInfer's release is a timely reason for founders to ask whether they could pay less.

Best for
Freelance ML engineers and cloud cost consultants
First step this week
Build a spreadsheet model comparing per-million-token prices from three hosting providers against GPU rental costs.
Open the full playbook
Launch steps
  1. Collect current public prices from hosts and GPU clouds
  2. Create a calculator that takes a client's monthly token volume
  3. Run a short test on rented GPUs to check real throughput
  4. Deliver a report with a recommended setup
Tools
Google SheetsRunpod or Lambda GPU rentalsvLLM
Risks

Prices change often and self-hosting has hidden costs such as staff time; date every report and include those costs.

3

Structured-output data extraction for local businesses

Low⏱ 1–2 weeks💰 Per-document pricing or a monthly subscription

DeepInfer highlights structured output, where a model must answer in a fixed JSON format. That capability, available in many cheap models and APIs, is ideal for turning invoices, receipts, delivery notes and forms into spreadsheet rows. Sell a simple extraction service to accountants, logistics firms and SACCOs that still retype paperwork.

Best for
No-code builders and junior developers
First step this week
Build a demo that turns 20 photographed receipts into a clean CSV using a JSON-schema-constrained model.
Open the full playbook
Launch steps
  1. Define a JSON schema for one document type
  2. Build the extraction flow with a low-cost model
  3. Add a human check step for low-confidence fields
  4. Pitch to three local accounting or logistics firms
Tools
An LLM API with JSON schema supportn8n or MakeGoogle Sheets
Risks

Errors in financial data are costly; keep a human review step and handle client documents under a clear data-protection agreement, in line with Kenya's Data Protection Act.

Story 3 of 3Hardware4 min read

Amazon is buying Nvidia servers faster than it can power them, leaving 'dark GPUs' in warehouses

Internal emails reviewed by Business Insider show Amazon taking early delivery of about $5 billion of Nvidia GB300 server racks, then about $3 billion a month, even though some AWS sites lack the electricity to switch them on. Amazon says staging hardware near sites is standard practice.

Business Insider reported on October 19 that Amazon has set up an "Early Rack Receipt" process to take ownership of Nvidia GB300 server racks before they are installed in working data centres. According to internal August emails the outlet reviewed, as summarised by Investing.com and Storyboard18, Amazon expected about $5 billion of racks at first and about $3 billion more each month after that. Some AWS sites have floor space for the machines but not enough utility power, so finished equipment is waiting in intermediary warehouses as what the reporting calls "dark GPUs".

The numbers around it are large. Amazon expects about $220 billion of capital spending in 2026, up from roughly $200 billion forecast in July, according to Coinpaper, and that figure covers all company infrastructure, not only AI. Its trailing 12-month free cash flow fell to about negative $7.6 billion in the second quarter. At the same time, AWS revenue grew 37% in that quarter, its fastest rate in 18 quarters, and its contracted backlog reached about $496 billion. Cleanview Research estimates Amazon has 44 gigawatts of data-centre capacity under development across 16 US states.

Storyboard18, summarising Business Insider, says AWS chief financial officer John Felton joked at an internal meeting in September that the expansion had turned free cash flow negative. Prasad Kalyanaraman, who oversees much of the build-out, reportedly acknowledged that the AI business was producing large cash outflows that could continue for a couple of years, and said AWS struggled to find skilled workers in West Texas and funded nearby housing. An Amazon spokesperson told Business Insider that staging hardware until power is ready is a routine "best business practice" and disputed suggestions that it lacked a plan to bring the sites live.

Several caveats apply. The $5 billion and $3 billion figures come from internal forecasts in emails, not confirmed purchase totals, and we could not access the original Business Insider article directly, so details here rely on syndicated and secondary summaries. The reporting does not say how many racks are idle today or for how long. Amazon's view is that infrastructure costs arrive years before revenue, so negative free cash flow is a timing effect, not weak demand. CEO Andy Jassy has said Amazon expects demand to exceed capacity into 2027.

The bigger lesson is that the AI bottleneck has moved from chips to electricity, transmission lines and skilled construction workers. Even the richest cloud company in the world is waiting on grid connections. That favours anyone who can make AI cheaper to run per watt, anyone who can help data centres and utilities plan, and anyone who can supply skilled electrical and construction labour. For smaller buyers, it also suggests GPU capacity may stay tight and expensive, which rewards efficient models and careful cost control rather than assuming compute will soon be abundant.

Why it mattersIf the largest cloud provider cannot power the GPUs it already owns, compute will likely stay scarce and pricey, and the money in AI shifts toward energy, efficiency and the people who build and wire data centres.

👀 What to watch

Amazon's next quarterly results for capex and free cash flow, any disclosure of how much hardware is idle, and whether utilities accept Amazon's proposal that large data-centre customers help fund grid upgrades.

3 opportunities from this story

1

Data-centre electrical and solar skills training

Medium⏱ 4–8 weeks💰 Course fees, employer-sponsored cohorts and placement fees

Amazon reportedly had to fund housing to attract skilled workers in West Texas, a sign of how scarce electricians, technicians and commissioning engineers are. Data-centre build-outs are also growing in Kenya and across Africa. A short, practical course that prepares electricians and technicians for data-centre power, cooling and backup systems meets a real demand.

Best for
Vocational trainers, electrical engineers and technical colleges
First step this week
Interview two data-centre or solar installation managers about the skills they cannot find, and outline a 4-week course from their answers.
Open the full playbook
Launch steps
  1. Validate the skill gaps with employers
  2. Design a hands-on syllabus covering UPS, generators, cooling and safety
  3. Partner with a training centre or polytechnic for equipment
  4. Offer the first cohort with an employer placement partner
Tools
Google Forms for employer surveysMoodle or Google ClassroomWhatsApp groups for cohort support
Risks

Requires certified instructors and equipment, and accreditation rules vary; partner with an accredited institution rather than certifying yourself.

2

GPU cost and efficiency audits for AI-using businesses

Medium⏱ 2–3 weeks💰 Fixed audit fee or a percentage of savings over three months

If compute stays scarce, companies spending on GPUs or AI APIs will want to get more from every dollar. Offer an audit that finds waste: oversized models, unused reserved instances, missing caching and chatty prompts. Present the savings as a one-page report with a clear before-and-after.

Best for
Cloud engineers and AI automation freelancers
First step this week
Create a 20-point AI cost checklist and run it on your own projects or one friendly client's bill.
Open the full playbook
Launch steps
  1. Build the checklist covering model size, caching, batching and idle resources
  2. Collect anonymised billing data from a pilot client
  3. Write a savings report with prioritised fixes
  4. Publish the anonymised case study
Tools
Cloud billing dashboardsHelicone or Langfuse for API usageGoogle Sheets
Risks

Savings depend on the client's setup and can be smaller than hoped; avoid promising specific numbers before you see the data.

3

Power-and-grid research newsletter for AI investors and builders

Low⏱ 1 week💰 Free tier plus paid subscriptions, sponsorships and custom research

The story shows that power, grid connections and construction now decide who wins AI capacity. A focused newsletter that tracks data-centre power deals, grid bottlenecks and energy announcements, including in Africa, gives founders, analysts and procurement teams a quick weekly read. Few sources connect AI and energy in plain language.

Best for
Writers, energy analysts and researchers
First step this week
Publish a first issue summarising five recent data-centre power stories with links to primary sources.
Open the full playbook
Launch steps
  1. Set up alerts for data-centre, utility and grid news
  2. Publish weekly with a consistent format
  3. Grow on LinkedIn and X with one chart per issue
  4. Offer paid deep dives once you have 1,000 readers
Tools
Substack or BeehiivGoogle AlertsDatawrapper for charts
Risks

Building an audience takes months and income is uncertain; keep sourcing rigorous and avoid investment advice.

Get these as a PDF every 3 days

Free. One email every 3 days. Unsubscribe any time.

More editions