Changelog

Bring Your Own PostHog

Until now, Analytics was cloud-only and the page wasn't even in the sidebar of a self-hosted deployment. It is now, and it connects to a PostHog project you already own: open Analytics, paste a PostHog personal API key, pick US or EU, and click Connect PostHog.

The key is the only thing you type. InsForge validates it against PostHog before storing it, encrypted, on your own backend, and reads the project ID and public phc_ key back automatically. From there the page works the same as on Cloud: web analytics KPIs, breakdowns, retention, and session replays.

Or connect from the CLI:

npx @insforge/cli posthog setup --key <phx_...>

Self-Hosted Web Scraper

The Web Scraper gets the same treatment. Connect your own Apify account by pasting an Apify API token from the Apify Console (Settings → Integrations). The token is checked against Apify before it is written and stored encrypted on your backend, and the Actors, Runs, and Dataset tabs fill with your account's data.

The CLI equivalent:

npx @insforge/cli webscraper apify connect --token <apify_api_...>

On Cloud, both features keep their one-click OAuth connect. Nothing changes there.

Bring Your Own S3 Storage to Self-Hosted InsForge

Self-hosted InsForge can now use any S3-compatible service as its storage backend. Connect AWS S3, Cloudflare R2, Wasabi, Tencent COS, Aliyun OSS, or an existing MinIO, RustFS, Garage, or Ceph deployment by setting the new S3_* environment variables.

Prefer to keep everything on one host? InsForge now includes Docker Compose overlays for MinIO and RustFS. Each overlay starts the storage service, creates the backing bucket, and keeps it on the private Docker network:

# MinIO
docker compose -f docker-compose.prod.yml -f docker-compose.minio.yml up -d

# RustFS
docker compose -f docker-compose.prod.yml -f docker-compose.rustfs.yml up -d

Private storage endpoints and providers without S3 POST policy support can use the new proxy mode, which streams uploads and downloads through the InsForge backend and supports ranged downloads for media seeking.

With an S3 backend connected, the S3 Configuration panel is available in the self-hosted dashboard. You can create access keys and use the InsForge S3-compatible gateway with tools including the AWS CLI, rclone, boto3, and Terraform.

Existing files are not migrated automatically when you switch from local storage to S3, so move them before changing the backend.

Read the self-hosted storage guide

Passwordless Login with Email OTPs

Your apps can now sign users in with a six-digit code sent to their email address—no password required.

Request a code from POST /api/auth/email/send-otp, then log in through POST /api/auth/sessions with the email, code, and method: "otp".

For a new email address, InsForge creates a verified passwordless user only after the code is confirmed. Existing users can sign in with the same flow. Codes expire after five minutes, work once, and are consumed after three failed attempts. The code-request endpoint also returns the same response for known and unknown emails to prevent account discovery.

The new Email OTP Sign-In template is available with the other authentication email templates in the dashboard, so you can customize the subject and HTML for your app. Self-hosted instances need Custom SMTP configured to deliver sign-in codes.

Read the Email OTP REST API guide

Both features are available in InsForge v2.2.9.

Connect Your Coding Agent with Your User API Key

The organization projects page now has a floating Connect your coding agent dock. It generates a setup prompt with your user API key (uak_...), allowing the InsForge CLI to authenticate as your signed-in user and connect the current project.

Click Copy prompt, then paste it into Claude Code, Cursor, Codex, Windsurf, Cline, or any other coding agent to continue setup from your working directory.

Connect Your Coding Agent in One Paste

The organization projects page now has a floating Connect your coding agent dock with a ready-to-paste setup prompt. Click Copy prompt, paste it into Claude Code, Cursor, Codex, Windsurf, Cline, or any coding agent, and the agent takes it from there:

1. Signs in to the InsForge CLI with your user API key — the key is filled in when you copy, and never displayed on screen
2. Creates a project linked to your working directory with npx @insforge/cli create (or links an existing one with npx @insforge/cli link), which also installs the InsForge agent skills and writes an AGENTS.md
3. Follows those skills to build your backend: the insforge-cli skill for infrastructure and the insforge skill for app code with @insforge/sdk

No dashboard clicking, no copying keys around, no reading setup docs — one paste turns your coding agent into an InsForge-native backend engineer.

We're rolling this out gradually, so it may not be on your projects page yet. If you'd rather keep the page clean, dismiss the dock and it stays away for the rest of your session.