Changelog

New features, improvements, and fixes shipped to InsForge.

Backend Alert Notifications

We now send email notifications for backend alerts (e.g. instance down) on every project. You will be notified when an incident occurs and when it recovers.

To avoid noise, we added a suppression policy: critical backend alerts are sent at most 3 times within a 3-day window.

Integrations Hub

We added an Integrations entry to the insforge.dev navigation bar, giving you a dedicated hub to discover and connect third-party services with your InsForge project.

The first wave of integrations focuses on authentication — you can browse guides for Clerk, Auth0, Kinde, Stytch, and WorkOS, each with step-by-step setup instructions and sample apps.

More categories — payments, messaging, storage, and devtools — are on the way.

Edge Function Editor

You can now view, edit, download, and delete your edge functions directly from the dashboard. The built-in code editor gives you full visibility into your function source code without needing the CLI or an external editor.

Edge Function Editor

Custom Domains for Project Websites

Developers can now add their own custom domains to project websites deployed with InsForge. Add a domain, follow the DNS records shown in the dashboard, and verify it directly in the deployment settings when propagation is complete.

Custom domains for project websites

Realtime Message Retention

InsForge Realtime now supports configurable message retention, so you can automatically clean up old realtime messages without manual maintenance. Choose a retention window like 30, 90, or 180 days, or keep messages forever, and InsForge will prune old messages on a daily schedule.

Realtime message retention settings

Deprecated: Hosted Auth Packages

The packages @insforge/react, @insforge/nextjs, and @insforge/react-router are now deprecated and should not be used in new projects. These packages provided pre-built authentication UI components that redirected users to backend-hosted auth pages using a cross-domain flow that passed tokens via URL query parameters.

What to use instead: Use @insforge/sdk directly for all authentication flows. Build your own auth UI and call SDK methods like signUp(), signInWithPassword(), signInWithOAuth(), and verifyEmail(). For SSR frameworks (Next.js, Remix, SvelteKit), use server mode with createClient({ isServerMode: true }) and manage tokens in httpOnly cookies.

View Auth SDK documentation

Open-Source Development Skills

We added open-source development skills to the InsForge platform repository. These skills guide AI agents contributing to the InsForge codebase with best practices for each package: backend, frontend, UI, shared-schemas, and docs. They follow the Agent Skills Open Standard and are available for Claude Code, Codex, and other compatible agents.

View InsForge repository

Bring Your Own Key (BYOK) for AI Gateway

We now support Bring Your Own Key (BYOK) for OpenRouter. You can configure your own API key directly in the AI gateway, giving you full control over usage, billing, and model access. The platform automatically handles key resolution across BYOK, managed, and environment-based credentials, so your applications continue to run without interruption.

We've also introduced a new Gateway Credentials UI to make key management simple and transparent, along with improved request handling that surfaces both response results and key sources for better debugging and visibility.