Build once, publish everywhere

A BotForge module is a declaration: you tell the platform what capabilities, permissions, and workflow triggers your module provides. The platform handles the rest — no dashboard rewrites needed. 1. Create a BotForge account, then register as a developer 2. Submit a module, agent, prompt pack, knowledge pack, or connector for review 3. Declare capabilities[], permissions[], workflowTriggers[], workflowActions[] 4. Our team reviews the submission (auto-validation + manual security review) 5. Once approved, it appears in the Marketplace and auto-wires into installed workspaces See the full manifest field reference on the SDK page, and the submission/review lifecycle on the Marketplace page.

Every marketplace module runs inside BotForge's Sandbox Runtime — a real execution layer, not just a manifest declaration: • Static security scan before approval — blocks eval, filesystem/child_process access, hardcoded secrets, and obfuscated payloads • Workspace isolation — every query is scoped to workspaceId, no raw Prisma exposed • Permission boundary — only the permissions[] you declared are callable, checked on every API call • Plan and install gates re-checked at execution time, not just at install time • Audit logging lives outside module scope — a module can never suppress its own audit trail See the full threat model on our security page.