Agentic Infrastructure for Systems Assurance
Map dependencies across applications and services, uncover security and reliability risks, and understand the impact of changes before you make them.
Why Gdwyn
A service can pass its checks while the connection to another service still introduces risk. Gdwyn follows dependencies across applications, services, and policies, so you can see the gaps that isolated reviews miss.
Trace how APIs, SDKs, web apps, and mobile apps depend on one another.
Review potential security, reliability, and consistency issues with observations graded by criticality.
Understand affected components and relevant policies before deciding what to do next.
Understand technical risk without needing to become the CTO.
Trace dependencies, review findings, and assess changes faster.
Compare code and policies with relevant requirements.
Get a clearer view of where systems connect and where attention is needed.
Platform
Five focused components, one shared understanding of your system. Use each on its own or combine them into a workflow that fits your team.
Trace dependencies within and across codebases, from models and endpoints to the applications that use them.
Turn maps, findings, and long documents into compact facts that people and tools can reuse.
Examine code and cross-component paths through focused review modes, with findings graded by criticality.
Explore change impact, evaluate plans, and get guidance from what Gdwyn already knows about your system.
Generate a mapping script to refresh dependency facts and report potential impact on pull requests.
Observe + Facts
Observe maps how components depend on one another, even across application boundaries. Facts turns that map into compact, reusable knowledge, so you can explore a change without starting from scratch each time.
Dependency map
Follow a dependency from one component to every mapped place that relies on it.
Gdwyn facts
Reuse compact facts in reviews and conversations instead of re-reading entire repositories or standards.
Review
Examine your system through seven focused lenses. Every review returns observations in a consistent format, graded by criticality, so teams can understand findings and decide what to address first.
Trace potential security weaknesses, including risks that cross component boundaries.
Identify code patterns that may exhaust memory or retain resources unnecessarily.
Surface contradictions between system behaviour, documented expectations, and policies.
Examine how data is read, accessed, and returned, including inefficient or excessive access.
Spot potential failures involving timeouts, retries, shutdowns, and concurrent work.
Review user-facing strings, API messages, and errors for clarity and consistency.
Assess app and API experiences against relevant usability and developer-experience practices.
Example observation
Reviews read code statically and infer potential problems. They don’t run attacks or load tests, and people decide what to fix.
Assist
Assist works from the dependency maps, review findings, and fact files you’ve saved. Ask what a change might affect, where to focus first, or how a plan compares with your policies and standards, without starting from a fresh codebase read every time.
Utilities
After Gdwyn maps your codebase, a generated mapping script can update the dependency graph as your code changes. Run it in your workflow to surface affected components when a pull request is opened, without mapping everything from scratch.
The mapping script is at version 1, and its accuracy, especially for links between apps, is still improving.
Change: Transfer model updated
Potentially affected:
Review the affected paths before merging.
Standards & Policies
Bring the standards and internal policies that matter to your team into the review process. Gdwyn can compare requirements with code and with one another, surfacing potential gaps for people to evaluate and resolve.
Examples of standards and policies
Gdwyn supports reviews and audit preparation. It does not issue certifications or replace professional assessment.
Get started
Point Gdwyn at the codebases you want to understand. Start by mapping dependencies, run the reviews that matter, and use Assist to explore the results.
01
Choose the folders and services to analyse. Observe builds a dependency map from the code provided.
02
Select a review mode and relevant standards to surface potential issues.
03
Use Assist to explore impact, prioritise findings, and evaluate next steps.
Early access
Gdwyn is in early access. Request access and we’ll help you get set up.
Technical approach
Explore the approach behind Gdwyn’s static system mapping, cross-component reviews, and compact facts, and the design choices that make them work together.
Map your first set of services, explore the connections between them, and get a clearer picture of what your next change could affect.