Selected workSolmate / Infrastructure

The engineering
behind the numbers.

A website is what people see. The system behind it determines what they can rely on. For Solmate, the story goes from source data to a controlled, dated publication.

Explore the system
Solmate
Project
Website & investor dashboard
Engineering focus
Data integration & publication controls
Public reference
solmate.com

01 / The challenge

Moving inputs.
A clear point of reference.

Market prices move. Company-reported holdings have their own reporting dates. Bringing them together means preserving those differences, showing the calculation basis and making exceptions explicit.

The engineering question: how do you turn separate inputs into a consistent public page without making a snapshot look like real-time reporting?

02 / The system

Follow the data.
See the boundaries.

Select a stage to inspect it. Then introduce a source mismatch to see why the exception path matters.

Inside the publication pathInteractive schematic

Explore the architecture

01 / Source

A source and a time for every figure.

Market prices and company-reported figures have different origins. The dashboard keeps those sources and their dates visible instead of treating everything as a live feed.

Inputs with source references and timestamps

Illustrative walk-through. No live data, connected agents or publication actions.

03 / Engineering decisions

The important part
is what the system
does not let through.

  1. 01

    Keep the provenance.

    Show where each figure comes from and when it applies. A market price and a company-reported holding do not necessarily share the same date.

  2. 02

    Make disagreement a stop condition.

    Cross-check the source price before generating a replacement page. An exception should not silently become a new public number.

  3. 03

    Publish a snapshot, not a ticker.

    Render one consistent dataset into the page. Readers see a point in time, without numbers changing underneath them.

04 / Evidence, not promises

Inspect the work.

The public site carries Bithart’s build credit. Its dashboard describes the sources, cross-check and snapshot methodology. These are observable features—not claims about revenue, time saved or investment performance.

Your systems. Your next step.

What needs to work
behind your website?

Bring the workflow, the data sources and the decisions your team needs to keep. We can start by mapping how they should connect.

Discuss your use case

Bitsy answers from the heart — try one

AI replies via Anthropic. Privacy