Your editor.
Your terminal.
Your agent.
dForge meets you where you already work. Syntax-highlighted, schema-validated module files in VS Code. A CLI on npm you run with npx or install locally. An MCP server that lets your AI agent drive the whole module surface. And an importer that turns an existing database into a working module.
Author modules
where you
already write code.
The dForge VS Code extension understands every file in a module. DSL syntax highlighting, JSON-Schema validation, and inline errors across entities, views, roles, actions and triggers — so a typo is a red squiggle, not a failed install.
Get the VS Code extensionEntities, fields, formulas and the action DSL are colorized so module files read like real code, not config soup.
Every module file is validated against its schema as you type. Required keys, enum values and field types are checked before you ever package.
Bad references, unknown field types and malformed views surface in the Problems panel with the exact line — caught in the editor, not at install.
Zed highlighting ships today and more editors are on the way. The schemas are open, so any JSON-Schema-aware editor gets validation for free.
{
"entity": "lead",
"label": "Lead",
"fields": [
{ "name": "company", "type": "text", "required": true },
{ "name": "stage", "type": "flags", "options": ["new","won"] },
{ "name": "owner", "type": "ref", "to": "user" }
]
}One command
to scaffold,
validate & ship.
The dForge CLI lives on npm. Run it ad-hoc with npx — no install — or add it to a project and wire it into your scripts and CI. Scaffold a module, validate it against the schemas, package a versioned .dforge artifact, and install it into any tenant.
No global install, always the latest version. Best for scaffolding a new module or a one-off validate / package run.
Add it as a dev dependency and call it from npm scripts and CI. Pin a version so every developer and every pipeline runs the same toolchain.
- →scaffold a new module workspace with the right layout and schemas
- →validate every file against the dForge JSON-Schemas
- →package a versioned .dforge artifact
- →install or upgrade a module into a tenant
Let your agent
drive the
whole surface.
The dForge MCP server exposes the entire module surface to AI agents like Claude Code. The agent adds entities and fields, builds views, wires roles, writes actions and triggers, then packs and installs — calling real tools, not pasting guesses. The built-in skill knows every convention.
Create entities and fields, add references and dependencies — the agent calls typed tools, so the metadata is always valid.
Views, folders, menus, roles, actions, triggers, reports and webhooks — the whole module is addressable from the agent.
Inspect, pack a versioned artifact, and install it into a tenant — the build-and-ship loop runs end to end from the conversation.
Add an SLA timer field to the ticket entity and a kanban view by status
Already have
a database?
Start from it.
Point the schema importer at an existing SQL or DBML schema and get a rough-cut module — entities, views, menus, folders and roles inferred for you, your legacy data carried along. Let AI finish it, validate, and ship. You don't start from a blank file.
- 01feed it a SQL dump or a DBML file
- 02entities, views, roles and folders are inferred
- 03AI finishes the rough cut in your editor or agent
- 04validate, package, install
Pick a tool.
Start building.
Scaffold a module with the CLI, open it in your editor, or hand the whole thing to your agent. Read the docs or talk to us about a walkthrough with your team.