<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Sector88 Blog</title><description>Analysis and field notes on AI beyond the cloud: edge, sovereign, defence, space, energy and critical infrastructure AI.</description><link>https://www.sector88.co/blog</link><language>en</language><atom:link href="https://www.sector88.co/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Tue, 13 Oct 2026 11:17:05 GMT</lastBuildDate><image><url>https://www.sector88.co/icon-192.png</url><title>Sector88 Blog</title><link>https://www.sector88.co/blog</link></image><item><title>The cloud has a blast radius: AI continuity in 2026</title><link>https://www.sector88.co/blog/cloud-outages-ai-blast-radius</link><guid isPermaLink="true">https://www.sector88.co/blog/cloud-outages-ai-blast-radius</guid><description>War, heat, lightning, an automated account flag and ransomware took cloud regions down in 2026. AI in critical systems needs a smaller blast radius.

In 2026 cloud regions failed for physical and administrative reasons: drone strikes, overheating, lightning, a three millisecond voltage dip, an automated account suspension and ransomware. Each outage lasted hours or months. AI that runs critical systems needs continuity, which means it keeps producing correct, accountable output at the site when the cloud, the link or the supplier is gone.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/cloud-outages-ai-blast-radius.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>ai-resilience</category><category>cloud-outages</category><category>critical-infrastructure</category><category>edge-ai</category><category>sovereign-ai</category></item><item><title>Self-replicating AI will live on compute nobody owns</title><link>https://www.sector88.co/blog/self-replicating-ai-compute-nobody-owns</link><guid isPermaLink="true">https://www.sector88.co/blog/self-replicating-ai-compute-nobody-owns</guid><description>Anthropic says small AI models may soon self-replicate across cheap IoT devices. The risk is not edge AI. It is edge compute with no operator in command.

On 12 October 2026 Anthropic reported that small AI models may be months away from copying themselves across cheap, poorly secured internet devices such as smart TV boxes. The risk is not AI at the edge. It is compute nobody owns. Every machine that runs a model needs an operator who knows what is running and can stop it.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/self-replicating-ai-compute-nobody-owns.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>edge-ai</category><category>ai-security</category><category>self-replicating-ai</category><category>critical-infrastructure</category><category>sovereign-ai</category></item><item><title>Data centres are now targets</title><link>https://www.sector88.co/blog/data-centres-are-now-targets</link><guid isPermaLink="true">https://www.sector88.co/blog/data-centres-are-now-targets</guid><description>Drone strikes on data centres in Russia and Ukraine show a cloud region is a building. AI in critical systems must keep running when one goes dark.

Data centres have become physical targets in the war between Russia and Ukraine. On 8 October 2026 a drone strike took a Yandex Cloud availability zone offline, and it was still down at the end of the day. Failover kept running workloads alive, but creating new resources was limited. AI in critical systems needs to keep working, and stay under the operator&apos;s command, when a facility or link is lost.</description><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/data-centres-are-now-targets.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>critical-infrastructure</category><category>cloud-outages</category><category>resilience</category><category>edge-ai</category><category>sovereign-ai</category></item><item><title>Location is not control: Australia&apos;s AI sovereignty test</title><link>https://www.sector88.co/blog/location-is-not-control-australias-ai-sovereignty-test</link><guid isPermaLink="true">https://www.sector88.co/blog/location-is-not-control-australias-ai-sovereignty-test</guid><description>Megawatts and postcodes are not sovereignty. Australia&apos;s AI Standards must force a visible control chain for Commonwealth and critical infrastructure AI, or the country will certify racks while someone else owns the layer that matters.

Australian sovereignty over AI is not about where the data centre sits. It is about who holds the keys, who chooses the models, who keeps the record of what ran, and who can stop the system. The Standards should require a plain-language control attestation for Commonwealth and critical infrastructure AI.</description><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/location-is-not-control-australias-ai-sovereignty-test.png" medium="image" type="image/png" width="1200" height="630"/><category>company</category><category>sovereign-ai</category><category>critical-infrastructure</category><category>australia</category><category>ai-standards</category><category>national-security</category></item><item><title>How to fix vLLM OOM (CUDA out of memory): 8 steps</title><link>https://www.sector88.co/blog/how-to-fix-vllm-oom</link><guid isPermaLink="true">https://www.sector88.co/blog/how-to-fix-vllm-oom</guid><description>vLLM crashing with CUDA out of memory? Fix it in 8 steps, from gpu_memory_utilization and max_model_len to quantisation and memory tiering.

