Configure the native tools.
DataWalk provides
Search, dashboards, population analysis and Link Charts.
Your team configures
The model, analysis, views and access.
Platform / Data Applications
Put the graph behind your next application.
Your model, resolved identities and calculations are already built in DataWalk. Put them to work for any team or agent: in DataWalk, inside your own application, through MCP, or in the BI tools your teams already use.
The challenge
The screen is only the surface.
A team wants a new screen, such as a supplier review or a project dashboard. Building the screen is the easy part. Underneath it, the application has to get three things right.
Who is who. When two records turn out to be the same person or supplier, the screen has to show them as one.
What the numbers say. When someone leaves a project early, every count of who worked on it has to change too.
Who can see what. The new screen has to hide the same fields the old one did.
Copy the data into each new application and your team rebuilds all three every time. Then it fixes them in every copy when something changes. In DataWalk, all three live in one place, and every application uses them.
The platform
Build as much or as little as you need.
Embed DataWalk in your application.
DataWalk provides
The Link Chart and other components, through the Embed Toolkit.
Your team builds
Where they sit in your application and how users sign in.
Build your own on the APIs.
DataWalk provides
APIs to query connected data and analytical results.
Your team builds
The interface and the workflow around it.
Give your agents the graph.
DataWalk provides
An MCP server that gives agents the model and the analytical tools, under each user’s own permissions.
Your team builds
The agent and the work it does.
Run your own code.
DataWalk provides
Python tools, notebooks and App Center processing.
Your team writes
The code, and decides which alerts start it.
Feed the tools your teams already use.
DataWalk provides
A live data source for Tableau and other BI tools, and scheduled reports.
Your team chooses
The data, who gets it and how often.
In detail
Put DataWalk in your application, or your application in DataWalk.
The Embed Toolkit puts the Link Chart and other DataWalk components inside your own web application. DataWalk JS works the other way round. Your custom components run inside DataWalk and work with its entities and views.
Teams that live in BI tools don’t have to switch. The Downstream Connector lets Tableau and other tools that speak the Postgres protocol read selected DataWalk data. Report Sender puts scheduled reports in front of the people who need them.
Every result DataWalk returns follows the access rules you set, so each team sees what it is allowed to see.
Four ways to deliver
- 1Embed ToolkitDataWalk components inside your application
- 2DataWalk JSYour components inside DataWalk
- 3Downstream ConnectorSelected DataWalk data in Tableau and other BI tools
- 4Report SenderScheduled reports to the people who need them
In practice
The next team has a starting point.
Delivery models which specialists worked for which partner, and on which project. Supplier Assurance needs the same history to review its partners. It doesn’t rebuild anything. It uses Delivery’s model under its own access rules.
Delivery builds the model.
Delivery asks which partners supplied people to the Harbor project in 2021 and 2022. Alex Morgan worked for Northstar from 2019 to 2023 and on Harbor from 2020 to 2022. Jordan Lee worked for Southbank from 2021 to 2024 and on Harbor from 2021 to 2022. Both partners count, and Delivery can see everyone’s contact details.
Delivery · Harbor contributions
| Person / partner | Employment | Harbor assignment | Source |
|---|---|---|---|
| Alex / Northstar | 2019 to 2023 | 2020 to 2022 | Employment E01 / assignment A01 |
| Jordan / Southbank | 2021 to 2024 | 2021 to 2022 | Employment E02 / assignment A02 |
Both partners supplied people to Harbor in 2021 and 2022. The names and records are illustrative.
Supplier Assurance reuses it.
Supplier Assurance embeds a Link Chart in its own review application. Its reviewers follow each partner’s people to the projects they worked on. They see the full project history, but not the contact details Delivery can see.
Same model, different access
| Team | Project history | Contacts |
|---|---|---|
| Delivery | Allowed | Allowed |
| Supplier Assurance | Allowed | Restricted |
Both teams get the same answer from the same records: Northstar and Southbank contributed in 2021 and 2022.
Changes reach the team on their own.
When an assignment enters or leaves Delivery’s saved analysis, an alert starts an App Center application your team has written. Delivery hears about the change without running the analysis again.
Alert to action
- 1The saved analysis changesAn assignment is added or removed
- 2An alert starts your applicationIt runs in App Center
- 3Your code acts on the changeIt notifies Delivery or runs your own processing
Resources
Choose your starting point.
Platform
Explore Entity Resolution
Entity Resolution.
Get the identity links your applications depend on right.
Platform
See supported analytical methods
Connected Analytics.
Develop the analytical work your applications will use.
Platform
Explore AI & Context
AI & Context.
Let agents use permitted knowledge and analytical tools.
FAQ
Questions before you build.
Do we need a custom application to use DataWalk?
No. DataWalk includes analytical interfaces, search, dashboards and configurable alerts. Custom development is an option when your workflow needs another experience or integration.
Is App Center an end-user application builder?
App Center runs configured extensions and processing jobs. An end-user application can use DataWalk’s native interfaces, embedded components or a custom interface built through the APIs.
How does an embedded Link Chart authenticate?
The component authenticates as an existing DataWalk user, using credentials or SAML. Your team must implement and test the authentication flow in the host application.
Can any application run from an alert?
Only an active application configured for alert triggers can be selected. The alert can pass added or removed objects for processing. The application and its output handling still need to be configured. Delivery and error handling are part of the integration design.
Who governs data once it leaves DataWalk?
DataWalk applies your access rules to every result it returns. Once data is exported to a BI tool or a report, the receiving system governs its copy. Agree the fields, access and retention for each route before you go live.
What does our team remain responsible for?
Your team defines the model and analytical logic, then configures or builds the interface. For custom applications, it also owns integration, authentication and deployment.
Does custom code always run inside the database?
No. Processing can use DataWalk’s engine, App Center applications or external services, depending on the implementation. Design data access and movement for the route you choose.
Show us the workflow you want to change.
We’ll work out with you what to configure, what to embed and what to build.
Plan an application review
- Bring
- Bring one workflow your team wants to change, and the data behind it.
- Choose
- We pick the route with you: native, embedded, API or BI.
- Test
- We test it with your users, your access rules and your response times.
- Leave with
- You leave with a plan that names what you configure, what you embed and what you build.
