A product studio that uses its own software
Scriptix Labs builds and runs its own products. That is not a side project — it is the thing that makes us useful on client work, because we have made the expensive mistakes on our own time and money first.
We ship, then we talk about it
Everything on this site links to something you can install, open, or read the source of. Where something is not finished, it says so. That constraint is deliberate — it is the only claim that cannot be faked.
Small on purpose
We are not trying to be a hundred-person agency with a service for every acronym. A narrow stack and a short service list mean our estimates hold and the person who designed your system is the person building it.
Free where it costs us nothing
Pulse Companion is free forever on every browser store, with no paid tier planned, because it costs us almost nothing to run. Our libraries are MIT-licensed. We charge for engineering time, not for access.
Built in this order, for these reasons
- The libraries
strio and encryptix
We kept writing the same two utilities — secure token generation and application-layer encryption — badly, in project after project. So we built them once, properly: zero runtime dependencies, full types, tested in CI, documented. Both are live on npm.
See the packages - The first product
Pulse, for Jira
A time tracker built because the team was losing hours to reconstructing timesheets from memory. It became a full Forge app — timers, bulk logging, templates, timesheets, reports — and then a browser extension to cover everything a Forge app structurally cannot reach.
Read about Pulse - Products in production
Paisa and RLBH Connect
Paisa handles shared expenses with debt simplification and multi-currency, offline-first. RLBH Connect replaced a WhatsApp group and a hand-maintained spreadsheet with a real alumni and business directory. Both are live.
All products - Now
Client engineering
The same team, the same standards, applied to other people’s problems. We are deliberately small, which means we take on work we can actually finish and say no to the rest.
What we do
What the first conversation looks like
You describe the problem. We ask what we need to ask, then tell you honestly whether it is a fit, roughly what it would take, and what we think the risky part is. If it is not a fit we will say so — that is cheaper for both of us than three weeks of discovery.
Tell us what you're building
A few sentences is enough to start. If it's a fit we'll come back with questions and a rough shape; if it isn't, we'll say so rather than waste your time.