vLLM OOM crashes almost always come from one of four causes: gpu_memory_utilization set too high, max_model_len larger than the KV cache budget allows, too many concurrent sequences, or the model simply not fitting in VRAM at the requested precision. Work through the eight steps below in order. Most crashes fix at step three. If they do not, you need memory tiering across VRAM and system RAM.</description><pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/how-to-fix-vllm-oom.png" medium="image" type="image/png" width="1200" height="630"/><category>technical</category><category>vllm</category><category>oom</category><category>gpu-memory</category><category>inference</category><category>llama</category><category>memory-orchestration</category><category>kv-cache</category></item><item><title>What is sovereign AI? Definition and 5 tests</title><link>https://www.sector88.co/blog/what-is-sovereign-ai</link><guid isPermaLink="true">https://www.sector88.co/blog/what-is-sovereign-ai</guid><description>Sovereign AI is AI you fully control: the model, the data and the infrastructure stay under your legal and physical control. Definition, examples and 5 tests.

Sovereign AI is artificial intelligence that a country or organisation controls end to end. The model weights, the prompts and outputs, and the infrastructure they run on all stay under its own legal and physical control. No foreign law can compel access, no vendor can change or switch it off, and it keeps running without anyone else&apos;s cloud.</description><pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/what-is-sovereign-ai.png" medium="image" type="image/png" width="1200" height="630"/><category>guides</category><category>sovereign-ai</category><category>air-gapped-ai</category><category>on-premise-ai</category><category>data-residency</category><category>defence-ai</category></item><item><title>The On-Premise AI Gap: Why Cloud Isn&apos;t Always the Answer</title><link>https://www.sector88.co/blog/on-premise-ai-gap</link><guid isPermaLink="true">https://www.sector88.co/blog/on-premise-ai-gap</guid><description>Cloud AI APIs are convenient, but they&apos;re not viable for defense, government, healthcare, and industrial operations. Here&apos;s why on-premise AI infrastructure matters.</description><pubDate>Tue, 20 Jan 2026 00:00:00 GMT</pubDate><dc:creator>Sector88 Team</dc:creator><media:content url="https://www.sector88.co/og/blog/on-premise-ai-gap.png" medium="image" type="image/png" width="1200" height="630"/><category>use-cases</category><category>on-premise-ai</category><category>sovereign-ai</category><category>air-gapped</category><category>enterprise-ai</category><category>cloud-alternative</category></item><item><title>Why We Built Sector88</title><link>https://www.sector88.co/blog/why-we-built-sector88</link><guid isPermaLink="true">https://www.sector88.co/blog/why-we-built-sector88</guid><description>From solving GPU memory crashes in production ML systems to building infrastructure that makes on-premise AI deployment actually work. The story behind Sector88.</description><pubDate>Tue, 13 Jan 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/why-we-built-sector88.png" medium="image" type="image/png" width="1200" height="630"/><category>product</category><category>sector88</category><category>founder-story</category><category>on-premise-ai</category><category>infrastructure</category></item><item><title>Introducing Sector88: AI compute for constrained hardware</title><link>https://www.sector88.co/blog/introducing-sector88</link><guid isPermaLink="true">https://www.sector88.co/blog/introducing-sector88</guid><description>Running AI should not require unlimited GPU budgets or a cloud connection. How Sector88 runs AI compute on constrained hardware, starting with the memory wall.</description><pubDate>Tue, 06 Jan 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/introducing-sector88.png" medium="image" type="image/png" width="1200" height="630"/><category>product</category><category>sector88</category><category>memory-optimization</category><category>on-premise-ai</category><category>gpu-efficiency</category><category>enterprise-ai</category></item></channel></rss>