Skip to content

Turn device events into a collaborative child-safety workflow.

MTFDX Platform connects families, institutions and third-party devices with unified identity, authorization, Handover, Safety Event, Notification and Audit.

Layered architecture diagram for Hero (MTFDX original candidate illustration, project-owned)
Layered architecture diagram for Core objects (MTFDX original candidate illustration, project-owned)

Unify the objects first, then the workflows.

01

Family

02

Child

03

Adult

04

Authorization

05

Handover

06

SafetyEvent

Layered architecture diagram for Event standard (MTFDX original candidate illustration, project-owned)

Upstream services don't need to know the device brand.

Device eventNormalizationSafetyEventRulesFamily / Institution
Layered architecture diagram for API capabilities (MTFDX original candidate illustration, project-owned)

Open capabilities around authorization, Handover, Safety Event, notification and audit.

Demo · synthetic data only

Auth & scoped token
Auth & scoped token
Authorization
Authorization
Handover
Handover
Safety Event
Safety Event
Notification/Webhook
Notification/Webhook
Audit
Audit

Reliable delivery, without guessing state through client polling.

Production must include signature verification, idempotency, retries and dead-letter handling; documentation pages show only non-sensitive examples.

  • Signature verification
  • Idempotency & retry
  • Dead-letter handling
Safety Core and partner-device diagram for Webhook (MTFDX original candidate illustration, project-owned)
Layered architecture diagram for Region (MTFDX original candidate illustration, project-owned)

A single product core does not mean children's sensitive data is centralized across borders by default.

Demo · synthetic data only

Japan data plane
Japan data plane
China data plane
China data plane
Original illustration for Developer CTA (an adult and child scene) (MTFDX original candidate illustration, project-owned)

Start integrating with a test event.