Local server or cloud for an SME in Madagascar: how to choose?

For an SME in Madagascar, choosing between a local server and the cloud starts with the work to be done: which tools must be available, from which locations and with what tolerance for interruptions? Connectivity, power supply and the people able to intervene are part of the decision.

Start with business tasks, then compare solutions covering the same scope: hosting, administration, access, backups and recovery.

1. Define what must remain available

List the applications, files and databases your business needs. For each service, record its users, access locations, acceptable downtime and how much work could be re-entered after data loss.

Also identify dependencies: authentication, licences, email and external services. Software installed on your premises can still rely on the Internet for some functions.

2. What an on-premises server involves

An application running entirely on your local network may remain available during an Internet outage, provided workstations, networking equipment and the server remain powered and operational. Access from outside the premises depends on connectivity and the chosen remote access solution.

The project should cover equipment location, power, maintenance and authorised personnel. A UPS can bridge some short outages or allow an orderly shutdown; its runtime should be measured with the connected equipment.

A local server is therefore worth assessing for internal tasks that must continue without a permanent Internet connection. It requires suitable arrangements for faults, backups and remote access.

3. What a cloud service involves

A remotely hosted service can be used from several locations without placing a server at each one. Every user still needs a suitable way to connect. If a tool offers an offline mode, check its capabilities and synchronisation before relying on them.

Cloud covers different service models. With a hosted virtual machine, your business or provider may still manage the operating system and applications. With software delivered as a service, the publisher handles more of the operation. Accounts, permissions and data protection still require organisation: Microsoft’s shared responsibility model illustrates this distinction.

For cloud-dependent work, assess the impact of connectivity failure and the value of a backup connection. Two offers do not necessarily provide independent paths. AWS guidance on connection diversity highlights equipment, carriers and physical routes.

4. Assess a hybrid setup

You can split workloads: a business application on your premises, hosted email and an off-site backup copy, for example. This allows hosting to be adapted to each need.

It also adds dependencies to document. When data exists in several places, define the authoritative version, permitted exchanges and how interruptions are handled. File synchronisation alone does not replace a backup strategy.

5. Compare the full cost and required work

Request quotes over the same period, separating setup from operation:

• On premises: hardware, storage, backup power, licences, administration, backups and possible replacement.
• Cloud: subscription, storage, backups, any chargeable transfers, administration and connectivity required by users.
• Both: data migration, access control, support, recovery tests and the business impact of downtime.

The decision also depends on available skills. Specify who monitors services, applies updates and intervenes when equipment or accounts cause problems.

6. Check recovery before deciding

Ask where copies are held, who can restore them and which test will demonstrate a usable service. The hosting location alone does not prove that your data can be recovered.

The NIST IT contingency planning guide sets out an approach based on business requirements and recovery priorities. Our guide to testing backup restoration provides a practical starting point for preparing that check.

Which solution should your business choose?

Gather your priority workflows, site constraints and access needs. Then compare a local option, a hosted option and, where it meets the need, a hybrid option. Each proposal should explain its cost, dependencies and recovery arrangements.

Konsolia can help scope the project and organise your IT infrastructure in Madagascar. The first 30-minute conversation is free: describe your project and the tools your team uses.