From a file to a finished app
Three steps, no boilerplate.
Describe it once
You start with a small, readable definition of your data. No database setup, no API code, no UI scaffolding — just a description of the records you care about and the rules around them.
Watch it generate
salesOrder.entity.jsondefine
{ "naming": "SO-{####:fiscal_year}", "is_submittable": true, // docstatus + workflow "states": [draft → confirmed → delivered], "fields": [ { customer, Link→Customer }, { lines, Table[ product, qty, unit_price, line_total ] }, { grand_total, computed } ], "hooks": { computeTotals, checkCreditLimit }}Digita
POST /api/v1/resource/SalesOrderapi
{ "_id": "SO-2026-0042", // naming series "customer": "ACME GmbH", "lines": [ { Aurora Lamp, ×10, 1,490.00 }, { Cable Set, ×5, 95.00 } ], "grand_total": 1886.15, // computed "status": "confirmed", "docstatus": 1}Admin formui
ACME GmbH
ProductQtyLine total
Aurora Lamp101,490.00
Cable Set595.00
Grand total€ 1,886.15
DraftConfirmedDelivered
What happens next
1 · Define
Write a metadata file describing an entity and its fields.
2 · Generate
Digita creates the API, the database wiring and the admin screens.
3 · Publish
Mark content public and serve it as a multilingual website.