Agentic Infrastructure for Systems Assurance

The harness for understanding your entire system

Map dependencies across applications and services, uncover security and reliability risks, and understand the impact of changes before you make them.

Request accessSee how it works
gdwyn

$ gdwyn observe --mode map ./api ./web ./mobile

✓ Mapped 3 apps and 2 services

✓ Fact graph saved

$ gdwyn review --mode consistency

high create transfer → transfers → ledger

No idempotency key: a retried request could create a duplicate transfer.

$ gdwyn assist

› What calls create transfer?

gdwyn Web checkout and mobile send-money, via the SDK.

Why Gdwyn

The biggest risks aren’t always inside the code.

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.

See beyond individual components

Trace how APIs, SDKs, web apps, and mobile apps depend on one another.

Find what deserves attention

Review potential security, reliability, and consistency issues with observations graded by criticality.

Make changes with more context

Understand affected components and relevant policies before deciding what to do next.

Built for everyone responsible for a system

Founders

Understand technical risk without needing to become the CTO.

Engineers

Trace dependencies, review findings, and assess changes faster.

Risk and compliance teams

Compare code and policies with relevant requirements.

Technical leaders

Get a clearer view of where systems connect and where attention is needed.

ObserveFactsReviewAssistUtilitiesYOURSystem

Platform

Modular by design

Five focused components, one shared understanding of your system. Use each on its own or combine them into a workflow that fits your team.

  1. 01

    Observe · Map how your system connects.

    Trace dependencies within and across codebases, from models and endpoints to the applications that use them.

  2. 02

    Facts · Keep the important context.

    Turn maps, findings, and long documents into compact facts that people and tools can reuse.

  3. 03

    Review · Find risks across the system.

    Examine code and cross-component paths through focused review modes, with findings graded by criticality.

  4. 04

    Assist · Ask questions with context.

    Explore change impact, evaluate plans, and get guidance from what Gdwyn already knows about your system.

  5. 05

    Utilities · Keep your map useful as code changes.

    Generate a mapping script to refresh dependency facts and report potential impact on pull requests.

Observe + Facts

See every connection you can trace. Keep the facts that matter.

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

Transfer modelAPI endpoints: create transfer, get transferSDK: transfers.create, transfers.get
Web app: checkoutMobile app: send money

Follow a dependency from one component to every mapped place that relies on it.

Gdwyn facts

model.Transferused_by api/transfers (5 files)
api.createTransferexposes Transfer
api.getTransferexposes Transfer
sdk.transfers.*calls api.createTransfer, api.getTransfer
web.checkoutcalls sdk.transfers.create
mobile.sendMoneycalls sdk.transfers.create

Reuse compact facts in reviews and conversations instead of re-reading entire repositories or standards.

Review

Seven modes. One schema.

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.

Security

Trace potential security weaknesses, including risks that cross component boundaries.

Memory

Identify code patterns that may exhaust memory or retain resources unnecessarily.

Consistency

Surface contradictions between system behaviour, documented expectations, and policies.

Query

Examine how data is read, accessed, and returned, including inefficient or excessive access.

Resilience

Spot potential failures involving timeouts, retries, shutdowns, and concurrent work.

Copy

Review user-facing strings, API messages, and errors for clarity and consistency.

UI/UX

Assess app and API experiences against relevant usability and developer-experience practices.

Example observation

criticalityhigh
modeconsistency
pathcreate transfer → transfers → ledger
reasoningTransfers are meant to happen once, but no idempotency key or unique index was found.
next stepConfirm duplicate handling; consider an idempotency key on create transfer.

Reviews read code statically and infer potential problems. They don’t run attacks or load tests, and people decide what to fix.

Assist

Ask better questions about your system.

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.

  • “What would adding this field affect?”
  • “Which high-criticality findings should we review first?”
  • “Does this proposed workflow conflict with our 2FA policy?”
  • “Which apps depend on this endpoint?”
Gdwyn Assist
What would adding a currency field to Transfer affect?
Based on the mapped files, Transfer is used by two endpoints, create transfer and get transfer. Both are exposed in the SDK and called by the web checkout and the mobile send-money flow. Reporting also reads Transfer, so its totals may need to group by currency.
Does it conflict with our 2FA policy?
Your saved policy facts say every withdrawal needs 2FA. Adding a field doesn’t change that path. It’s worth running a consistency review once the change is drafted.

Utilities

Know what a pull request could affect.

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.

Example impact report

Change: Transfer model updated

Potentially affected:

  • Transfer API endpoints
  • SDK methods using those endpoints
  • Web and mobile flows that call them

Review the affected paths before merging.

Standards & Policies

Understand how your system measures up.

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

PCI DSSISO 27001SOC 2GDPRNDPACBN Risk-Based Cybersecurity FrameworkCBN Consumer Protection RegulationsInternal policies

Gdwyn supports reviews and audit preparation. It does not issue certifications or replace professional assessment.

Get started

Start with your code. Build understanding from there.

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.

  1. 01

    Map your system

    Choose the folders and services to analyse. Observe builds a dependency map from the code provided.

  2. 02

    Review what matters

    Select a review mode and relevant standards to surface potential issues.

  3. 03

    Ask with context

    Use Assist to explore impact, prioritise findings, and evaluate next steps.

Early access

Map your first set of services with us.

Gdwyn is in early access. Request access and we’ll help you get set up.

Technical approach

Go deeper into how Gdwyn works.

Explore the approach behind Gdwyn’s static system mapping, cross-component reviews, and compact facts, and the design choices that make them work together.

White paper coming soon

Start seeing the whole system.

Map your first set of services, explore the connections between them, and get a clearer picture of what your next change could affect.

Request accessSee how it works