The Position

The Manifesto.

Every codebase has a hidden story. About risks, about quality, about the secrets of and in the code — and what if your most important developer leaves right now?!

We analyze and understand your software within one week and tell you the honest, clear and complete story — written from the code itself. We point out the strengths and weaknesses of the source code — we hide nothing.

Theme 01/05

Legacy code is unread.

A million lines, written over 15 years, by teams that no longer exist. No one reads it. Everyone depends on it. That’s the risk we make visible.

The reality
Nobody knows
  • The people who built it left years ago
  • Onboarding takes quarters, not weeks
  • Tribal knowledge — fragile, irreplaceable, undocumented
The risk
Invisible liability
  • 100K–1M+ lines — no one owns the full overview and insight
  • Security gaps, architectural drift, hidden coupling
  • One resignation from a crisis
MarQed.ai
We read it
  • Our scanners — every line, every dependency
  • Digital Twin of your codebase — live, queryable
  • The hidden story, told back to everyone
Theme 02/05

Verification is half the work. Comprehension is the other half.

Automated pipelines invest in verifying what agents wrote. We invest in understanding what already exists — before anyone, human or agent, changes it.

What they verify
Output correctness
  • Tests, linters, type checks, sandboxes
  • Did the agent build the right thing?
  • Loop closes at the PR
What we surface
System comprehension
  • Architecture, coupling, complexity, drift
  • What did we just buy — and what does it cost to keep?
  • Loop closes at the boardroom
Why both matter
Two timescales
  • Agent verification: this sprint
  • Software intelligence: the next ten years
  • You need both. We do the second.
Theme 03/05

The audit survives the agent.

Regulators don’t care which agent wrote the code. They care who decided, who approved, and what was known. We make that traceable.

The agent’s view
Stateless execution
  • Each session: prompt → diff → forget
  • No memory of why across sessions
  • Compliance burden falls back on humans
The regulator’s view
Lasting accountability
  • NEN 7510, NIS2, AVG, ISO 25010
  • Sovereign by design — data stays in your perimeter
  • Every decision audit-traced, not just every commit
Our position
The memory layer
  • Decision provenance — who, when, why
  • Local-first runtime — runs in your data center
  • Built for any codebase. Built to last.
Theme 04/05

One platform. Three audiences.

The C-level needs an overview. The PM needs insights. The developer needs understanding. Same software. Same engine. Different reading.

For the C-level
Portfolio overview
  • Which application brings you one step closer to a crisis?
  • Modernization costs forecasted
    6, 12, 36, 60 months ahead
  • Sovereignty & audit posture, at a glance
For program/project mgmt
Operational insights
  • Sprint health, observability trends, compliance status
  • Migration paths, quality drift, vendor risk
  • The weekly truth, not the quarterly story
For developers
Live understanding
  • Digital Twin — what changed, why, what depends
  • Refactor guidance, observability, decision provenance
  • PO Companion — the codebase’s voice in your PR review
Theme 05/05

Constrained software outlives unconstrained software.

Counterintuitive: giving software less freedom makes it more predictable, more auditable, and more durable. The same lesson that makes agents work makes software last ten years.

Unconstrained
What breaks down
  • Anything can call anything — no architecture survives
  • Every dependency drifts. Every shortcut compounds.
  • The codebase becomes a swamp — agents and humans both drown
Constrained
What compounds
  • Layered architecture — violations break the build
  • Boring technologies. Strong contracts. Few surprises.
  • Predictability is a feature, not a limitation
What we add
Visible constraints
  • Coupling, complexity, and drift — continuously measured
  • Architecture seen as a living document, not a wiki page
  • Boundaries you can show your auditor — and your future self
The Primitive

The ProductOwner Companion is the writing primitive.
We are the reading primitive.

$ # every PR, every dependency, every change — read, understood, told.
01 · Read
Continuous comprehension of every line.
02 · Tell
User stories, in language anyone can follow.
03 · Govern
Audit-ready by default. Sovereign by design.
The Takeaway

Don’t generate faster than you can understand.

Automated pipelines solve the writing problem. We solve the living-with-it problem.

The Trap

Generate, ship, forget.

  • Agents produce more code than any team can read
  • Verification stops at the PR — nobody owns the whole
  • Compliance becomes a quarterly fire drill
  • The senior who quietly knew everything still leaves

The Position

Read. Tell. Govern.

  • Continuous comprehension — for every audience
  • A Digital Twin of your software, told in plain language
  • Decisions, ownership, and compliance traced from day one
  • The team’s understanding survives the team
  • All software delivered with quality indicators & metrics

Automate it all if you must.
But the more you generate, the more you must understand what was built. When it fails, you are held accountable — not the prompt. Under the new EU Cyber Resilience Act, that responsibility is legally yours.

Start a conversation  →
MarQed.ai B.V. · KVK 98614797 · Apeldoorn, NL