Tessera Viz
PX-02
For people already paying someone
Four libraries, one selection-sync file, and a bill that grows when you hire.
You bought a graph SDK. It works. Then the timeline arrived as a second product, the dashboard needed a charting library and the table needed a grid vendor. Four licences, four theming systems, four renewal dates — and a file in your codebase whose only job is keeping four selections in step. That file has bugs. It always has bugs. Nobody wants to own it.
The file nobody wants to own.
What is in it
An effect that pushes the grid's selection into the graph. A second that pushes the graph's back into the grid and on to the timeline — which loops with the first, so there is a guard flag. A third that turns a brushed time range into a filter for the graph and the map, which runs on every frame of the brush, so there is a debounce.
What else is in it
The bug you have not found yet. Four components with four opinions about when state settles will disagree eventually, and the disagreement surfaces as a selection that flickers or a filter that does not clear.
What replaces it
Nothing. The surfaces share a selection model, so there is no synchronising code, because there is nothing to synchronise.
Three arguments, in the order they matter.
Delete the glue code
The strongest one, because it is about your codebase rather than your budget — and you can verify it in an afternoon rather than a procurement cycle.
Per application, not per developer
Hiring should not increase your software bill. The licence covers the application you ship, and the developers working on it are unlimited.
One security review instead of four
Four vendors is four dependency trees, four sets of CVEs and four sets of paperwork. No third-party runtime dependencies and one vendor is a materially smaller review, and the ISO 27001 gap assessment is ready to hand over.
What we are not going to tell you.
That your current tool is bad
You chose it, and it was the right choice for one surface. You now have four surfaces. That is a different question from whether the first answer was wrong.
That price is the reason
Leading with price says "cheaper, probably worse". The reason is the file, and the bill is a consequence.
That migration is trivial
A straightforward graph view is typically days. An application with heavy custom rendering is weeks, and the custom drawing is where the time goes. We will do a scoped assessment free, including telling you when it is not worth doing.