PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopersSENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse casesSOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →THE MECHANISM
One definition, every surface.
An entity is defined once — fields, formulas, validations. Every screen, view and API is generated from that single definition, so nothing drifts.
Web formGENERATED
Outlet name
Delivery window ▾
List & Kanban viewsGENERATED
ENTITY DEFINITION · OUTLET
nametext · required
delivery_windowpicklist · global
credit_okformula = used < limit
validationphone must be 10 digits
saved → REST & OData endpoints exist
Native mobile screenGENERATED
native · offline sync
REST / OData responseGENERATED
GET /odata/outlets
{ "name": "Apex Mart",
"delivery_window": "Thu AM" }
{ "name": "Apex Mart",
"delivery_window": "Thu AM" }
OVER THE AIRLayout change saved⇢Rep's phone — updatedlayout changes ship without an app-store release
HOW IT WORKS
Model→Design→Preview→Publish
01 · IN DEPTH
From data model to running app.
DATA MODEL
Fields that actually do things
Currency, geo-location, formulas and calculated fields, dependent and global picklists, lookups with filters — plus record types and validation rules. Every entity is API-first from the moment you save it.
TWO DESIGNERS, ONE DEFINITION
Web and mobile, never drifting
A dedicated designer for web layouts and another for native mobile screens — because a phone in the field is not a desktop. Layout changes reach devices over the air, no app-store release.
WHOLE APPS, NOT JUST FORMS
Compose the app your team opens
Navigation, home pages with KPI widgets, role-scoped pages, cards and list views — assembled from 100+ prebuilt widgets, or your own custom components.
FOR THE EVALUATORS
For the people who will actually build on it.
The details an RFP answer needs — all verifiable in a demo.
RICH FIELD TYPES
Currency, geo-location, cron, formula and calculated fields, dependent and global picklists, and lookups with filters — modelled, not coded.
RECORD TYPES & VALIDATION
Record types give one entity several shapes; validation rules run server-side on every write.
WEB + MOBILE DESIGNERS
Separate designers for web and native mobile, generated from the same definition — parity is enforced, not hoped for.
WIDGET LIBRARY
100+ prebuilt widgets, plus custom React components where they earn their place.
APP COMPOSITION
Apps compose from navigation, role-scoped pages and KPI widgets — a whole product, not a pile of forms.
INSTANT APIS
Every entity gets REST and OData endpoints the moment it is saved.
GLOBAL BY CONFIGURATION
One application, every audience.
Rename the business language per tenant — your “outlets”, their “counters” — localize labels without waiting on a release, brand each app as its own, and let every surface follow light or dark mode.
TENANT LOCALIZATION
Your words, per tenant
Labels and business language are tenant-managed resources — override them without waiting on a release.
PER-APP BRANDING
Every app its own identity
Logos, visual configuration and branded mobile builds — each application carries its own face.
LIGHT & DARK
Both modes, everywhere
One theme system across the application — every surface follows the choice.
FEATURE HIGHLIGHTS
Everything in App Builder.
Custom entities & fields
Your objects, first-class.
Model outlets, schemes, claims — anything — with the same depth the built-in entities get. Each is API-ready on save.
Formula & calculated fields
Fields that compute themselves.
Derive values server-side — margins, ratios, flags — so every screen and report shows the same answer.
Record types
One entity, several shapes.
A retail outlet and a wholesale outlet can share data but differ in layout, picklists and process.
Validation rules
Bad data stops at the door.
Declared once, enforced on every write — web, mobile, API and import alike.
Global & dependent picklists
Choices that stay consistent.
Shared value sets across entities, and picklists that narrow based on a previous answer.
Web layout designer
Forms without a frontend team.
Drag-and-drop layouts with sections, related lists and conditional visibility.
Mobile layout designer
Designed for thumbs, not shrunk.
A dedicated designer for native mobile screens — because the field is not a desktop.
Card & list-view designer
Lists that carry meaning.
Design list, card and Kanban views per entity — what a rep scans first is a decision, not a default.
App composition
Whole apps, assembled.
Navigation, role-scoped pages and KPI widgets compose into an app users log into — not a pile of forms.
Instant APIs per entity
Integration-ready by default.
REST and OData endpoints exist the moment an entity is saved. No API project.
100+ widget library
A running start on every page.
Charts, KPIs, lists, timelines and more — prebuilt, themeable, extendable with custom React components.
Over-the-air layout delivery
Ship a change at lunch.
Layout changes reach every device without an app-store release or a reinstall.