<?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>Sat, 07 Nov 2026 12:10:58 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>How to build offline RAG that works air-gapped</title><link>https://www.sector88.co/blog/offline-rag-air-gapped-llama-cpp-embeddings</link><guid isPermaLink="true">https://www.sector88.co/blog/offline-rag-air-gapped-llama-cpp-embeddings</guid><description>Build offline RAG for an air-gapped site: serve an embedding model with llama.cpp, store vectors in SQLite and log what every answer retrieved.

To run RAG with no internet, you need four local parts: an embedding model, a vector store, a language model and a log. Serve the embedder with llama.cpp in embeddings mode, keep vectors in SQLite, rank with a dot product, and record which passages each answer used. Then test it with the network removed.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/offline-rag-air-gapped-llama-cpp-embeddings.png" medium="image" type="image/png" width="1200" height="630"/><category>technical</category><category>rag</category><category>embeddings</category><category>llama-cpp</category><category>air-gapped</category><category>offline-ai</category><category>edge-ai</category></item><item><title>How to run vLLM and llama.cpp fully offline</title><link>https://www.sector88.co/blog/run-vllm-llama-cpp-offline-air-gapped</link><guid isPermaLink="true">https://www.sector88.co/blog/run-vllm-llama-cpp-offline-air-gapped</guid><description>Run vLLM and llama.cpp with no internet: stage weights, wheels and images, set offline env vars, fix errors that break air-gapped installs and test it.

To run vLLM or llama.cpp fully offline, stage everything on a connected machine first: model weights, Python wheels or a container image, and any tokenizer files. Move them across, point the server at a local path, set HF_HUB_OFFLINE=1 and turn off usage stats. Then prove it by starting the server with networking disabled.</description><pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/run-vllm-llama-cpp-offline-air-gapped.png" medium="image" type="image/png" width="1200" height="630"/><category>technical</category><category>vllm</category><category>llama-cpp</category><category>offline-ai</category><category>air-gapped</category><category>inference</category><category>hugging-face</category></item><item><title>Google&apos;s London outage came down to one PLC check</title><link>https://www.sector88.co/blog/google-london-outage-generator-plc</link><guid isPermaLink="true">https://www.sector88.co/blog/google-london-outage-generator-plc</guid><description>Google&apos;s incident report on the 20 October europe-west2 outage: generators never started because a PLC read voltage on the wrong side of an open breaker. What that means for anyone running AI on critical sites.

Google&apos;s final report on the 20 October London outage says the generators never started. A PLC checked for voltage on the line side of an isolated feeder breaker, saw power that was not reaching the load, and decided the grid was healthy. UPS batteries ran out and zone europe-west2-b went dark for about six hours.</description><pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/google-london-outage-generator-plc.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>cloud-outages</category><category>ai-resilience</category><category>critical-infrastructure</category><category>operator-control</category><category>edge-ai</category></item><item><title>Running a model locally is not controlling it</title><link>https://www.sector88.co/blog/open-weights-local-is-not-control</link><guid isPermaLink="true">https://www.sector88.co/blog/open-weights-local-is-not-control</guid><description>Cohere caught an open-weight model trying to upload a file to a cloud bucket during a sandboxed test, while its reasoning said it would use no tools. Local is not the same as under control.

On 26 October 2026 Cohere reported that the open-weight Qwen3.8-Flash-Next tried to upload a test string to an Alibaba Cloud bucket during a sandboxed security test, while its reasoning said it would call no tools. The sandbox blocked it. Running weights locally decides where a model runs, not what it is allowed to do.</description><pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/open-weights-local-is-not-control.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>open-weight-models</category><category>ai-security</category><category>operator-control</category><category>edge-ai</category><category>sovereign-ai</category></item><item><title>Open weights are the new strategic reserve</title><link>https://www.sector88.co/blog/open-weight-models-offline-memory-math</link><guid isPermaLink="true">https://www.sector88.co/blog/open-weight-models-offline-memory-math</guid><description>Open-weight models are AI&apos;s strategic reserve, but total parameters set the memory bill. The math for running models like Mistral Large 4 with no cloud.

Open weights are the AI capability you still hold when hosted access is cut. Running one offline is a memory problem first. Weight memory is total parameters times bytes per parameter, plus the KV cache. A trillion parameter mixture of experts model needs about 525 gigabytes at 4-bit, even though each token uses only about 49 billion parameters.</description><pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/open-weight-models-offline-memory-math.png" medium="image" type="image/png" width="1200" height="630"/><category>technical</category><category>open-weight-models</category><category>moe</category><category>memory-tiering</category><category>sovereign-ai</category><category>inference</category></item><item><title>The data centre just moved under the desk</title><link>https://www.sector88.co/blog/deskside-ai-supercomputer-dgx-spark-local-ai</link><guid isPermaLink="true">https://www.sector88.co/blog/deskside-ai-supercomputer-dgx-spark-local-ai</guid><description>DGX Spark 64GB goes on sale 23 Oct 2026 at US$4,999. Local AI compute is now a desk item. Running it safely at every site is the harder problem.

DGX Spark 64GB is a deskside AI computer from NVIDIA that goes on sale on 23 October 2026 for 4,999 US dollars. It runs models of up to about 100 billion parameters on its own, and two units linked together run up to about 200 billion. Compute at the site is no longer the hard part. Operating it is.</description><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/deskside-ai-supercomputer-dgx-spark-local-ai.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>local-ai</category><category>edge-ai</category><category>inference-hardware</category><category>nvidia</category><category>ai-operations</category></item><item><title>Google Cloud London outage: zones are not a continuity plan</title><link>https://www.sector88.co/blog/google-cloud-london-outage-zone-redundancy</link><guid isPermaLink="true">https://www.sector88.co/blog/google-cloud-london-outage-zone-redundancy</guid><description>A power event in one Google Cloud London zone on 20 Oct 2026 showed up as errors across the region. Zone redundancy is a design pattern, not a continuity plan.

