Edge Functions

Documentation Index

Fetch the complete documentation index at: https://docs.insforge.dev/llms.txt

Use this file to discover all available pages before exploring further.

Use InsForge edge functions to run TypeScript on Deno, deployed close to your users for low latency. Functions can be invoked on-demand from any client, chained from database triggers, or scheduled to run on a cron expression. The runtime ships standard fetch, streaming responses, and ESM imports out of the box.

​

Features

​

HTTP triggers

Every function is reachable at https://<project>.insforge.dev/functions/<name>. Standard fetch in, standard Response out. Streaming, JSON, redirects, and websockets all work.

​

Schedules

Attach a cron expression to a function and InsForge invokes it on time, with retry on failure. See Schedules for the cron syntax and execution model.

​

Database triggers

Wire a function to fire on INSERT, UPDATE, or DELETE against a table. The function receives the row payload and runs with a service-role JWT so it can perform privileged follow-up writes.

​

Secrets and environment variables

Set env vars and secrets per function. The dashboard, CLI, and MCP all read and write the same store; secrets never round-trip through your repo.

​

Logs

Structured logs are captured per invocation, queryable by status, duration, and function name. The InsForge MCP get-function-logs tool lets your agent diagnose failures without leaving the editor.

​

Deno standard library

Use the Deno standard library and any ESM module from jsr.io, esm.sh, or npm: specifiers. You don’t run a bundler, and there’s no node_modules directory to ship.

​

Concepts

​

Build with it

​

Next steps

• Set up the CLI to link your project (the recommended path).
• Browse the TypeScript SDK reference for invocation patterns.