Ubikron is our third answer to a question from 2017.

The question was whether browsers should organize the web by site. The first two answers taught us what not to build.

The first was too dense and the second too light.

  1. The question

    A pet peeve from the Maltego days: in a hurry, I reach for a browser to get info first, not a graphing tool. But we're nowhere in a browser!

    Right question, legacy dragged us down.

  2. Vortimo

    A browser for what you'd already browsed. The deepest tool of its time.

    Too complex for the time. Also, unstable DB.

  3. Skylight, then OSINT-Tool

    The opposite bet: no install, no database, no learning curve.

    It couldn't hold a real investigation.

  4. Ubikron

    Started from scratch. The depth of the first, the ease of the second, and a real server underneath.

    This one stuck.

Twenty-eight empty tins of instant coffee stacked in a pyramid against white tiles
sha256 08729e0c…33051c

Ubikron so far: 28 tins of coffee.

Every tin we've emptied since we started building it in 2023, and that's just from South Africa.

The three people who make Ubikron, on a street lined with trees
All three of us.sha256 a3099923…d262f9

Three people, no suits, and nobody telling us to make it worse.

We answer to the people who use Ubikron.

Roelof TemminghSensePost, then Maltego, now Ubikron