We build softwarethat actually ships.
A small software studio building SaaS products, internal tools, and business systems. No bloated teams, no recycled templates — just software people actually depend on.
Custom software, end to end.
From a blank repo to a product real users depend on. No department hand-offs — the person who scopes the work is the person who ships it.
01
Custom product builds
Full SaaS platforms from scratch — architecture, auth, payments, admin tooling — taken from idea to a system real users can run on.
02
Infrastructure & DevOps
Deployment pipelines, monitoring, automated backups, and cloud cost decisions made with the same scrutiny we'd apply to our own product.
Technology we reach for, and why.
Not a buzzword wall — this is what's actually running OikkoEdu and the infrastructure behind it today.
Frontend
React
Next.js
TypeScript
JavaScript
Tailwind CSS
Redux
React Native
Mobile
Flutter
Dart
Android
iOS
Backend
Node.js
Express
TypeScript
MongoDB
Redis
BullMQ
Firebase
PostgreSQL
SQLite
Infrastructure
DigitalOcean
Cloudflare R2
Coolify
Nginx
Docker
Uptime Kuma
Services
Stripe
SSLCommerz
Resend
MimSMS
WebView
Telegram API
Products, not portfolio pieces.
Two builds that show how we think — a live commercial platform, and the project that shaped our approach to product design.
Flagship · Live
OikkoEdu
The operating system for coaching centers in Bangladesh — multi-tenant student management, queued attendance SMS, fee tracking, and a dedicated parent portal, running in production today.
Product design
Gamify Learn
A gamified social learning platform — turning study progress into achievements, streaks, and shared goals between students. Where our thinking on engagement-driven product design took shape.
Scope. Build. Ship. Repeat.
No discovery that drags for months, no hand-offs between teams. Just a straight line from understanding your problem to shipping working software.
01
Understand & scope
We learn your workflow, map the real requirements, and define a scope that fits your budget. Usually takes a few calls — no invoices until you're happy with the plan.
02
Build in the open
You get access to the private repo and a live staging URL from day one. Progress is measured in shipped commits, not status-meeting slides.
03
Deploy & iterate
We deploy to production, set up monitoring, and hand over with documentation. Post-launch, we're a message away for fixes, tweaks, and v2 features.
Built different by design.
Small studio, no bloat. Here's what that means for you.
Small team, direct ownership
The people who scope your project are the same people who build and deploy it. No layers of management, no lost context.
Products, not mockups
We don't deliver Figma files and call it done. You get a working system deployed to a real URL, with real users on it.
Lean & transparent
No agency overhead, no account managers, no 200-person team baked into your rate. You pay for engineering time that ships.
Decisions we make on every build.
Not abstract values — these are the calls we actually make when scoping and building a product.
01
Design for the failure case first
Before we write the happy path, we ask what happens when a queue backs up, a payment fails mid-flow, or a server needs replacing at 2am. Resilience built in from the start is cheaper than resilience bolted on later.
02
Multi-tenant by default, not by request
Even single-client builds get architected with isolation in mind — subdomain or schema-level separation — so the system can grow into more users without a rewrite.
03
Queue anything that can be retried
SMS, email, and notification delivery go through a managed queue, not a synchronous call. If a provider hiccups, the job retries — it doesn't silently fail.
04
Back up before you need to
Automated, off-site, and tested — not a manual export someone forgets to run. A backup strategy nobody has verified is just a hope.
Built like infrastructure, not a prototype.
A look at what's actually running in production today.
Multi-tenant
Subdomain-isolated architecture
Queued
Redis/BullMQ notification pipeline
Daily
Automated off-site backups
24/7
Uptime monitoring & alerting
A platform that handles real schedules, real payments, and real student data can't afford to be fragile. That's why OikkoEdu runs on a replicated database, queued messaging, and monitored infrastructure from day one — not bolted on after something breaks.
We design for the failure cases first: what happens if a queue backs up, if a payment fails mid-flow, if a server needs to be replaced overnight. Client work gets the same discipline, whether it's a five-page site or a multi-tenant platform.
Let's talk
Got something worth building?
Tell us what you're trying to solve. We'll tell you honestly if we're the right fit.
Usually reply within a day · Sirajganj, Bangladesh