Our team
Engineering depth,
not headcount.
Our team has built carrier-grade telecom systems, ~517K-line Rust codebases, and sovereign payment infrastructure. We solve hard problems because we have done it before.
Definition
Who leads LoneSock?
LoneSock is led by Lutfar Rahman (Nirjhar), CEO and Managing Director of both LoneSock and its parent KaritKarma Limited. He has shipped production software since 2000 and is the principal engineer behind every LoneSock engagement and every KaritKarma platform product.
Founder and leadership
Lutfar Rahman (Nirjhar)
CEO and Managing Director
A 26-year journey from founding SNIPro in 2000 to directing KaritKarma's 22-product ecosystem and LoneSock Consultancy. Nirjhar is the architect behind the entire KaritKarma platform, from identity infrastructure (Wenme) and authorization (Darwan) to carrier-grade voice (BitsPath Voice) and sovereign payment networks (IntraPay).
As an APNIC member operating ASN 64005 with BGP peering and own IP blocks, Nirjhar brings infrastructure-level thinking to every project. This is not theoretical, it is the operational backbone serving production traffic today.
His expertise spans systems architecture, platform design, and telecom infrastructure. Every client engagement at LoneSock draws on patterns validated across this portfolio.
The journey
From SNIPro to
22 KaritKarma products.
Twenty-six years of shipping production software. Same principal engineer. Same operating principles. Compounding engineering depth, not headcount expansion.
SNIPro Founded
Started as an IT consultancy in Dhaka, serving local businesses with custom software.
KaritKarma Established
Built the technology company. Became APNIC member with own ASN (64005) and IP blocks.
LoneSock Launched
Created as the consultancy and implementation wing of KaritKarma.
KaritKarma ecosystem matures
Directing KaritKarma's 22-product portfolio across ERP, fintech, telecom, media, AI, and identity infrastructure.
Core expertise
What we bring
to every engagement.
Architecture, platform thinking, carrier-grade telecom, and data center operations. None of these are slides. All four are running KaritKarma products in production today.
Systems Architecture
Designed distributed systems handling millions of daily transactions across ERP, payments, and identity platforms.
Platform Design
Architected KaritKarma's federated platform of 22 products with shared auth (Wenme), RBAC (Darwan), and communications (BitsPath).
Telecom Infrastructure
Built carrier-grade voice systems (SIP, RTP, SRTP, WebRTC), SIGTRAN and SS7 gateways, and RADIUS AAA for ISPs.
Data Center Operations
Runs a Tier-3 data center as an APNIC member with ASN 64005, BGP peering, and own IP blocks.
The advantage
The KaritKarma
advantage.
As part of KaritKarma, your project benefits from patterns proven across 22 production products. Auth patterns from Wenme. Authorization from Darwan. Bank-custodial escrow from Hold.bd. Communication pipelines from BitsPath. Every solution we build for you inherits this depth.
Frequently asked
About the team,
in plain language.
Who runs LoneSock?
Lutfar Rahman, known as Nirjhar, is CEO and Managing Director of both LoneSock Consultancy and its parent KaritKarma Limited. He is the principal engineer on every LoneSock engagement and the architect behind KaritKarma's 22-product platform.
How big is the LoneSock team?
LoneSock runs as an owner-operator consultancy. Engineering depth comes from the principal engineer plus a small senior delivery team. Capacity scales by pulling specialists from the KaritKarma product organization for the specific component a client needs.
Does the same engineer who scopes my project also build it?
Yes. The discovery call, the architecture review, and the working code all come from the same principal engineer. There is no handoff from sales to delivery and no rotation of junior engineers onto the engagement.
What if the team grows mid-engagement?
Capacity is added by attaching specialists from inside the KaritKarma platform team for the specific module the client needs. They report to the same principal engineer for the duration of the engagement, then return to the platform team.
How do you handle a client whose project sits outside your expertise?
We say so during discovery and either decline politely or scope the engagement to the parts we can deliver well. We will not pad capacity by learning a new ecosystem on the client's dollar.
Want to work with us?
Tell us what you are building. We will respond with engineering, not a sales deck.