infrai vs Netlify

SMS Delivery Status Polling for Waitlist Outage Alerts

The article advises that teams should only rely on an SMS API for critical outage alerts if their backend can poll delivery status and own retry, escalation, cancellation, and timing logic. Delivery reliability and timing constraints drive the design: define service-level objectives, record four reliability invariants (application-owned send IDs, bounded/idempotent retries, defined next actions per delivery state, and incident recovery that suppresses obsolete alerts), and treat providers as transport adapters. The author shortlists Twilio, Vonage, Sinch, and Infrai for evaluation, provides load-testing guidance, and includes a runnable Python example that polls SMS status, honors Retry-After, and applies backoff. The recommended architecture keeps durable incident state in the application and makes provider polling a replaceable adapter.

• Choose an SMS API for critical outage alerts only if the backend can poll delivery status and implement retry, escalation, cancellation, and timing logic.
• Four reliability invariants: application-owned identifier per send; bounded and idempotent retries; every delivery state must map to a defined next action; incident recovery must stop obsolete alerts.
• Article shortlists Twilio, Vonage, Sinch, and Infrai as candidate SMS providers to validate against the same decision record.

Backend-Owned SMS OTP: Cooldowns and Attempt Caps

This technical blog post explains best practices for implementing passwordless phone logins using SMS OTPs in an Express/Node.js backend. It argues that the backend must own resend cooldowns, verification attempt counters, and anti-abuse policies (not the client), model the authentication state machine (ready → code_sent → verified/expired/locked), persist minimal authoritative state, use atomic database transitions, emit single transition events for observability, and use idempotency keys and retry/backoff handling when calling providers. Provider choices (Twilio, Firebase, Auth0, Amazon SNS, Infrai) are discussed with trade-offs between managed verification and owning template/state-machine responsibilities.

• The article recommends the Express/Node.js backend should own SMS OTP resend cooldowns, maximum verification attempts, and anti-abuse counters rather than trusting the client.
• Designs should expose explicit states: send-code, verify-code, resend-code, and lockout; persist minimal authoritative state (challenge ID, phone identity, expiry, next-send time, counters, lockout).
• Use atomic database transitions and idempotency keys tied to admitted transitions to prevent race conditions and duplicate sends.

Bulk LLM Text Classification with Tenant Chargeback

The article recommends treating tenant accounting as the primary artifact when performing bulk CSV moderation with LLMs: create a tenant-owned job with stable row IDs, estimate costs before submission, submit asynchronous batch classification (preferably chat classification with a closed label set), and attach returned results and export references to the same tenant ledger for reconciliation. The author provides an example TypeScript batch submission pattern (idempotency derived from the validated request, bounded retries, handling 429), argues for allocating costs at the job boundary and reconciling at the row level, and discusses when to call providers directly (Infrai, OpenAI, Anthropic, Google Gemini) versus renting batch execution.

• Author recommends asynchronous chat classification with a closed label set and using a tenant ledger as the primary artifact for billing and reconciliation.
• Pattern: create a tenant-owned job with a stable ID per accepted CSV row, show an estimate before submission, persist the provider batch identifier, then reconcile results and costs back to the job and rows.
• TypeScript example demonstrates deriving an idempotency key from the validated batch-request.json, honoring Retry-After for HTTP 429, and using bounded exponential backoff.

TypeSafe Jev now available in AI Gateway

TypeSafe’s Jev model is now available through Netlify’s AI Gateway with zero configuration required. Install @typesafe-ai/sdk and use it directly in your Netlify Functions — no API keys to create, no provider config, no base URLs to wire up. AI Gateway handles credentials automatically, and usage is billed to your Netlify credits like every other model in the gateway.

WebHaste Launches Local-First CMS for Smaller Websites

WebHaste, a free, local-first Content Management System (CMS) developed by Destination Toolbox, has been released in public beta. Designed for teams building and managing smaller websites (under 100 pages), it aims to eliminate server-side infrastructure headaches like plugin updates, SSL certificate management, and security concerns. The CMS operates as a Chrome extension, offering file management, visual editing, real-time previews, and template rendering. It deploys finished sites to CDNs like Cloudflare Pages and Netlify, and supports local ownership of site files. Key features include built-in SEO (sitemaps, meta descriptions, OpenGraph tags), agency-friendly tools (shared drives, Git, per-page tracking pixels), and AI collaboration readiness with file-aware AI agents for content management without publishing rights. The product is positioned as an alternative to database-driven systems like WordPress for simpler sites, including informational sites, blogs, campaign landing pages, and portfolios.

• WebHaste is a free, local-first CMS released in public beta.
• The CMS is available as a Chrome extension and deploys to Cloudflare Pages and Netlify.
• WebHaste targets smaller websites, including informational sites and blogs under 100 pages.

Compete in OpenAI’s WebMCP Challenge with Netlify

Netlify announced a partnership with OpenAI for the WebMCP Challenge, which opens on August 25, 2026. Netlify is backing builders with 3 million credits and a $5,000 prize pool to build new agent-native web apps or add WebMCP support to existing ones. The challenge features a kickoff livestream on August 25, community office hours on August 31, submissions closing on September 3, and winners announced on September 23, 2026.

• Netlify is partnering with OpenAI to support WebMCP and the WebMCP Challenge, which opened on August 25, 2026.
• Netlify will provide 3 million credits and a $5,000 prize pool for participants.
• Participants must build a new agent-native web app or add WebMCP support to an existing app.