Product

A project-controls operating system, not another reporting layer.

Most controls tooling reads extracts and draws charts over them. VECYRA is different: it holds the project itself — activities, calendars, resources, costs, documents, decisions, and evidence — as one governed model, and every module is a professional workspace over that model.

Download the Beta Browse the Modules

VECYRA — Knowledge Graph

Core

One governed model. Zero reconciliation.

In VECYRA there is no schedule file, cost file, and risk register to keep in sync. There is one versioned project model. Modules are lenses over it: Planning authors the network, Control closes periods against it, Analysis stress-tests it, Commercial builds claims from it, and Reporter publishes from it.

Object-centric — activities, WBS, BOQ, documents, decisions, and evidence are typed objects with relationships
Knowledge graph — the model is queryable as a graph, so cross-discipline questions have one place to answer from
Provenance everywhere — every value knows its source, and every change knows its author

VECYRA — Schedule / Gantt

VECYRA Gantt workspace with activity table, critical path, and inspector

Scheduling

A deterministic, calendar-aware CPM engine — and real XER import.

The scheduling core computes early/late dates, float, and the critical path deterministically from the network, calendars, constraints, and data date. The same inputs always give the same dates, and the arithmetic can be inspected — essential when a date is challenged.

Calendars are first-class — work periods, exceptions, and calendar assignments drive every date
Real XER import — validated against genuine Primavera P6 v5–v8 exports, with mapping and validation on arrival
Baselines — publish a baseline, then measure every later revision against it

Governance

Trust is engineered in, not audited in afterwards.

VECYRA's governance layer runs continuously, not at month-end. It is what lets six modules share one model without one team's edit silently corrupting another team's numbers.

Validation engine

The model is checked continuously — schedule logic, progress discipline, structural integrity. Findings are explainable: each one states what is wrong, where, and why it matters, ranked by severity so review starts with what matters most.

Audit trail

An append-only record of change: who changed what, when, and from which source. Baselines and period closes are governed events, so “the number changed” always has an answer that isn't a shrug.

Traceability & provenance

Every value in every module can be traced back through the objects it was computed from to the source it came from — a progress entry, a document, an import. When a figure is challenged, the answer is a path, not a search.

Deterministic by default

Computed results are reproducible: recompute with the same inputs and you get the same answer. Where the product simulates — Monte Carlo schedule risk — the output is labeled as a distribution from a simulation, never as a fact.

Modules