An island cloud, not a hyperscale rival The most important thing to understand about cloud.mu is that it is not trying to be “the Mauritian AWS.” Public evidence points to a more grounded, and more economically plausible, business: a locally assembled cloud and hosting platform selling web hosting, VPS, backup, domains, dedicated servers, reseller services, and a thin layer of managed convenience to customers who care about three things hyperscale cloud is structurally bad at in small island markets—jurisdictional familiarity, local support, and predictable latency to Mauritian users. Its pitch is explicit: infrastructure “hosted locally in Mauritius,” fast local access, and support by a real local team. Its price book is equally explicit: low-entry shared hosting, very cheap Linux VPS, Acronis-based backup, reseller packages, and dedicated servers priced at a clear premium in Mauritius relative to South Africa. That is not a hyperscale profile. It is a small-market infrastructure utility with retail packaging.
That distinction matters because the central commercial question is not whether cloud.mu can beat hyperscalers at cloud computing. It cannot, and it is not set up to try. The real question is whether a Mauritian platform can reliably sell enough “island advantages” to offset the island’s structural disadvantages. Those advantages are real but narrow: local data residency under Mauritian law, lower in-country latency, some trust premium in a jurisdiction that markets itself as orderly and compliant, and easier hand-holding for SMEs and local institutions that do not want to buy infrastructure from a distant self-service console. The disadvantages are also real and, in the long run, harsher: a population of roughly 1.25 million, limited large-enterprise depth, expensive international bandwidth, exposure to submarine-cable geography, high fixed operating costs spread over a small domestic base, and public-sector procurement patterns that tend to concentrate at state or telco scale rather than at boutique-hosting scale.
So the “Island-Cloud Problem” is not a technical mystery. It is an economics problem. Local cloud in Mauritius can be commercially useful. It can even be strategically valuable. But it is valuable in the way a ferry service is valuable on an island: because it solves a specific local need better than distant alternatives, not because it becomes the ocean itself. cloud.mu’s challenge is to collect enough recurring revenue from those specific local needs before the very things that make it attractive—locality, intimacy, manual support, low-latency proximity—are eroded by cheaper offshore tooling, better connectivity, or customers deciding that “good enough” offshore is fine after all.
On the evidence available in public, cloud.mu looks commercially real, technically non-trivial, and strategically bounded. It has its own ASN, its own prefixes, public looking-glass infrastructure in Mauritius and Johannesburg, visible peering at the Mauritius Internet Exchange and NAPAfrica Johannesburg, and a locally framed retail catalog. That is enough to distinguish it from a mere white-label web-hosting shop. But the same public evidence also shows that its “sovereignty” is softer than marketing language implies. The platform sits on external transit, external data-centre facilities, external control-panel and backup software, and external submarine routes. Even where the servers are local, some of the risk is not. That is the island-cloud contradiction in one sentence.
Who cloud.mu appears to be The corporate identity is more revealing than the homepage. cloud.mu’s public-facing contact page names Hosted Ltd as the registered company, with an office in The Dot Building in Moka. But its privacy policy still identifies the operator as DataKeepers Ltd, registration number C18158096, and its refund-policy page still uses the DataKeepers name and an older address in The Core Building in Ebène. Mauritius Revenue Authority VAT records help reconcile the discrepancy: the same registration number, C18158096, appears under Hosted Ltd. The simplest reading is that DataKeepers Ltd has been renamed Hosted Ltd, while parts of the legal and billing stack still carry older branding. That is not unusual for a small infrastructure firm, but it is economically meaningful: it suggests a real operating business that has changed skin without fully rebuilding its compliance surfaces, which usually happens in firms that are growing incrementally rather than through heavily managed corporate process.
The network side reinforces that the company is more than a storefront. BGP records show AS328699, registered to DataKeepers Ltd, active since July 2020, with five upstreams and multiple originated IPv4 and IPv6 prefixes. The same records list the website as cloud.mu, the ASN name as cloud-mu, and a Mauritian address in Ebène. The organization also publishes a public looking glass and appears in PeeringDB under the cloud.mu name with The Core Building address in Ebène. In other words, whatever the legal rename, the network personality was built as DataKeepers and is being sold to the market as cloud.mu. That gives the company a harder asset than a domain and a support inbox: it controls IP space and routing policy under its own ASN. In the hosting business, that is a meaningful threshold.
There is also an intriguing South African shadow in the public record. AS328699 lists AS328170 DataKeepers (Pty) Ltd as one of its upstreams, and the AFRINIC WHOIS block for the Mauritian network references David Venter as an administrative contact. LinkedIn shows a Cape Town–based DataKeepers firm focused on disaster recovery, cloud backup, virtual servers, and DRaaS, with cloud.mu shown among similar pages. That does not prove ownership. It does, however, strongly suggest some operational or corporate kinship between the Mauritian cloud.mu platform and a South African DataKeepers business. Economically, that matters because it changes how one should interpret cloud.mu. It may not be a purely domestic startup born from Mauritian demand. It may instead be a Mauritian market edge of a wider South African infrastructure and backup competence stack. Public records do not fully resolve the cap table, but they do make the “standalone local shop” story look incomplete.
That incompleteness is visible elsewhere. cloud.mu’s website claims that it “own[s] and manage[s]” its entire infrastructure, but the wording on the broader site is carefully phrased as “hosted securely in local Mauritius data centers,” not “in our own data centre.” Public peering records show cloud.mu present at MIXP through Rogers Capital Data Center, and the company’s PeeringDB and older legal addresses point to office buildings in Ebène rather than to a named carrier hotel owned by the firm itself. The available evidence therefore supports a narrower conclusion than the homepage rhetoric: cloud.mu appears to control its network resources and service stack, while colocating in third-party Mauritian facilities. That is still significant. It just means the scarce asset is not a building permit or a Tier IV shell. It is a routable, peered, supportable local hosting platform assembled inside someone else’s physical shell.
This distinction is central to the economics. A company that owns local IP space, manages routing, maintains peering sessions, and runs public looking-glass infrastructure has more control than a reseller. But a company that colocates in another operator’s data centre instead of owning the facility also has lower fixed capital burdens and lower physical moat. That is not a bug. In Mauritius, it may be the only sane model at cloud.mu’s apparent scale. The market is too small to make “own the whole stack” attractive unless one is a telco, a state facility, or a diversified infrastructure group. cloud.mu’s apparent structure therefore looks like an adaptation to Mauritian economics, not a failure of ambition.
What it sells and where the margin sits The catalog tells you what kind of business this is. cloud.mu sells shared web hosting, WordPress hosting, Linux VPS, Windows VPS, cloud backup, reseller hosting, SSL certificates, domain registration, Microsoft licences, and dedicated bare-metal servers. The entry points are low: shared hosting from Rs289/month, Linux VPS from Rs299/month, and cloud backup from Rs259/month. Windows VPS starts higher, with explicit Windows licensing baked into pricing, and dedicated servers are a big jump-up product. This is a classic laddered recurring-revenue design: pull in very small customers cheaply, upsell them to reseller or VPS plans, and keep a few heavier users on dedicated servers and backup storage. It is economically closer to an ISP-adjacent hosting business than to an enterprise cloud platform.
The gross-margin profile of these products can be inferred, even if not directly observed. Shared hosting is normally the fattest layer in a business like this because one machine can support many low-usage customers, and the value is a bundle of convenience—email accounts, DNS, SSL, cPanel, backups, support—rather than raw compute. Domains are thinner: cloud.mu sells .MU and other domains, but the MU-NIC accredited registrar list does not include cloud.mu, while it does include Register MU and other registrars. cloud.mu’s own domain prices for .mu and related local namespaces are visible on its cart pages, which strongly suggests it is acting as a registrar reseller or channel rather than as a registry-facing registrar of record. That means domains are likely lead-generation and account-stickiness tools, not a rich standalone profit pool.
The price relationship is revealing. Register.mu lists .mu registration at $64 for one year and transfer at $114; cloud.mu’s own pricing page shows .mu registration at Rs2,800, renewal at Rs2,900, and transfer at Rs5,600. Those numbers are close enough to suggest that cloud.mu is not “manufacturing margin” on domains in any deep way. Domain services here look more like an attachment sale: if the customer buys the domain, they are easier to keep inside the hosting account, easier to upsell to email or DNS support, and harder to churn away. In small hosting markets, that matters more than the raw domain spread itself.
VPS and dedicated servers are a different story. They look like the company’s attempt to capture higher average revenue per account without abandoning the self-service SMB segment. Linux VPS pricing is aggressive enough to win local developers, agencies, and small business systems that need predictability more than hyperscale elasticity. Windows VPS is priced in a way that makes licensing visible rather than hidden, which is typical of providers selling into small firms that still run Windows-dependent applications but do not want to navigate Microsoft licensing complexity themselves. There is a Microsoft licences section for SQL Server Web Edition sold on top of hosted Windows servers. Economically, that is useful because it converts a commodity VM into a higher-margin compliance-and-convenience bundle. You are not just selling RAM and SSD; you are selling “we handled the annoying Microsoft part.”
Cloud backup is its own logic. cloud.mu markets backup explicitly with Acronis branding, “unlimited devices,” and storage tiers up to 20 TB. In managed-services economics, backup is attractive because it is sticky, contractual, and emotionally defensive: customers buy it to avoid catastrophe, not to chase experimentation. That typically lowers churn. But the margin is not pure. Acronis itself positions its cloud product as an MSP platform, and cloud.mu is visibly packaging that kind of service. So backup margin here likely depends on how effectively cloud.mu arbitrages local trust and support against upstream software costs and storage costs. If utilization is poor or support is labour-heavy, backup can become a deceptively expensive promise to maintain. If managed well, it becomes recurring annuity revenue with strong lock-in.
The dedicated-server pages expose the island economics most bluntly. cloud.mu sells the same dedicated server families in Mauritius and South Africa, and the Mauritian location is materially more expensive. For the entry dedicated product shown publicly, the Mauritius price is Rs13,499/month versus Rs7,499/month in South Africa. That gap is the article’s thesis in numeric form. The company itself is telling the market that “locality” is a premium product, either because local infrastructure costs are higher, local capacity is scarcer, or both. If a customer only wants raw compute, South Africa is much cheaper. If the customer pays the Mauritius premium, they are buying something other than raw compute—usually latency to Mauritian users, local legal location, or local comfort. cloud.mu’s own pricing therefore confirms that its true product is not cloud capacity; it is the locality wrapper around cloud capacity.
This is why the business model looks commercially literate, even if narrow. The company does not appear to assume it can monetize “enterprise digital transformation” at Mauritius Telecom scale. Instead, it monetizes proximity and simplification. It sells self-service hosting with human support, domains with DNS hand-holding, local backup with a familiar vendor stack, VPS with clear upgrade paths, and reselling infrastructure to agencies that want to host customers under their own branding. The reseller pages explicitly market custom nameservers, custom branding, WHMCS integration, and the ability to set one’s own prices. That is not just technology. It is channel strategy. In a small market, indirect distribution through local agencies and freelancers can matter more than trying to build a large direct salesforce.
The network says this is real infrastructure, but not sovereignty in the strong sense cloud.mu’s strongest public evidence is not its marketing copy. It is the routing record. AS328699 originates multiple IPv4 and IPv6 prefixes, appears at MIXP with 10 Gbps links, and also appears at NAPAfrica IX Johannesburg with 10 Gbps connectivity. BGP.tools shows five upstreams: Kaldera, DataKeepers (Pty) Ltd, Mauritius Telecom, Hurricane Electric, and Vodacom. That combination matters. It proves that cloud.mu is operating a substantive network edge with local peering and external reach, not simply reselling a server rack under someone else’s ASN. In small markets, having one’s own ASN and routing policy is a hard strategic threshold because it lets the operator shape traffic paths, multi-home transit, and present itself credibly to business customers who know enough to ask where the packets really go.
The Mauritian part of the story is real. At MIXP, cloud.mu appears with two visible port entries at Rogers Capital Data Center. The presence there means that local traffic to other Mauritian networks can often stay local rather than tromboning out to distant transit. That is exactly how a Mauritian cloud operator creates observable value against offshore hosting: not by inventing superior servers, but by reducing the path length and coordination friction for domestic traffic. The site’s claims of “lowest possible latency” to Mauritian users are therefore at least directionally supported by peering data. If your customers are mostly in Mauritius, local peering really can be worth money.
But the same network record punctures any grander sovereignty narrative. cloud.mu also peers in Johannesburg and relies on South African and international upstreams. Mauritius Telecom’s own business materials highlight the island’s subsea-cable ecosystem—SAFE, LION/LION2, MARS, and T3—and the T3 cable itself is documented as connecting Mauritius to South Africa, with Liquid Telecom as landing partner in Amanzimtoti. In other words, Mauritius does not live in splendid network isolation. It sits in a subsea geography whose resilience is better than it once was, but still regionally entangled. cloud.mu’s Johannesburg presence and South African upstreams make operational sense for performance and reach. They also mean that the platform’s promise of local sovereignty is only partially about route independence. If the South African side of the system wobbles, Mauritian service quality can still suffer.
This is not theoretical. cloud.mu’s own announcements disclose a 29 August 2024 “network connectivity issue” caused by an outage with one of its upstream providers, which intermittently affected international connectivity to its Mauritius data-centre facility for roughly two and a half hours while services remained operational but less reachable. The more dramatic anecdote came in May 2026, when South African providers were hit by sustained DDoS attacks. MyBroadband reported that Datakeepers also suffered outages; local LinkedIn chatter complained that “cloud.mu [was] down” for hours and linked the issue to attacks in South Africa; and Mauritian press coverage of l’express framed the outage as affecting services hosted on cloud.mu. Some of that evidence is informal and should be treated as such. But taken together, it changes the commercial interpretation. The whole point of buying “local cloud” is supposed to be insulation from external complexity. The public outage trail shows that locality reduced some risks but did not remove regional infrastructure exposure.
The Ubuntu and other Linux mirror sponsorships are a subtler piece of network evidence. SysAdmin Journal documents that cloud.mu sponsored server and bandwidth for Mauritius-hosted mirrors for Ubuntu, Fedora, AlmaLinux, and openSUSE, and that the Ubuntu country mirror for Mauritius points to a cloud.mu subdomain. This matters for two reasons. First, it strongly suggests that cloud.mu has enough spare bandwidth, enough operational competence, and enough local peering relevance to support a nationally useful cache-and-distribution function. Second, it reinforces the company’s role as a domestic traffic localizer. Mirrors do not just create goodwill; they reduce international dependency for software updates. In that narrow sense, cloud.mu does create real digital-infrastructure value for the island. The catch is that mirror sponsorship is also a reminder that this is a bandwidth-and-caching business as much as a cloud business. That is strategically useful, but it is not the same as being a broad enterprise compute platform.
So what does the network evidence actually prove? It proves that cloud.mu is a real operator with its own network identity, visible peering, routable allocations, and practical local Internet integration. It proves that “local hosting” is not just a slogan pasted over an offshore reseller account. It does not prove ownership of a Mauritian data-centre building, immunity from regional outages, or sovereign independence in the stronger geopolitical sense implied by some marketing around data sovereignty. Locality here is a service-quality and commercial-trust variable. It is not autarky.
Mauritius as market, regulator and buyer Mauritius is large enough to sustain local digital infrastructure, but small enough that the addressable market is always the central strategic constraint. The country has roughly 1.25 million people and a diversified economy with ICT and financial services among the important sectors. That is enough to produce a meaningful long tail of websites, SMEs, agencies, schools, NGOs, and local applications. It is not enough to generate hyperscale-grade utilization by domestic demand alone. For a local hosting platform, that means the operating game is to keep boxes full enough, support efficient enough, and churn low enough that modest recurring revenue can cover a stubborn fixed-cost base in power, colocation, transit, software licences, staffing, and spares.
This is where Mauritius’ regulation and policy environment cut both ways. The country’s Data Protection Act 2017 does not create a sweeping legal obligation to keep all personal data in Mauritius. Section 36, as summarized in official and quasi-official materials, allows transfer of personal data abroad where the controller or processor provides appropriate safeguards, where the data subject gives explicit consent, or where other specified grounds apply. The National Data Strategy talks more assertively about data sovereignty and notes that data classification frameworks should be harmonized with government-cloud or data-localization policies. But the public policy posture is more nuanced than a simple “local hosting required” rule. Economically, that means cloud.mu’s sovereignty pitch is usually a soft advantage, not a hard mandate: it simplifies comfort, due diligence, and local accountability, but it does not automatically foreclose offshore alternatives for private-sector customers.
That nuance is important because local-cloud narratives often exaggerate legal lock-in. In Mauritius, the better framing is that local hosting can make regulated or cautious customers feel safer, can help keep data under a familiar legal regime by default, and can reduce the compliance conversation around cross-border transfers. That has commercial value. But it is not the same as a sovereign monopoly. A bank, lawyer, insurer, clinic, or media company can still decide that an offshore provider plus contract language and governance controls are good enough. In a small market, that means the cloud.mu pitch lives or dies on organizational preference, not only on law. Preferences are weaker moats than mandates.
The public sector is even less open than the sovereignty story might suggest. Mauritius already has a substantial state-hosted cloud position through the Government Online Centre, which official assessments describe as the central government data centre and “Government Cloud” providing hosting services and IaaS for public systems such as e-procurement. Government strategy documents continue to assume that public digital services are hosted on the Government Cloud, and the Public Sector Investment Programme includes explicit funding lines for the GOC Tier IV Data Centre, the GOC Data Centre, and related hosting infrastructure. This makes the state both a promoter of cloud and a vertically integrated customer of its own cloud. For an operator like cloud.mu, that narrows rather than expands the obvious path into public demand.
The tender record confirms the ceiling. In the 2023 procurement for hosted services of a data centre for a disaster-recovery site for the Government Online Centre, the two visible bidders were EMTEL Ltd and Mauritius Telecom Ltd, with EMTEL’s first option quote materially below Mauritius Telecom’s. cloud.mu was not visible in that bid opening. One should be careful: absence from a tender opening does not prove inability. But combined with the public-sector GOC architecture and the tendency of large tenders to draw telcos and infrastructure incumbents, it suggests that cloud.mu’s realistic government-adjacent role is probably not “host the state.” It is more likely to pick up smaller institutions, quasi-public niches, subcontracting opportunities, or overflow needs that do not require carrier-scale comfort. In procurement-heavy island markets, that distinction is a major commercial boundary.
The competitive map inside Mauritius also caps the strategic space. Mauritius Telecom markets my.t Cloud, private cloud, colocation, backup-as-a-service, and two data centres including a Tier IV site in Rose Belle. Kaldera markets cloud, hosting, backup, managed infrastructure, and says it has three data centres. Mauritius Computing Services has long marketed itself as a cloud and hosting provider in the country, with historical press positioning it among early movers. These are not imaginary competitors. They are the incumbent categories that capture large-account trust: telco, ISP, long-established enterprise IT integrator. cloud.mu therefore seems to occupy the space between them and pure offshore self-service. That can be a viable niche. It is also exactly the kind of niche that becomes crowded whenever incumbent providers decide they want the same SME and mid-market wallets more aggressively.
Where the moat exists and where it leaks cloud.mu’s moat, such as it is, does not start with “Mauritius” by itself. Plenty of firms can put a rack in Mauritius. The moat starts with combination. Public evidence suggests cloud.mu combines a visible local network presence, a retail-grade self-service catalog, human support, a domain and DNS wrapper, low-friction onboarding, and community embed. That combination is harder to replicate than any single feature. The company sponsors local developer and software-craftsmanship events, appears in community posts as a hosting sponsor, and turns up in practical tools like country Linux mirrors. It also appears in customer-side footers such as Capetech, which explicitly says it is “Powered by cloud.mu.” That is not the same as enterprise referenceability, but it is exactly how a small infrastructure brand wins mindshare in a limited domestic market: by becoming the default recommendation among developers, agencies, and small-business operators who want somebody local to call.
There is also a trust moat in being visibly Mauritian without being purely bureaucratic. Large offshore clouds intimidate some buyers because they require self-service competence and governance maturity. Large local incumbents intimidate other buyers because they look expensive, slow, or overbuilt. cloud.mu positions itself in the middle: local enough to answer the phone, structured enough to publish incident reports and run a visible network, and cheap enough to feel approachable. The Digital Marketing Specialist job post on LinkedIn is revealing in that respect. It frames the company as interested in driving organic and paid search growth “for our group and select customers.” That sounds like a business trying to behave not only as a hoster but as part of the local digital go-to-market stack. In small markets, that adjacency can matter as much as the technology. If you help the customer launch, not just host, you become harder to displace.
But the moat leaks in four places.
The first leak is law. As noted above, Mauritius’ data-protection regime supports careful cross-border transfer rather than absolute local retention. cloud.mu can sell reassurance, but it cannot rely on a blanket legal compulsion that forces businesses onto Mauritian infrastructure. Where customers are sophisticated, the sovereignty premium becomes a negotiation variable rather than a regulatory necessity.
The second leak is utilization. A small country produces small aggregate demand. Shared hosting can work because of oversubscription, but the heavier parts of the stack—backup repositories, virtual infrastructure, and especially dedicated servers—need enough paying usage to support local power, space, inventory, and support. cloud.mu’s own price gap between Mauritius and South Africa is evidence that utilization and cost are harder locally. If a customer is price-sensitive and does not need Mauritian residency, the offshore or regional option becomes hard to resist, even on cloud.mu’s own menu.
The third leak is connectivity dependence. Local hosting helps domestic latency, but the island still depends on submarine cables and regional routing. cloud.mu’s Johannesburg footprint, South African upstreams, and the public outage trail mean that some of the operational risk sits below the “hosted in Mauritius” label. That matters especially for customers buying local hosting for resilience rather than just for latency. If the sales pitch is “stay local and stay safe,” customers will eventually ask what happened when South African infrastructure was under DDoS stress. The answer from the public record is not fatal, but it is not comforting either.
The fourth leak is enterprise procurement. Bigger buyers care about certifications, vendor risk, disaster recovery architecture, contract frameworks, and institutional permanence. Mauritius Telecom and Kaldera can wrap cloud and hosting inside broader connectivity, managed security, and data-centre propositions. Government has its own cloud. Large integrators and telcos already occupy the “trusted infrastructure” seat for many serious procurements. cloud.mu may be able to win around the edges, but public evidence does not show it yet holding the commanding heights of Mauritian enterprise infrastructure demand. The visible customer signals point more toward communities, websites, SMEs, agencies, and selected business workloads than toward a slam-dunk presence in high-end regulated infrastructure contracts.
So where, precisely, is the durable value? It is in being the credible local default for the middle of the market: not the state, not the hyperscaler-native multinational, but the Mauritian organization that wants a website, email, VPS, backup, or app hosting under a familiar jurisdiction with a local support path and decent domestic performance. That is a genuine business. It is also a business that creates strategic value beyond its own revenue line. Linux mirrors, local IX presence, and locally reachable hosting infrastructure all reduce frictions in the domestic digital economy. cloud.mu therefore has strategic value for Mauritius even if it never becomes a huge company. The trouble is that strategic value for a country is not the same as large economic rents for the operator. Many strategically useful infrastructure firms remain only modestly profitable because they solve collective problems in markets too small to overpay them.
What the public record still cannot answer For all the visible evidence, there are crucial things the public record does not settle.
It does not settle the exact ownership structure. The rename trail from DataKeepers Ltd to Hosted Ltd is strongly supported by public records, and the South African DataKeepers connection is suggestive. But the public sources reviewed here do not clearly show whether cloud.mu is a subsidiary, sister company, franchise, closely allied operator, or simply a Mauritian business using a South African partner or founder network. That matters because ownership affects available capital, procurement credibility, and resilience options. If cloud.mu is backed by a wider group, its commercial durability is stronger than its website alone suggests. If it is mostly a lean local operator, then concentration risk is higher.
It does not settle customer concentration. Public customer signals show community sponsorship, some visible hosted sites, media reliance in at least one press account, and a reverse-DNS footprint that suggests a wider tenant base. But none of that tells us whether the company has one giant anchor customer, fifty mid-sized retainers, or thousands of tiny accounts. That is perhaps the single most important missing commercial fact. A local host with diversified small accounts can survive churn better than one exposed to a few large logos. Conversely, a few larger recurring backup or dedicated-server contracts could explain how a small-market operator affords visible network investments. The ledger of public evidence is not rich enough to answer this confidently.
It does not settle facility architecture in sufficient detail. We can see local data-centre use, IX presence via Rogers Capital Data Center, and a Mauritius/South Africa location split in dedicated-server offerings. We cannot fully see rack count, redundancy design, storage architecture, power contracts, or whether South Africa is merely an alternative sales location or an actual failover spine for some Mauritian services. In an island market, those distinctions are not footnotes. They can determine whether “local cloud” means “primary in Mauritius and secondary abroad,” “primary in third-party colocation with regional spillover,” or simply “some products are local, some are not.”
It does not settle the economics of support. cloud.mu emphasizes support heavily—phone, live chat, email, real people—which is often exactly what the local market wants. But support is labour, and labour is margin. Without staff counts, ticket volumes, or renewal rates, one cannot tell whether support is the reason cloud.mu wins business or the reason cloud.mu may struggle to scale profitably. The existence of a marketing role posting hints at active demand generation, but there is no public evidence here showing whether customer acquisition cost is low because of word of mouth, or high because the local market is expensive to educate and price-sensitive once approached.
Finally, the public record does not settle whether cloud.mu can move upmarket without losing its economics. The website’s dedicated servers, backup tiers, and Microsoft licensing offer the ingredients of a move from “web host” toward “serious SMB infrastructure provider.” But Mauritius is full of firms that can handle websites and not many that can clear enterprise procurement hurdles. The decisive evidence would be certifications, audited uptime or facility standards, evidence of disaster-recovery exercises, named enterprise wins, and repeat public-sector or regulated-industry contracts. That evidence is thin in the material reviewed here. The sober conclusion is therefore not that cloud.mu lacks strategic value. It is that its strategic value is currently easier to prove than its ability to harvest large enterprise rents from that value.
Evidence ledger Source name URL Source type What it supports What it does not prove Why it matters economically Citation cloud.mu homepage https://cloud.mu/ Official company page Core positioning around local hosting, local support, full product family, and “own and manage” infrastructure rhetoric It does not prove facility ownership or financial performance This is the firm’s demand-side narrative and reveals the premium it tries to charge for locality cloud.mu contact page https://cloud.mu/contact/ Official company page Current public operator name as Hosted Ltd and office address in Moka It does not prove legal history or shareholding Establishes present operating identity and local commercial presence cloud.mu privacy policy https://cloud.mu/legal/privacy-policy/ Official legal page Operator identified as DataKeepers Ltd with registration number C18158096 It does not prove why branding changed or when Shows legal-stack lag and supports the rename/rebrand interpretation Mauritius Revenue Authority VAT list https://www.mra.mu/download/ListofVATRegPersons.pdf Official government record Registration number C18158096 appears as Hosted Ltd It does not prove all historical names or beneficial ownership Helps reconcile legal identity; rename evidence matters for vendor diligence and continuity BGP.tools AS328699 https://bgp.tools/as/328699 Network registry / measurement ASN, prefixes, upstreams, Mauritian address, network age, and DataKeepers branding It does not prove customer count, on-net utilization, or facility ownership Confirms cloud.mu is a real network operator, not just a reseller bgp.he.net AS328699 https://bgp.he.net/AS328699 Network registry / measurement Company website, looking glass, IX participation, and originated prefixes It does not prove service quality or commercial success Validates the infrastructure layer and multi-homing/peering posture MIXP PeeringDB record https://www.peeringdb.com/ix/1508 IX / Peering record cloud.mu presence at MIXP, with ports at Rogers Capital Data Center It does not prove exclusive colocation or full architecture Local peering is a real low-latency advantage and a hard operational asset in Mauritius cloud.mu looking glass https://lg.cloud.mu/ Official network tool Public routing/diagnostic surface in Mauritius and Johannesburg It does not prove uptime or capacity utilization A public looking glass is a marker of serious network operations and transparency Domain pricing pages https://my.cloud.mu/cart.php?a=add&domain=register and https://register.mu/cart.php?a=add&domain=register Official company / official registrar pages .MU pricing at cloud.mu and Register.mu, showing likely reseller-style domain economics They do not prove gross margin or registry-side contract terms Shows domains are probably a retention and bundling tool, not a deep rent source MU-NIC registrars list https://www.nic.mu/registrars/ Official registry record Accredited .MU registrars include Register MU but not cloud.mu It does not prove cloud.mu has no reseller arrangement or indirect access Important for understanding whether cloud.mu controls a scarce registration permission or merely channels it Product pricing pages https://my.cloud.mu/store/web-hosting, https://my.cloud.mu/store/linux-vps, https://my.cloud.mu/store/cloud-backup, https://cloud.mu/dedicated-servers/ Official company pages Retail price ladder across shared hosting, VPS, backup, and Mauritius vs South Africa dedicated servers They do not prove realized selling prices, discounts, or margins The public price book reveals business model, segment focus, and the premium charged for Mauritian locality ICTA commercial licensees https://www.icta.mu/licences-issued/ Official regulator page Public ICTA telecom-license listing is populated by telcos/ISPs; searches for Hosted Ltd and DataKeepers return no match in the page text It does not prove definitively that the company has no other approval or arrangement Suggests the moat is not an obvious telecom regulatory franchise but an operational-market position Mauritius Government cloud records https://ppo.govmu.org/Documents/Publications/Maps/MAPS_Assessment_Mauritius_e-proc_vol1.pdf and https://mof.govmu.org/Documents/budget_2025_2026/2025_26_PSIP.pdf Official government report / budget GOC operates the Government Cloud; state continues to invest in GOC data-centre infrastructure They do not prove total exclusion of private suppliers from all state workloads Shows the state is itself an infrastructure incumbent, limiting the private local-cloud addressable market DR hosting tender opening https://cpb.govmu.org/Documents/pub_openings/N7_CPB_24_2022-Hosted%20Services%20of%20a%20data%20centre.pdf Official procurement record Visible bidders for GOC disaster-recovery hosting were EMTEL and Mauritius Telecom It does not prove cloud.mu was unwilling or unable to bid Indicates where large sovereign-style contracts gravitate: to telco-scale players Mauritius data-transfer regime https://www.fscmauritius.org/media/105843/the-data-protection-act-2017.pdf and https://dataprotection.govmu.org/Documents/NDS_final.pdf Statute / official policy PDF Cross-border transfer is permitted with safeguards/consent; sovereignty is a policy theme, not a blanket localization mandate It does not prove how every regulator or sector interprets edge cases Shows cloud.mu sells soft compliance and comfort, not an absolute legal necessity for most private buyers Outage and regional-dependence trail https://my.cloud.mu/announcements/view/2024-08, https://mybroadband.co.za/news/cloud-hosting/648362-south-african-infrastructure-providers-wiped-off-the-internet-by-sustained-ddos-attacks.html, https://lexpress.mu/s/une-cyberattaque-massive-en-afrique-du-sud-558137 Official status page / press / local press cloud.mu disclosed upstream-related disruption; South African DDoS reporting and local press linked regional attacks to Mauritian service impact It does not prove the exact internal fault path for every outage Commercially crucial because it tests the strength of the “local insulates you” thesis
What would change the island-cloud bet Three facts would materially change the commercial view.
The first would be hard evidence that cloud.mu has durable enterprise anchors—for example, named long-term contracts in finance, healthcare, media, education, or regulated industry; credible third-party certifications; or repeated wins in quasi-public procurement. That would shift the company from “real local infrastructure merchant” to “institutional platform,” and it would make the margin story more attractive.
The second would be hard evidence on ownership and capital backing. If public filings eventually showed that Hosted Ltd / cloud.mu is backed by a larger South African or regional infrastructure group with meaningful balance-sheet support, some of the fragility implied by small-market economics would weaken. If the opposite were true—if it is effectively a very lean local operator—the concentration and resilience risks would look sharper.
The third would be a better view of how much of the locality premium customers will still pay as connectivity keeps improving. cloud.mu’s own Mauritius-versus-South Africa price split says the premium exists today. The long-run question is whether Mauritian customers continue to buy it for sovereignty, latency, and support—or whether they gradually decide that the island’s cloud should be local only at the edge, while the real workloads live elsewhere. That is the true Island-Cloud Problem. The public evidence shows cloud.mu has built a serious answer to it. The public evidence does not yet show that the answer scales indefinitely.