Relay
Connect source systems, webhooks, APIs, files, and operational tools to the workflow without creating unmanaged action paths.
- ERP and CRM context
- Webhook intake
- Scoped connections
Capability
Relay
connect systems safely
Yedron connects enterprise systems and data through the operating loop: source systems become events, business context, decision options, approvals, actions, and audit evidence.
Connected context
Keep each source in its place.
Yedron uses relevant records to assemble the context for one decision, while the source systems remain responsible for their own data.
- Signal
- A carrier update reports a new arrival time.
- Sources
- Transport, order, inventory, and customer systems.
- Context
- A linked delivery commitment and available alternatives.
- Writeback
- Only an approved action reaches the target system.
Illustrative workflow view. Controls and integrations depend on deployment.
Strata: the separate data plane
Strata governs datasets, data posture, preparation, feature snapshots, training inputs, access, and lineage. Relay provides the connection; Strata provides the governed data plane.
- Governed dataset catalog
- Feature and training snapshots
- Integrate-only, hybrid, and hosted posture
Operating events
Important changes become durable operating events so teams can see what changed, why it mattered, and how the workflow responded.
- Event requests
- Durable history
- Replayable context
In practice
Bring the relevant systems into one workflow.
Integration begins with an operating need: which event opens the work, which records explain it, and which target can receive an approved response.
Order and delivery coordination
Link transport events to order, inventory, and customer records. Give the delivery exception a connected context while each source system retains its own responsibility.
Production and maintenance
Connect equipment events and production records to a review workflow. Identify the evidence and target work-order action needed to coordinate an approved response.
Service operations
Bring case, account, and operational updates together for a handoff. Keep the source event, proposed response, and approved target change traceable across the systems involved.
How it works
Define the read path and the action path.
A connection should have an owner and a purpose. The first workflow establishes the access, mapping, and failure handling required at each system boundary.
- 01
Map the sources
Identify the relevant APIs, events, documents, or files. Define account scope, record identity, and how each source contributes to the selected decision.
- 02
Govern the context
Use Relay for connection and transport, Strata for datasets and lineage, and Lattice for accepted operating relationships. Keep those responsibilities explicit.
- 03
Validate the response path
Define the allowed writeback and required authority. Test rejected requests, unavailable targets, and review paths as part of readiness for the workflow.
Common questions
Understand the fit.
Does integration mean copying every source record?
No. Begin with the information needed for the operating purpose. The agreed data posture determines what is accessed, processed, or retained for that workflow.
What should an integration owner define?
Source identity, permitted access, event mapping, target actions, credential responsibility, and failure handling. These boundaries should be agreed before the workflow relies on the connection.
Can a source event trigger an unrestricted writeback?
No. The incoming event provides context. Policy, Workflow, and Praxis establish and execute the authorized response through the scoped target connection.
Explore further
See the connected platform.
Start where one workflow needs clearer control.
Adoption starts with one workflow, the systems around it, the approvals it needs, and the outcome your team wants to improve.
Design a decision loop