Changelogs: Week of June 1, 2026

Last week's product work focused on performance transparency, developer security, and infrastructure reliability.

Always-Warm Infra

We've overhauled the warmup infrastructure with a new self-healing keep-warm loop. The loop continuously monitors model state across all nodes and automatically detects and reloads any model that drops from steady state. Previously, a model drop meant the next inbound request would trigger a full cold load. That penalty is now eliminated for any model covered by the keep-warm configuration.

The warmup fix also resolved broken warmup behavior, and updated model cards with verified benchmark data have been published for Whisper Large V3 Turbo and Kokoro 82M.

Public Benchmarks Hub

We've published our first public benchmarks page at polargrid.ai. The headline number is 205ms end-to-end time-to-first-token, measured at p50 across 100 consecutive runs on our Vancouver production edge node. We also publish p95 numbers, head-to-head comparisons against GPT-4o (4x faster) and Claude Sonnet (8x faster), and full methodology disclosure including the specific node, date range, and run count behind every figure.

We built this because “fast” is a claim anyone can make. We wanted to give developers, evaluators, and buyers something they could actually scrutinize. The benchmarks are sourced from live infrastructure, the same nodes handling production traffic, not synthetic lab conditions. The page will be updated as we expand regions and add new models.

Secure CLI Credential Storage

The PolarGrid CLI no longer stores credentials in plaintext.

Starting this week, polargrid loginsaves your API key to your operating system's native credential store: macOS Keychain, Windows Credential Manager, or Linux libsecret. In headless and CI environments where a keychain isn't available, credentials fall back to an AES-256-GCM encrypted file rather than a plaintext JSON file.

If you're already logged in, nothing changes on your end — credentials are migrated automatically the next time you run any CLI command. No re-authentication required.

This closes a long-standing gap (POL-318) and brings the CLI up to the security baseline expected for enterprise tooling. It builds on last week's focus on platform hardening ahead of broader availability.