What Smart Data Studio does (and what you own)

Smart Data Studio is the WFX integration and data-distribution layer. It manages the logic of working with WFX for you, and it makes that logic easy to build, maintain and trust. It is deliberately not a general integration-platform-as-a-service, and this page explains exactly where the lines are drawn so there are no surprises.

What Smart Data Studio does

• Discovers the fields WFX can give you (schema discovery).
• Patches correctly back into WFX (the right payload shape, signing, rate limits, safe-update rules).
• Handles versions and lifecycle.
• Builds automations in and out of WFX (Smart Fields, reference data, feeds).
• Keeps proper, provable logs of what happened.
• Provides a managed connector into id.codes.

Think of it as the equivalent of writing code directly against the WFX API, but made far easier to build, maintain and reason about.

What we are responsible for

Interacting with WFX correctly, on your behalf: correct calls, correct mapping, correct patching, and idempotent delivery (we do not re-send unchanged data). We also keep a timestamped, checksummed record of what we sent and what WFX returned.

What you are responsible for

Ingestion. On the outbound side we support two shapes:

1. A pull feed you consume on your own schedule.
2. Delivery to a single endpoint you control.

Routing that data into your systems and tables is owned by your team. We deliver correct data, at the right time, to one location. What happens after that delivery is your side.

Where the data comes from

We call the WFX API and pass on the data WFX returns, changed only by the mapping you configure. WFX is the system of record for the data itself; our job is to call it correctly and deliver it faithfully. To keep that fully transparent, we record a timestamped, checksummed copy of exactly what WFX returned for every run and every record, so the flow is auditable end to end.

What we do not do

• We do not write into your database.
• We do not manage delivery across multiple systems or endpoints, and we do not guarantee a payload lands in the correct table on your side.

If you need per-system or per-table updates, either pull from our feed and route on your side, or receive at one endpoint and route on your side. (id.codes is the one exception: it is our partner system, so we own that ingestion.)