Why Vaeltrix Labs
What this blog is for, what I plan to write about, and why it runs on a handful of Markdown files and a free static host.
After close to twenty years in banking technology, I’ve built up a long list of things I wish someone had written down for me earlier. How to put an API gateway in front of a core system that was never designed for it. What actually goes wrong in a digital onboarding journey once real customers hit it. Why the vendor demo and the production rollout are rarely the same product.
Vaeltrix Labs is where I’ll write those things down.
What to expect
Most posts will be about the practical side of banking technology:
- Integration and APIs: gateways, middleware, event-driven patterns, and keeping legacy and new platforms talking to each other
- Architecture: target-state designs, the trade-offs behind them, and how they survive contact with delivery
- Digital channels and security: onboarding, mobile, WebViews, and the controls a regulator will ask about
- AI in production: where it earns its place in a bank and where it is still a slide
- Programme delivery: vendor evaluations, steering committees, and getting decisions made
Now and then I’ll write about personal investing. Those posts will be clearly tagged finance, and they are opinions, not advice.
How the site is built
In keeping with the subject matter, I wanted something simple, fast and cheap to run. No database, no CMS, nothing to patch. Every post is a Markdown file in a Git repository, and the site is rebuilt and deployed on every push.
A post starts life like this:
---
title: 'Putting a gateway in front of a 20-year-old core'
description: 'Patterns that worked, and the ones that did not.'
pubDate: 2026-12-01
tags: ['tech', 'integration', 'apis']
draft: true
---
The stack is Astro generating static HTML, hosted on Cloudflare Pages. A build takes seconds, and the pages that come out are plain HTML and CSS with very little JavaScript.
A note on views
Everything here is my own view. It doesn’t represent any employer, and I won’t be sharing anything confidential. Where I use real-world examples, they will be generalised enough to be useful without being identifiable.
If that sounds useful, the RSS feed is the easiest way to follow along.