Chris Brook, Co-founder and Head of Platform Engineering, FINBOURNE Technology, shares the limitations of the new tech trend ‘low-code, no-code’ as it applies to investment management operations.

This post is about Weave, our customisations, and a Weave related production issue that FINBOURNE encountered and resolved in the last couple of months.

In this piece we look at how the concept of the OMS became popular, what problems it sought to address, how today’s complex investment environment is testing the capabilities of the OMS and the alternative solutions available.

Daria Deluermoz, one of our first graduate hires – talks through her route to FINBOURNE, her first few months in the job and what a typical day looks like.

On a recent cycle ride, a fellow cyclist asked me what FINBOURNE does. Before I could reply a friend interjected with “FINBOURNE is building a ‘Strava’ for investment data”.

Everyone knows that data is important, but do we really appreciate how important access to correct data is for the successful execution of an investment strategy?

Bitemporal data is a fundamental principle in our LUSID platform, yet the term is not very common amongst technologists nor business users. It can be a complex concept to describe, and I’ve been thinking of a simple example to help illustrate it…

Using nginx and oauth2_proxy to deliver S3 based content (and azure blob store)

Having spent the last 15 years cossetted in the big corporate world blissfully unaware of just how complex managing Identity and access control actually is, I can best describe my journey of the last month as enlightening. Emboldened by our mission and with the idea that we were, through the advent of cloud technologies, free from having to worry about such tedious things as user management, we embarked on our righteous path.

Azure currently has some pretty interesting rules and restrictions around how things can be named. At times they seem arbitrary, but none-the-less, it’s what we have to work with.