3beez

Product · Modernization

Legacy software, carried forward by agents.

Vive assesses a legacy codebase, documents what it actually does, plans the migration, generates the new system, and proves it with tests. A fleet of specialized agents runs the pipeline; a person approves every stage before it advances.

One pipeline, from archaeology to production

01Provision
02Assess
03Docs
04Future State
05Spec
06Plan
07Generate
08Test
09Deploy

About these screens. The screenshots below are taken from the Vive interface running against a sample project built for demonstration. They show the real product; the codebase being modernized is illustrative, not a customer deployment.

Where the whole programme stands.

Every project opens on a modernization overview: the nine-stage pipeline with its current position, the subsystems the analyzer found, how many of them are regulated, and what is waiting on a human.

Vive modernization overview showing the nine-stage pipeline, metrics for clusters, regulated subsystems, open checkpoints, and stages complete
Modernization overview · four subsystems identified, three carrying regulatory obligations, two of nine stages complete.

The system, broken into subsystems it can name.

The analyzer reads the repository and clusters it into coherent subsystems — each with a domain, a size, the regulations that touch it, a confidence score, and the provenance of how it was decided.

Vive clusters table listing Card Authorization, Statement Generation, General Ledger and Customer Master with domain, lines of code, regulatory tags, confidence and status
Cluster map · PCI-DSS, SOX and GLBA obligations surfaced per subsystem, each with a confidence score.

How the pieces actually depend on each other.

Dependencies are extracted from the code itself rather than from documentation nobody has updated. Arrow thickness tracks the number of underlying inter-cluster edges.

Vive architecture view showing four cluster cards connected by dependency arrows, with file counts, internal edges and lines of code
Architecture · static call extraction across four clusters, three edges.

The model proposes. You decide.

Gated stages stop and wait. Approving advances the pipeline and starts the next stage; requesting changes re-runs the same stage with your comment fed back to the agent as instruction. Nothing moves forward unreviewed.

Vive checkpoint review screen for current-state documentation, with a comment box and Approve or Request changes actions
Checkpoint review · the current-state documentation stage awaiting a decision.

Every artifact is readable, editable, and answerable.

The documents the agents produce are not a black box. Browse the generated tree, read or hand-edit any file, and interrogate the whole corpus — answers are grounded in the project's own artifacts rather than in general knowledge.

Vive artifact management screen with a file tree, a markdown preview of a subsystem specification, and an agent question-and-answer panel
Artifact management · generated subsystem specs, with edit approvals and grounded Q&A alongside.

A run you can watch, and a history you can audit.

Each run reports where it is, what it is waiting on, and what happened at every stage before it — so a modernization that takes weeks stays legible the whole way through.

Vive run detail screen showing the pipeline position, a prompt that the run is waiting on human review, and stage history with event counts
Run detail · the pipeline paused on a human decision, with per-stage event history.

Modernize the system everyone's afraid to touch.

Vive is in development. If you have a legacy estate you would like to put through it, we would like to hear about it.