Keeping analytics off the hot path with Kafka
In a multi-tenant SaaS, one busy storefront can exhaust the connection pool every other merchant shares. Why Fitly's events go to an append-only log instead of straight into Postgres.
Ripelix is a small software studio in Dhaka, Bangladesh. We build a handful of products and give each one real attention — starting with Fitly, a Shopify size-chart app.
A Shopify app that lets merchants build professional size charts and show them on product pages — no code, no theme edits, no developer.
The ripple
Our name comes from the ripple effect: solve one problem cleanly, and the value spreads out from there. It's the reason we'd rather go deep on one thing than wide on ten.
Most software problems are never solved. They're absorbed.
Absorbed by a workaround. Someone builds a spreadsheet around it, and the spreadsheet quietly becomes part of the job.
Absorbed by a setting. The problem gets an option instead of a fix, and everyone learns which path to avoid.
Not patched, not hidden behind a setting nobody finds.
The spreadsheet, the copy-paste step, the thing everyone just knew to do.
It fits the job they already had, so it stops costing them attention.
Fewer support threads, less to explain, nothing to undo later.
Into the next problem, instead of into maintaining the last one.
The later effects are the ones worth building for
Anyone can ship the first link in that chain. The value is in what stops happening afterwards — the workaround nobody rebuilds, the support thread nobody opens, the week nobody spends undoing it. Those are slower to arrive and they are the reason we keep the catalogue short.
Why Ripelix
We're early, and we treat that as a strength. Here's what shapes the way we work.
We build a small number of products and give each one real attention, rather than spreading thin across many.
Every feature starts from an actual merchant or user problem — not a spec sheet.
An early-stage studio with no investors to please. We can prioritise what genuinely helps our users.
Type-safe code, sensible architecture, and performance treated as a feature from day one.
Our approach
A simple, repeatable way of working that keeps our products focused and honest.
We talk to the people who feel the pain and map the workflow before writing any code.
A small, solid release that solves the core problem well beats a bloated one that solves nothing cleanly.
We watch how the product is actually used and improve it in tight, deliberate iterations.
From the blog
Whether you want to try Fitly or talk about custom software, we'd love to hear from you.