About
From an idea to working technology
Complex organisations run on networks of applications, dataflows, business processes and suppliers. The information about how those things connect already exists — scattered across CMDB exports, spreadsheets, architecture documents and Visio drawings. Seeing the connections is the part nobody has solved well. Fluxcarta started as that observation, and is now working software.
Who is behind it
Small, independent, and close to the work
Fluxcarta is initiated by Jelmer Baars, an International Business student with a long-standing interest in technology and in how organisations cope with complexity. He takes the product and the company forward from here.
The usual order is a business plan first and the technology later. This went the other way around: build the thing, prove it works, and only then work out what business belongs around it. That is why there is a finished product to try before there is a sales team to talk to.
Staying small is deliberate. It means a short line between a question and an answer: no support tier to escalate through, no account manager between you and a decision, and no roadmap committee deciding your request is out of scope. When you write in, you reach the people who build the thing.
Where things stand
- The product works. Fluxcarta is on the Mac App Store as a one-off purchase. What you see in a demo is the real software, not a mock-up.
- In development. Windows, iPad and iPhone, plus a shareable-viewer and tenant deployment for organisation-wide rollout.
-
No shared backend.
Your model stays on your device in a native
.ctvfile. There is no vendor server holding your landscape data — by design, not by promise. - Independent. No outside funding, no investor pressure on the roadmap, no acquisition to plan around.
Why it exists
Organisations have the data. They do not have the overview.
A modern organisation runs through applications, integrations and APIs, business processes, dataflows, cloud platforms and outsourced services. What each of those is tends to be documented somewhere — in a CMDB, in a register, in someone's Visio file. How they depend on each other usually is not.
A diagram gives you a snapshot that is out of date by the time it is printed. A spreadsheet gives you rows without relationships. An enterprise-architecture suite gives you everything, at the price of a year-long project. The gap in between is where this belongs: take the data an organisation already keeps, and turn it into something you can actually look at.
Import the data. See the connections. Press play and watch the process run. That is the whole idea, and everything in the product serves it.
Why now
Dependencies keep growing. Understanding of them has not kept up.
Cloud, SaaS, integrations, APIs and outsourcing add new dependencies every year. At the same time, boards and supervisors increasingly expect organisations to be able to explain those dependencies — under GDPR, under NIS2 or DORA, or simply because someone asked which systems touch personal data, or what breaks when one of them goes down.
Most of that explaining still happens through spreadsheets, slide decks and static diagrams. A picture you can interrogate is a better answer, and it is a strange thing for an industry this technical not to have.
Investors & partners
An early-stage opportunity
The first milestone is done: an idea became working software. The next one is commercial. Which use cases create the most value, which customers feel the problem most sharply, and what the right model is — those questions are open, and being worked on rather than guessed at.
The underlying technology is not limited to application landscapes. The same engine already drives SupplyVisual for supplier chains and concentration risk. Data governance, impact analysis and operational-resilience reporting are adjacent, and reachable from the same foundation.
Experience is worth as much as capital at this stage. B2B SaaS, enterprise software, go-to-market, product strategy, international growth, or governance, risk and compliance — if you have built something in that territory and see the potential here, a conversation is welcome.
The software is the argument.
Rather than read about it, see it run: book a 20-minute demo and we'll turn one of your own processes into a playable journey, on your data.