New features, improvements, and fixes shipped to InsForge.
Stripe Payments
InsForge now supports Stripe-powered checkout, subscriptions, and billing portal flows in private preview.
Use Payments Settings to configure Stripe test and live keys, sync products and prices from Stripe, and set up the managed webhook. The main Payments area gives you a quick view into catalog data, customers, subscriptions, and payment history.
Sensitive financial operations such as refunds and disputes still live in the Stripe Dashboard. InsForge focuses on setup, integration, and clear visibility into the parts you need while building.
InsForge Storage now speaks the AWS S3 protocol. Point any SigV4-signing client — the aws CLI, AWS SDKs, rclone, or Terraform — at /storage/v1/s3 on your project and you'll read and write the same buckets you already use from the REST API and the Dashboard.
Generate an access key from Storage → Settings → S3 Configuration in the dashboard. The secret is shown exactly once, so save it on creation.
Clients must use path-style URLs (forcePathStyle: true). Virtual-hosted style is not supported.
Covers bucket, object, and full multipart operations — aws s3 cp with multi-GB files and aws s3 sync run without any client-side config changes.
Starting with InsForge v2.0.8, every project can create long-term database backups and restore from any of them on demand. You'll find the new tool in the project dashboard under Database → Database Studio → Backup & Restore.
Free plan — one active manual backup. To create another, delete the existing one first.
Paid plan — up to five active manual backups. Once the slots are full, delete one before taking a new snapshot. Automatic daily backups (a rolling 7 days) live in a separate quota.
InsForge never overwrites manual backups on its own — deletion is always an explicit action. Manual and automatic backups restore the same way: pick one from the list and click Restore.
InsForge now supports database migrations for developers who want a safer way to evolve their schema with raw SQL.
Successful runs now appear under Database → Database Studio → Migrations, where you can review the migration number, name, executed SQL, and timestamp from the dashboard.
Only successful runs are added to migration history, so the dashboard stays focused on applied changes.
If you're building with AI agents, InsForge Skills and the InsForge CLI can manage migrations as part of your backend workflow automatically, so schema changes stay in sync without extra manual steps.
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.
