UDF.one · v3.0scroll to compose
progress 0%72 records · 6 primitives
scroll
UDF.one · The Enterprise Reality Platform

Your reality,
computable.

Six primitives. One graph.
Every record from every system, classified into the six things a business actually contains, connected into one graph. Evidence behind every decision. Agents behind every action.
In production since April 2026 · 3,800+ order deliveries · customs-grade reports

In every enterprise, the same thing exists in fifty places. A customer in the CRM. A debtor in finance. A user in operations. A signature on a paper contract, each shaped by the system that holds it, each speaking a different dialect.

We've spent two decades writing translators between them. We call them integrations, mappings, ETL, master data management, canonical models. None of them survive past two systems. They rot the moment something new connects.

The translator approach is finished. There is a different path: don't model. classify.

UDF.one holds that everything in the enterprise is one of Location, Entity, Asset, Product, Event, or Document. No more. No less. Six fundamentals, what the world actually contains.

Every record from every system is given a primitive, and becomes a node in one centralised graph. Queryable by humans, BI, agents, anything that asks.

§ 03 · Try itWatch UDF.one think.

A record arrives. UDF.one reads it. One of six primitives lights up. That's the entire product.
Input · raw recordClassifier online
Generator unit G-2204, last serviced 18 February 2026Invoice 2026-04832, Acme Logistics, €18,420.00Hans de Waal, Founder, Arero7Sensor alert: bearing temp exceeded 92°C at 14:32UDF.one rollout, 12-week engagementArero7 office, Silicon Wal, Ossendrecht
to classify
Output · primitive resolutionAwaiting input
Six primitives await. The classification will land on one.
, A record will appear here, classified into one of six.,
§ 04 · The six

Everything is one of six.

The premise is simple. Believing it is the work. Once accepted, the data layer collapses, every record in every system fits exactly one primitive, and every primitive carries shape, behaviour, and a place in the graph.

01 · L

Location.

Where it is. Anywhere with a coordinate, address, region, route, or geofence, physical or virtual.

A warehouse in Rotterdam. A region in AWS. Both, location.
In SAPPlant / Storage locationIn SalesforceAccount.BillingAddressIn UDF.oneJust a Location.
02 · E

Entity.

Who or what acts. People, organisations, agents, departments, customers, anything that holds a role.

A customer. A maintenance team. An autonomous agent. Same shape.
In SAPBP / Customer / VendorIn SalesforceContact / AccountIn UDF.oneJust an Entity.
03 · A

Asset.

What persists. Machines, buildings, accounts, inventory, code, IP, anything that has state.

A production unit. A balance sheet. A Salesforce instance. All assets.
In SAPEquipment / MaterialIn SalesforceAsset / ProductIn UDF.oneJust an Asset.
04 · P

Product.

What is offered. Services, goods, plans, subscriptions, contracts, value exchanged with the world.

An enterprise license. A premium subscription. Both, product.
In SAPMaterial / ServiceIn SalesforceProduct2 / PriceBookEntryIn UDF.oneJust a Product.
05 · Ev

Event.

When something happens. The connective tissue. An order, a delay, a payment, a query, a delivery.

An order ships. A sensor fires. A change of state.
In SAPIDoc / Application LogIn SalesforceActivity / EventLogIn UDF.oneJust an Event.
06 · D

Document.

What is recorded. Invoices, contracts, manuals, emails, tickets, runbooks, the artefacts of business.

An invoice. A maintenance manual. The signed PDF.
In SAPDocument / AttachmentIn SalesforceContentDocumentIn UDF.oneJust a Document.
§ 05 · Graph

Six points.
One graph.

Once classified, a record finds its place. Connections form between what was scattered. Queries traverse the graph, not the systems.

"Where is unit 4019, who serviced it last, and which document covers it?" Three primitives, one query, no joins.

§ 06 · Compared

What UDF.one isn't.

01
ETL & ELT: copy data between systems, maintain the pipelines, break on every schema change.
Fragile · expensive
02
Canonical models: one enterprise data model, hundreds of objects, redesign on every new system. Rarely finished.
Brittle · slow
03
Vector databases: embed everything, hope similarity is enough. Semantic but unstructured. Without grounding, agents drift.
Lossy · ungrounded
04
UDF.one: classify into six. One centralised graph. Adding a new system means classifying its records, not re-architecting.
Stable · governed
§ 07 · The company

Built and run by Arero7.

Arero7 is the parent. Advisory and build for the intelligent enterprise. Counsel for leadership, architecture for what's missing, products on a single foundation. UDF.one is the first.

One company, one product: Arero7 builds and runs UDF.one. The grammar of six beneath it and the AI layer on top ship inside the product, not as brands beside it.

Where tech adds value
ARERO7
PracticeAdvisory · Build · Delivery
MissionFrom digital to intelligent
MethodOne layer. One voice.
arero7.com →Ossendrecht · 2024

§ 08 · How it worksSix steps.
Your data
AI-ready.

From raw evidence to one living world model, and back to any document, any answer.
01
Connect
Link your systems (WMS, ERP, CRM) and drop in everything you have, exports, emails, PDFs. It’s all evidence; nothing has to be “clean” first.
02
Unfold
Pack-driven, the platform classifies everything into the six primitives (Location, Entity, Asset, Product, Event, Document). One customer, one container, one order, each exists exactly once.
03
Anchor
Domains, departments, value streams and access rules, who sees what. Governance lives inside the model, not a separate document.
04
Flow
Delivery-guaranteed flows: partner files arrive, are understood, mapped and delivered, on a ledger where nothing silently disappears.
05
Infold
Reports, BI and customs audit files come straight from the model (infold): the same truth, in every format.
06
Converse
The AI agent stands on the world graph and answers traceably, every answer points back to the evidence it came from.
One model · Six steps · Evidence in, answers out
Get access

The intelligent enterprise starts here.

UDF.one, Unified Data Field, by Arero7