// metadata-driven business platform

Define your
business.
Ship the app.

dForge turns business definitions into production-ready apps — real database schemas, real APIs, real UI, real security. Pick a module from the catalog or build your own with AI.

lead.module ● live
entity Lead {
  name        string  required
  email       email   unique
  company     string
  stage       enum    [new, qualified, won, lost]
  owner       ref     User
  value       money
  created_at  datetime auto
}

view  LeadPipeline  kanban  by stage
role  SalesRep      can: read, update.own
role  SalesManager  can: read, update, delete
dforge build
Lead pipeline
new
qualified
won
lost
// running in production Sales CRM ·HR ·Finance ·Warehouse ·Pricing ·AI Authoring
/ 01 · the problem
20%

of building business software is actual business logic. The other 80% is auth, permissions, CRUD, deployment, migrations, audit logs — the same plumbing rebuilt every time.

~/typical-enterprise-stack 3 errors
  • 01
    Tool sprawl
    Every department picks its own SaaS. Data lives in silos. The "single view" is a CSV stitched in Excel.
  • 02
    Legacy gravity
    Critical processes run on aging software nobody wants to touch. Migration is risky, expensive, and never-ending.
  • 03
    Custom dev tax
    Building from scratch means months of plumbing before you write a single line of business logic.
/ 02 · how it works

You describe what.
dForge handles how.

lead.module entity Lead { name string stage enum owner ref value money } // metadata · the source of truth dForge runtime compiles · no codegen Database postgres · per-tenant APIs JSON-RPC Generated UI list · form · kanban Security row + column rules
step 01
define
entity Customer {
name string
tier enum [free, pro]
mrr money
}

Describe your module to an AI assistant — or write JSON metadata by hand. Entities, fields, views, roles, actions — the shape of your business.

step 02
generate
› dforge build lead.module
✓ schema · 8 fields, 2 indexes
✓ api · JSON-RPC
✓ ui · list · form · kanban
✓ rls · row-level security applied
✓ audit · history enabled
› deployed → tenant: acme.dforge.app

dForge produces the database schema, a JSON-RPC API, list/form/kanban UI, and row-level security automatically.

step 03
ship
acme.dforge.app

A real multi-tenant app on its own subdomain — branded, secured, observable. Update metadata, redeploy in seconds.

/ 05 · ai-native

Metadata,
not code.
That changes
everything.

Other platforms ask AI to write code — brittle, hard to maintain, hard to validate. dForge asks AI to write metadata : structured business definitions the platform turns into real apps. Run npx @dforge/create-module, open in Claude Code, describe what you need. Reviewable. Versionable. Safe to deploy.

dforge · ask claude-opus
→  "I need to track customer support tickets
   with priority, status, assignee, and SLA timer"

←  entity Ticket {
     subject    string  required
     priority   enum    [low, normal, high, urgent]
     status     enum    [open, pending, resolved]
     assignee   ref     User
     opened_at  datetime auto
     sla_due    datetime computed
   }
create
modules from conversation
import
from SQL / DBML schemas
validate
& package locally
/ 06 · for whom

Built for the people who decide,
build, and use it.

I
For CIOs

Consolidate scattered SaaS into one platform. Cut vendor lock-in. Visibility across every business app.

II
For IT Teams

Migrate legacy systems incrementally. Ship one module at a time. Self-hosted or cloud — your call.

III
For Builders

Skip the plumbing. Define metadata, get a full app with UI, API, and security. Days, not months.

IV
For End Users

One consistent surface for CRM, HR, Finance, WMS. Stop switching between five different tools.

/ 07 · ready when you are

Stop plumbing.
Start shipping.

Spin up a workspace on dforge.app or talk to us about a personalized demo for your team.

questions? → platform@dforge.io