Foundry — home

Foundry Intelligence

Answers about your software, with the evidence attached.

Tell us the system and the decision in front of you. We analyze it, test what we find, and hand back a defined set of deliverables. We operate Foundry, so there is nothing for you to install or run. Clear scope, not open-ended consulting.

Tell us about your system

foundry-analysis/what you get

Example package
  • behavior-report.pdfWhat the system does, finding by finding, with evidence states
  • interfaces.openapi.yamlReconstructed interface specification
  • dependency-map.svgWhat calls what, and what depends on it
  • conformance-tests/Runnable tests that prove each verified finding
  • limitations.mdWhat we could not confirm, and why
  • next-steps.mdRecommendations for the decision you scoped

Every finding carries its evidence

  • Verified
  • Observed
  • Inferred
  • Open
A typical package your engineers can use the same day — not a slide deck. Contents are agreed during scoping.

How an engagement runs.

  1. Scope

    You bring
    The system, the decision it supports, what we may access
    We do
    Objective, authorized target, success criteria, data-handling terms
  2. Analyze

    You bring
    Access as agreed, a contact for questions
    We do
    Discovery of behavior, interfaces and dependencies
  3. Verify

    You bring
    Nothing, unless a finding needs your judgment
    We do
    Tests against the running system; every finding gets an evidence state
  4. Deliver

    You bring
    A review session with your team
    We do
    The agreed package, known limitations, recommended next steps

Where teams usually start.

Make the next engineering decision with better information.

What changes afterwards. Outcomes, not promised percentages.

Then keep it current.

Systems change. When yours does, we re-run the analysis, flag what moved, and re-test what you rely on. A subscription instead of a new project every time.

Change reportorder-service

Example
  • ChangedRetry window: 24h → 1h
  • NewEndpoint /v2/orders/bulk
  • Unchanged12 behaviors re-verified

When the work has to stay inside your environment.

A Controlled Environment Engagement adds the controls the work genuinely needs. Whether work can run inside your environment, and exactly which data flows that leaves, is confirmed during scoping before we commit to it.

  • Analysis inside infrastructure you control

  • Restricted network connectivity

  • Additional access controls and audit evidence

  • Special retention, deletion or artifact-handling procedures

  • Dedicated deployment, validation or support arrangements

We price the delivery complexity, risk and support it adds. Operating in a regulated industry is not, on its own, a reason to pay more. How it is priced

Before we start.

What do you need to understand?