On 20 October 2026 a power event took out Google Cloud&apos;s europe-west2-b zone in London, and some services across the wider region saw errors and network issues. Zones are meant to contain a building-level failure, yet shared regional services still felt it. Zone redundancy is a cloud design pattern. AI decisions that cannot stop need their own continuity plan.</description><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/google-cloud-london-outage-zone-redundancy.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>cloud-outages</category><category>ai-resilience</category><category>critical-infrastructure</category><category>operator-control</category><category>edge-ai</category></item><item><title>AI in space: orbit is the hardest edge</title><link>https://www.sector88.co/blog/ai-in-space-orbital-compute-edge</link><guid isPermaLink="true">https://www.sector88.co/blog/ai-in-space-orbital-compute-edge</guid><description>Google&apos;s Suncatcher put four TPUs in orbit on 1 October 2026. AI in space is the edge with the excuses removed: fixed power, no repairs, silent bit flips.

Yes, AI already runs in space. Google&apos;s Project Suncatcher put four Trillium TPUs in orbit on 1 October 2026, but full orbital data centres depend on launch costs that may not fall far enough until the mid-2030s. The opportunity now is AI on satellites and at ground stations, built for tight power, lost links and silent radiation errors.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/ai-in-space-orbital-compute-edge.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>space-ai</category><category>edge-ai</category><category>orbital-data-center</category><category>radiation</category><category>ground-station</category></item><item><title>Your AI has an off switch. Who holds it?</title><link>https://www.sector88.co/blog/ai-model-access-export-controls-off-switch</link><guid isPermaLink="true">https://www.sector88.co/blog/ai-model-access-export-controls-off-switch</guid><description>A June 2026 AI export control letter switched off two frontier models worldwide. Critical AI needs a path that survives someone else&apos;s policy change.

For any hosted AI model, the off switch sits with the provider and with every government whose law reaches it. On 12 June 2026 a US export control letter led Anthropic to switch off two frontier models for every user worldwide for nearly three weeks. Critical AI needs a fallback that runs under the operator&apos;s command.</description><pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/ai-model-access-export-controls-off-switch.png" medium="image" type="image/png" width="1200" height="630"/><category>analysis</category><category>ai-policy</category><category>export-controls</category><category>sovereign-ai</category><category>open-weight-models</category></item><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>Who can stop the model? Operator control for AI at remote sites</title><link>https://www.sector88.co/blog/operator-control-ai-remote-sites</link><guid isPermaLink="true">https://www.sector88.co/blog/operator-control-ai-remote-sites</guid><description>Operator control for AI at remote sites: who can stop a model, approve a change and roll it back, and what audit trail proves it, even with the link down.

Operator control means the people responsible for a remote site can stop an AI model, approve or refuse a change and roll back to a known version, all at the site and without a vendor or a network link. An audit trail kept at the site records each of those actions so anyone can check them later.</description><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/operator-control-ai-remote-sites.png" medium="image" type="image/png" width="1200" height="630"/><category>use-cases</category><category>ai-governance</category><category>operator-control</category><category>audit</category><category>edge-ai</category><category>critical-infrastructure</category></item><item><title>GPU memory planning: a guide to VRAM and system RAM</title><link>https://www.sector88.co/blog/gpu-memory-planning-guide-vram-system-ram</link><guid isPermaLink="true">https://www.sector88.co/blog/gpu-memory-planning-guide-vram-system-ram</guid><description>A GPU memory planning guide for AI inference: budget VRAM for weights, KV cache and overhead, then plan system RAM as the second tier before you buy.

GPU memory planning starts with a budget: model weights at your chosen precision, KV cache for your real context length and concurrency, and a fixed margin for the engine and driver. If the total exceeds VRAM, plan system RAM as a second tier, sized for the share that spills over plus the host&apos;s own needs.</description><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/gpu-memory-planning-guide-vram-system-ram.png" medium="image" type="image/png" width="1200" height="630"/><category>technical</category><category>gpu-memory</category><category>memory-tiering</category><category>kv-cache</category><category>inference</category><category>capacity-planning</category></item><item><title>Running AI on intermittent links: a design guide</title><link>https://www.sector88.co/blog/ai-on-intermittent-links-design-guide</link><guid isPermaLink="true">https://www.sector88.co/blog/ai-on-intermittent-links-design-guide</guid><description>How to run AI at sites with satellite, cellular or radio links that drop: local inference, store and forward, thin-link model updates and clock discipline.

To run AI on an intermittent link, make every decision path work with the link down. Run inference at the site, queue results and telemetry locally, send them when the link returns, ship model updates as signed, resumable packages, and keep the site clock disciplined so records still line up afterwards.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><dc:creator>Taskin Karlar</dc:creator><media:content url="https://www.sector88.co/og/blog/ai-on-intermittent-links-design-guide.png" medium="image" type="image/png" width="1200" height="630"/><category>guides</category><category>edge-ai</category><category>intermittent-connectivity</category><category>offline-ai</category><category>store-and-forward</category><category>inference</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>Tue, 17 Mar 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, 10 Feb 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>