Custom business software
Billing, stock, ledgers, approvals, roles and reports — the system a business runs its day on. Our own hospital and distribution products are exactly this, so it is the shape of problem we know best.
ServicesCustom software development
We build custom software, and we run what we build.
Altushisoft is a software company in Sylhet, Bangladesh. We take on custom web applications, APIs, data-heavy systems and the cloud they run on — and we keep them running afterwards.
- Two of our three products we designed and built ourselves. All three we deploy, run and support in production.
- You talk to the engineers doing the work. There is no sales layer in between.
- Four shared working days a week with Europe, and English for everything written and spoken.
- years of professional experience
- 10+
- records on a data platform we led
- 300M+
- products we run in production
- 3
- automated tests in Altushi HMS and DMS
- 4,122
What we build
The work we take on, described by what it actually is.
Web applications
Server-rendered or single-page, built with Laravel, Node or NestJS and a TypeScript or Vue front end, on MySQL, MariaDB or PostgreSQL.
APIs and integrations
REST APIs for your own applications, and the awkward joins in between: payment and SMS gateways, attendance and barcode hardware, thermal and A4 printing, and imports from systems that will never change.
Data-heavy systems and search
Reporting over large tables, and search that has to stay fast — Elasticsearch, including geolocation search, and Redis where caching is the honest answer.
Cloud, deployment and operations
Docker on AWS, Google Cloud, a plain virtual machine or shared hosting, whichever suits the budget. TLS, backups, restore scripts and a deployment you can run yourself.
Maintenance of a system you already have
Taking on an existing codebase: finding out what actually works, writing it down, fixing what is breaking, and keeping it running.
The work you can already look at
We are not only a services company. Three products carry our name, and each has a page on this site. Two of them — Altushi HMS and Altushi DMS — we designed and built ourselves. All three we deploy, run and support in production.
Altushi HMS
Hospital management ERP
Designed and built in-house
A hospital ERP: 15 modules, 120 screens and 68 permissions, from registration and billing through the lab and wards to the accounts ledger. It runs on-premise, one machine per hospital, on Docker Compose and PostgreSQL 17.
Explore Altushi HMSAltushi DMS
Distribution management
Designed and built in-house
Distribution management for distributors with field sales and delivery teams: a Laravel API behind a Vue single-page front end, with 20 report pages and a role matrix of 111 permissions.
Explore Altushi DMSAltushi POS
Point of sale and inventory
We deploy, run and support it
Point of sale for pharmacies and shops. We run each shop as its own container with its own database, provisioned by a single command, with 24 reports behind the counter.
Explore Altushi POSThe screenshots on those pages come from local demo instances filled with invented data — never from a customer's system.
How we build, in specifics
General claims about quality are cheap. These are controls that exist in the code of the products above.
- Money is corrected by reversal, never deleted. Receipts cannot be edited or removed, and the application's own database role is not permitted to delete a financial, clinical or audit row.
- The audit trail is written in the same transaction as the change it records, so the two cannot drift apart.
- Prices are effective-dated. Reprint last year's invoice and it reproduces last year's price.
- Permissions are enforced on the server. The menu and the endpoint read the same grants, so hiding a button is never the security.
- Automated tests are part of the work rather than a phase at the end: 2,387 of them in Altushi HMS and 1,735 in Altushi DMS.
- Design decisions are written down as they are made. Altushi HMS alone carries 32 architecture decision records.
- Backup and restore are scripted and rehearsed, including a point-in-time recovery drill.
- Our software makes no third-party request at runtime unless you ask for one, and each shop on Altushi POS gets a database of its own.
- This website is the smallest example: no framework, no build step, no external request, one stylesheet inlined under a content-security-policy hash, and 100 out of 100 on all four Lighthouse categories.
How an engagement runs
Five steps, and you can stop after any of them.
Discovery
A conversation about the problem, what exists today and what "finished" would look like. If we are not the right people for the job, we say so here.
Written scope and quote
You get the scope in writing: what is included, what is deliberately excluded, what we need from you, and the price. Nothing is built before you have it.
Build in short cycles
We build in small pieces and show you working software rather than pictures of it. You open it yourself and tell us where we have it wrong, while it is still cheap to change.
Handover
The running system, the deployment scripts and the documentation written along the way — enough that another engineer could pick it up from there.
Support
We keep it running, on the same channels you already use to reach us.
What arrives every week
- Software you can open and use yourself, at a URL — not a recorded demo.
- A short written note: what changed, what is next, and anything that is blocked.
- Any decision we need from you, put as a question with our recommendation.
How questions get answered
By the engineer doing the work, on WhatsApp or by email, during our working hours. Nobody relays your question to someone else and relays an answer back.
Ways to work with us
Three arrangements. Which one fits usually becomes obvious during discovery.
Fixed-scope project
A defined piece of work, with a written scope and one price. It suits you best when you already know what needs building.
- Scope and price agreed before work starts
- Changes are quoted, not absorbed quietly
Monthly retainer or a dedicated engineer
An agreed amount of engineering time each month, working to your priorities as they change. It suits you best when the roadmap is still moving.
- You set the priorities each cycle
- The same engineer stays with your codebase
Maintenance and support
For a system that already exists and simply has to keep working — one we built, or one you inherited from someone else.
- Fixes, upgrades and dependency updates
- Deployment, backups and restore rehearsals
The practical questions, answered first
The things a client abroad asks before anything else.
- Where we are
- Sylhet, Bangladesh.
- Working hours
- Sunday to Thursday, 10am to 5pm (Bangladesh time, GMT+6). Closed Friday and Saturday.
- Shared working days
- Our week runs Sunday to Thursday, so we share Monday, Tuesday, Wednesday and Thursday with a Monday-to-Friday week. We work on Sunday, when you probably do not, and we are closed on Friday and Saturday.
- Language
- English for everything written and spoken: scope documents, code, commit messages and the conversation itself.
- How we talk
- WhatsApp and email for the day-to-day, and a call when a call is faster. WhatsApp and email need no overlapping hours at all.
- What we do not claim
- We publish no client names, logos or testimonials, and we hold no ISO or SOC 2 certification. Everything stated on this site is something you can check in the software itself.
Hours we share with you
Our working day is 10am to 5pm in Bangladesh, which is GMT+6. In your time that comes to:
| Where you are | Overlap |
|---|---|
| Central Europe | Three to four hours, depending on summer time. |
| United Kingdom | Two to three hours, depending on summer time. |
| The Gulf | About six hours — most of your working day. |
| United States | None. Our day ends before yours begins, so WhatsApp and email carry the work. |
The engineer you would be working with
Jidul IslamFounder & CEO
Altushisoft is led by Jidul Islam, a software engineer with more than ten years of professional experience, most of it on systems where traffic and data volume are the hard part.
- Lead software engineer on a data analytics platform for a Sweden-based company, working with data volumes of more than 300 million records at low latency.
- Senior developer for a UK real estate portal, including a geolocation search engine built on Elasticsearch.
- Team lead and software architect at software firms in Sylhet, Bangladesh.
- Works across PHP (Laravel), JavaScript and TypeScript (Node, NestJS), Go, MySQL, PostgreSQL, Redis, Elasticsearch, AWS and Google Cloud.
We describe the roles rather than naming the companies, because those clients have not agreed to be named.
What a quote is based on
We do not publish rates or packages, because neither would be true for your project. Tell us the problem and you get one written quote for the work.
What shapes the quote
- What the software has to do — and what it deliberately will not do
- The systems and hardware it has to talk to
- How much data it holds, and how quickly it has to answer
- Where it runs, and whether we set it up and operate it for you
- Whether you want us after launch, and for how long
Contact for a quote
Every engagement includes
- A written scope before anything is built
- Working software you can open yourself each week
- Deployment scripts and documentation at handover
- Direct access to the engineer doing the work
Prefer email? Write to hello@altushi.com
Questions clients abroad ask
Not answered here? Ask us directly and a person who knows the software replies.
Ask your question on WhatsAppWhere are you, and what hours do you work?
We are in Sylhet, Bangladesh. Sunday to Thursday, 10am to 5pm (Bangladesh time, GMT+6). Closed Friday and Saturday. That gives three to four hours of overlap with Central Europe and two to three with the United Kingdom on each of the four working days we share with a Monday-to-Friday week.
Do you take on work from outside Bangladesh?
Yes — that is what this page is for. All written and spoken work is in English, and most of a project happens over WhatsApp and email, which need no overlapping hours. Europe and the Gulf also get live overlap on every shared working day; the United States gets none, so that work runs asynchronously.
What languages and technologies do you work in?
PHP with Laravel, JavaScript and TypeScript with Node and NestJS, and Go. MySQL, MariaDB and PostgreSQL for data, Redis for caching and Elasticsearch for search. For infrastructure, Docker on AWS, Google Cloud or a plain virtual machine.
Can we see something you have built?
Yes. Altushi HMS and Altushi DMS were designed and built in-house, and each has a page on this site with real screenshots. Altushi POS is the third product we deploy, run and support. Every screenshot comes from a local demo instance filled with invented data, so none of it belongs to a customer.
Who will actually do the work?
The engineers who answer your messages. There is no account manager between your question and the person writing the code.
How does a project start?
With a conversation about the problem, then a written scope and a quote. Nothing is built before you have both of those in writing.
What does it cost?
It depends on the scope, the systems it has to talk to, how much data it holds and whether we run it for you afterwards. We do not publish rates or packages. Describe the problem and we send a written quote.