Product
Architecture needs a source of truth.
Veriom reconstructs how your code, cloud and delivery fit together, assesses the design with specialist agents and shows the evidence behind each conclusion. Your team decides what changes.
Architecture map
A living map of the whole system.
Code, infrastructure as code and cloud resolve into one map of services, data and dependencies, grouped by the boundaries they sit in and rebuilt at every audit.

Code, cloud and infrastructure records resolve into one map of a sample orders system: an API, its database, an event bus, queues and workers. The map groups services by boundary, updates itself when a pull request merges and a deployment succeeds, and answers which resources a service connects to.
01Model
Every relationship keeps its provenance and history.
See where a relationship was observed, what confirmed it and what changed, so the model can be questioned instead of trusted blindly.
payments-api → card-vault
RDS · Postgres0.9123 October
Observed in src/clients/vault.ts:22, at 0.72 confidence
EV-2041 · payments-api
30 October
Confirmed by the security group's egress rule
EV-2043 · AWS
30 October
Deployed with that group by the release workflow
EV-2050 · GitHub Actions
02Evidence
Confidence is earned, and contradictions stay visible.
Independent evidence raises confidence; a source that disagrees is shown beside the claim, not averaged away.
payments-api reaches card-vault outside the egress policy
- Confidence
- 0.91
- Reviewed by
- Security Architect
- Owner
- Payments team
- EV-2041The vault client is created with the card-vault endpoint.payments-api · src/clients/vault.ts:22
- EV-2043Egress allows 0.0.0.0/0 on 443, wider than the policy.AWS · security group sg-payments egress
- EV-2050The release workflow deploys payments-api with that group.platform-infra · deploy/payments.yml:31
- EV-2056Architecture decision record says egress goes through the proxyContradicts EV-2043payments-api · docs/adr/0031-egress.md
03Action
A fix opens as a draft only once it is approved.
Agents prepare a patch with the evidence it cites and rescan it. A reviewer, or a policy your admins turn on, approves the draft pull request within the limits they set; your team merges it, and the next audit checks the merged code.
Restrict payments-api egress to the card vault
Awaiting approvalPrepared by the remediation engineer from F-118 · Owner: Payments team
northstar/platform-infra · infra/payments/security.tf
resource "aws_vpc_security_group_egress_rule" "payments_https" { security_group_id = aws_security_group.payments.id ip_protocol = "tcp" from_port = 443 to_port = 443 - cidr_ipv4 = "0.0.0.0/0"+ referenced_security_group_id = aws_security_group.card_vault.id }After approval it opens draft pull request #318. Your team merges it on GitHub, and the next audit checks that F-118 is gone.
Review at every audit
See what deserves attention, and what to do next.
Audits run weekly and when the default branch changes. Specialist agents review the map with its evidence, explain why a finding matters and propose a fix that opens as a draft only once it is approved.

Veriom reviews a sample payments system from four evidence sources, highlights that a public API and a background worker share one runtime identity that can read transaction data, and proposes separate identities for each workload, marked as proposed and not applied.
Evidence flow
Watch an observation become a reviewable relationship.
Choose a source to see what was observed, how independent evidence converges, and why the claim earns its confidence.
- 01Observedcheckout-web registers a route that calls payments-api.
- 02CorroboratedThe imported client and the route registration name the same service.
- 03Reconciledcheckout-web calls payments-api
Specialist agents
A review team that cites its sources.
Each specialist works on the same model and returns a typed artifact with the evidence it relied on. Merging, accepting risk and attesting a report always need a person.

- 01ScopeA repository, branch and audit profile set what the run can see.
- 02CollectCollectors read code, cloud and delivery evidence without changing it.
- 03ReconcileThe model takes the new evidence, and the run records what changed since the last audit.
- 04ReviewSpecialist agents review the updated model, each citing its evidence.
- 05ReportFindings land in the queue, and the report waits for a person to approve it.
- 06RepeatSchedules and repository events start the next run, so drift shows up as a change.
Architecture
Keeps the system model and its boundaries current.
Security
Finds weaknesses and explains their reach.
Evidence
Validates sources and records provenance.
Threat
Models how the system could be attacked.
Diagram
Draws the current architecture from the model.
Remediation
Prepares fixes as typed proposals.
Reporting
Writes the review your stakeholders read.
You
Approve, change or refuse what they prepare.
Veriom MCP
Your assistant works in Veriom. Decisions stay with you.
Coding and chat assistants read findings, run audits and request fixes as the person who connected them. Evidence they send stays evidence, never instructions, and approving a fix stays in the app.

kind: relationship
source: deployment-manifest
entity: service.checkout-web
relationship: calls
target: service.payments-api
observed_at: 2026-10-30T09:18:00Z
workspace: ws_8f2cValidated, timestamped and scoped to one workspace before it reaches the model.
See your own system in the model.
Connect a repository and a cloud account, and review the first findings with your team.

