Ship your domain.
Skip the plumbing.
You're building a domain-specific B2B platform — and 80% of it is the same multi-tenant, auth, RBAC, CRUD, API plumbing every SaaS rebuilds. dForge gives you that foundation as metadata so you spend your time on the part only you can build.
Your domain
The workflows, rules, and product only you can build.
The foundation, as metadata
If any of this is on your plate, you're in the right place.
Three things you don't have to build.
The hard infrastructure is solved before you start — so your first commit is product, not plumbing.
Model your domain in metadata
Describe entities, views, roles, and actions — to AI or by hand. The runtime turns that description into a working multi-user app with a JSON-RPC API, out of the box.
- Change the model and the schema follows — no migrations to hand-write.
- Every entity ships with CRUD, validation, and a typed API automatically.
- Draft it with AI, then refine it like code.
True isolation, built in
One database per tenant from day one. Each customer's data lives in its own database — no shared tables, and no cross-tenant query is even possible. Row- and column-level security and a full audit trail sit on top.
- One database per tenant — the security boundary is the database itself.
- Composable row- and column-level security, per role.
- Full audit on every change.
Self-host or white-label
Run on your own infrastructure, bring your own Postgres, and put your brand on it. Your customers never see dForge. When you need hard separation, spin up per-customer instances.
- Your domain, your logo, your login screen.
- Bring your own Postgres; deploy with Docker on your infra.
- Export your metadata to version control — it's yours.
Modules worth installing first for this.
Sales CRM: contacts, leads, opportunities, quotes, activities, and product catalog. Customer identity lives in the shared parties module; CRM-specific columns (industry, credit limit, account manager) are layered on as an extension.
Shared customer & vendor directory — the identity layer fin, crm, and hr build on. One entity, role flags (is_customer / is_vendor), structured address that satisfies invoicing standards like Swiss QR-bill.
Tell us what you need and we'll build the module — or book a call to map your systems together.
See who else builds on dForge.
Monday, Zoho or HubSpot stopped fitting
Aging Access, FoxPro or custom ERP
CIOs under pressure to deliver more, faster
Simplify operations on one governed model
Run ops behind Shopify or WooCommerce
Small companies with no developer on staff
Department managers waiting on central IT
Consultancies & systems integrators