InsForge setup with Coolify, OpenCode and GLM 5.2

This tutorial tests InsForge as an open source backend alternative to Supabase, first in the cloud and then on a VPS with Coolify already installed. The presenter uses OpenCode with GLM 5.2 to create a React and Vite contact form, configure its database table and deploy a working frontend.

The server setup covers enabling Coolify's API and MCP setting, creating an API token and pointing a Cloudflare DNS A record at the VPS. The presenter then asks the AI agent to move the project to the self-hosted backend. He also flags an HTTPS issue: the dashboard's API-key copy button does not work in his setup without SSL.

Deployment needs troubleshooting. After configuring a Vercel token, Team ID and Project ID, the service fails. The agent attributes the failure to a Deno functions container repeatedly failing to download a module. The presenter gives it SSH access to investigate, and later demonstrates form submissions reaching the server's database without refreshing the dashboard.

The walkthrough also documents limits. The Sites section remains absent despite the Vercel configuration. The presenter reports that each InsForge installation supports one project, though it can contain multiple tables and schemas. This is an exploratory setup with errors and repairs, rather than evidence that generated infrastructure needs no review.