Few technology questions generate as much confident advice as "cloud or on-premise?". Some vendors say everything should be in the cloud. Some IT teams prefer servers they can see and touch. Both positions are sometimes right, and both are sometimes expensive mistakes. For a mid-size business, the honest answer depends on your systems, your connectivity, your people and your obligations, not on what is fashionable.
This article sets out what each option really involves, the questions that should drive the decision, and why a mixed approach is often the sensible outcome.
Be clear what you are comparing
"Cloud" covers several quite different arrangements:
- Software as a service (SaaS). You use an application run entirely by the vendor, such as email, accounting or HR software, through a browser or app.
- Cloud infrastructure. You rent servers, storage and databases from a cloud provider and run your own or custom applications on them.
- Local hosting or co-location. Your servers, or rented ones, sit in a data centre operated by someone else, possibly within Bangladesh.
"On-premise" means servers in your own building, managed by your own team or a contractor. Each option moves different responsibilities to different people, and that is the real comparison.
Cloud does not remove responsibility. It changes who does which part of the work, and what you pay for it.
Six questions that should drive the decision
1. How reliable is connectivity at each site?
Cloud systems depend on internet access. An office in Dhaka with two independent connections is in a very different position from a factory on the outskirts with one line and frequent outages. List each site, its connections and its history of downtime. For critical floor operations, consider whether the system can continue working offline and synchronise later.
2. Who will run it?
On-premise servers need someone to manage power, cooling, updates, backups, security and hardware replacement, including at night and on holidays. If you do not have that capability, or cannot reliably contract it, managed cloud services may be safer even if they look more expensive on paper.
3. What does the five-year cost look like?
Compare total cost over a realistic period, not the first invoice:
- On-premise: servers, storage, network equipment, backup hardware, licences, power and backup power, cooling, physical security, staff time and replacement every few years.
- Cloud: monthly or annual charges that grow with usage and users, data transfer, backup services, better internet links, and staff time to manage accounts and costs.
Cloud costs are easy to start and easy to let grow. On-premise costs are front-loaded and easy to underestimate. Work out the numbers for your own case, with real quotes.
4. Where must your data be, and who must be able to access it?
Check the obligations that apply to you: contracts with buyers and banks, and Bangladesh's personal data protection law, which includes rules on transferring certain personal data outside the country. These rules have been changing, so take legal advice on your specific position before moving personal or sensitive data to a provider abroad. Equally, consider who needs access: sales teams on the road, managers checking from home, or buyers through a portal.
5. How quickly must you recover from a failure?
Decide how long each system can be unavailable, and how much recent data you could afford to lose. A payroll system may tolerate a day. An order or production system may not tolerate an hour. Cloud providers offer strong options for resilience, at a price. On-premise resilience requires duplicate hardware, tested backups and, ideally, a second location.
6. How will you leave, if you need to?
For SaaS, confirm that you can export all your data in a usable format. For cloud infrastructure, prefer standard technologies that can run elsewhere. For on-premise, make sure the system is documented well enough for another team to take it over.
When each option tends to fit
Cloud or SaaS usually fits when
- The software is a commodity, such as email, file sharing, HR or standard accounting.
- Users are spread across sites or travel often.
- You lack in-house capacity to run servers well.
- Demand varies, and you would rather pay for what you use.
On-premise or local hosting usually fits when
- Floor operations must keep running through internet outages.
- Systems connect closely to local machines, scanners or devices.
- Legal or contractual requirements limit where data can be held.
- You already have a capable team and reliable infrastructure.
The hybrid answer
Many mid-size businesses end up with a mix: email, collaboration and some commodity applications as SaaS; core business systems in the cloud or a local data centre; and a small local server or offline-capable app at each factory to keep the floor running when the link drops. The design work is in connecting these parts cleanly, with clear data ownership and backups that cover all of them.
Practical steps before you move anything
- List your systems and rate each for criticality, sensitivity of data and dependence on local devices.
- Assess connectivity at every site honestly.
- Agree recovery targets for each critical system.
- Get real quotes for both options and compare five-year totals.
- Check legal and contractual obligations on data location.
- Move in stages, starting with a lower-risk system, and test backups and restores in the new setup before moving the next.
Where RAED fits
We design and deploy systems on cloud, local and hybrid infrastructure, and we choose based on your connectivity, recovery needs and obligations rather than a preference of our own. We can also help you build a clear, costed comparison before any migration begins.
Sources
- Dhaka Tribune, "Parliament passes 31 bills related to IG-era ordinances", 9 April 2026 (includes the Personal Data Protection Bill, 2026). dhakatribune.com
- Securiti, overview of Bangladesh's Personal Data Protection Act, 2026, including cross-border transfer provisions, 29 June 2026. securiti.ai
