Intel Unveils Starfire Chip Designed for AI Processing on US Military Satellites in Orbit
Intel has introduced a new system-on-chip called Starfire that is intended to operate not in data centers but in Earth orbit, where it must endure temperature swings from -55 °C to 125 °C and continuous exposure to cosmic radiation.
The chip was developed under contract for the US government and combines eight general-purpose CPU cores, a three-die neural-network accelerator, and a graphics block inside a single Foveros package. Two power variants are offered: a 10 W version rated at up to 45 TOPS and a 35 W version rated at up to 75 TOPS.
Manufacturing processes are deliberately split inside the same package. The CPU cores and neural accelerator are fabricated on Intel’s leading-edge Intel 18A node, while the graphics module uses the more mature Intel 3 process—the same heterogeneous approach Intel previously employed in the server processor Clearwater Forest. Because smaller transistors hold less charge, they are more susceptible to single-event upsets from space radiation; therefore, reliability will be achieved through circuit-level and architectural hardening rather than process maturity alone.
For decades the space-grade processor market has been dominated by BAE Systems’ RAD750, a 200 MHz device flying on Mars rovers and the Kepler and Fermi telescopes. Newer offerings such as the RAD5545 and a forthcoming Microchip design for NASA promise roughly an order-of-magnitude performance increase, yet they remain focused on telemetry and control. Starfire, with its dedicated neural accelerator, is aimed at a different mission: performing artificial-intelligence inference and real-time data analysis directly on board the satellite.
The device is still a demonstration vehicle. Radiation-tolerance figures are still being measured, and the chip has not yet received formal space-radiation certification. Intel cautions that final specifications may change. First engineering samples are slated for delivery in the third quarter of 2026 through the company’s Intel Government Technologies division.
The project carries strategic weight for Intel, which remains the only US company capable of producing chips of this complexity. It participates in the Pentagon’s RAMP-C and SHIP programs. Company roadmaps indicate that 18A process yields are expected to reach industry parity only in 2027, potentially affecting the timeline for volume production of space-qualified parts.
Related articles
OpenAI Releases GPT-6.1 Terra: Cost-Effective Model Focused on Computer Control, Image Analysis and Practical Automation
OpenAI has launched GPT-6.1 Terra, a new model positioned between its high-end GPT-6 Astra and more affordable options in the GPT-6 family. The model emphasizes real-world computer interaction, visual understanding of documents and interfaces, and reduced error rates rather than raw reasoning benchmarks. It supports a 1.05 million token context window, image inputs, and tool use through the Responses API while cutting input token prices by half compared with its predecessor. Published benchmarks show substantial gains on Terminal-Bench 4.0, OSWorld 2.1 and Agents' Last Exam, with error rates dropping sharply at both low and maximum reasoning levels. OpenAI stresses that the model still requires human oversight for high-stakes actions and does not directly process audio or video. The release targets developers and enterprises seeking reliable automation of repetitive multi-step tasks at lower cost than flagship models.
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.