XL Internet Services and the narrow margin of Dutch local cloud

XL Internet Services is a legacy name with current economic value

The public record around XL Internet Services B.V. does not describe a neat, stand-alone Dutch cloud company in 2026. It describes a company name, a CloudVPS operating history, an older XLS Hosting identity, an autonomous-system record that now sits under Signet B.V. in RIPE data, a PeeringDB profile that still names XL Internet Services B.V., and a customer-facing cloud path that has largely been folded into TransIP and team.blue. That does not make the company irrelevant. It makes the company a useful economic lens. The margin problem facing a Dutch small-cloud provider is not visible only in glossy product pages. It is visible in what survives after a local cloud specialist becomes part of a larger hosting group.

XL Internet Services B.V. appears in Dutch hosting directories as the company behind CloudVPS, with KvK number 24404163, a Rotterdam address at Delftsestraat 5 B, and a 2006 founding year. Hosting in Nederland lists CloudVPS under XL Internet Services B.V., gives Dutch and English as website languages, shows weekday helpdesk hours from 9:00 to 19:00, and lists older VPS packages from EUR 10.95 to EUR 174.95 per month at https://www.hostinginnederland.nl/providers/cloudvps. The same source is not a current financial filing, and its plan table is plainly historical. But it captures the old commercial shape: a Dutch VPS and cloud provider selling local infrastructure, Dutch support and a manageable technical ladder to customers who wanted more control than shared hosting without buying their own hardware.

The acquisition record explains why the direct public surface is fragmented. AKD says IT-Ernity Internet Services B.V. acquired all shares in XL Internet Services B.V. (CloudVPS) on 23 October 2014 and describes CloudVPS as a hosting company that began in 2006, grew into a European cloud provider, used OpenStack, and served financial, government, industrial, business-services and educational customers: https://www.akd.eu/cases/akd-assists-the-shareholders-of-cloudvps. CloudOrigin's 2014 transaction note adds that Rotterdam-based CloudVPS had offered virtual servers since 2007, launched a public European OpenStack cloud in 2014, and appealed especially to customers that cared about demonstrable data privacy in the Netherlands: https://www.cloudorigin.com/2014/11/15/it-ernity-acquisition-of-cloudvps/. TransIP then announced in 2018 that it acquired IT-Ernity Holding B.V., the group behind Proserve, CloudVPS, Signet, VDX, Webstekker and DDS: https://www.transip.co.uk/news/transip-and-it-ernity-join-forces/. A year later Combell and TransIP created team.blue, with TransIP Group's Dutch portfolio explicitly including TransIP, Proserve, Signet, CloudVPS and VDX: https://press.team.blue/175124-combell-and-transip-join-forces-to-create-team-blue/.

This ownership path matters because it converts a product question into a margin question. If local cloud were a high-margin standalone paradise, the old CloudVPS identity would have had less reason to become part of a larger portfolio. Instead, the record suggests a familiar story: local expertise has value, but it needs more scale, shared engineering, shared network buying, customer-base pooling and group sales reach to survive against both hyperscale clouds and ultra-cheap VPS providers. XL Internet Services is therefore not only a brand history. It is evidence that the economics of Dutch small cloud depend on whether local trust can be monetized faster than technical and support costs rise.

The useful thesis is narrow. Dutch small-cloud margin depends on six things at once: local hosting trust, Amsterdam interconnection, rack and power costs, support cost, supplier dependency, SME switching costs and substitution from hyperscalers and cheap VPS plans. XL Internet Services sits at the point where all six are visible. It had local trust through CloudVPS. It had Amsterdam network evidence through PeeringDB and RIPE. It faced a country where data centers have become politically and electrically constrained. It had customers that needed support, privacy and OpenStack familiarity, not only raw compute. It was absorbed into a group that could buy and operate at larger scale. And it now competes indirectly with a market where a buyer can compare Dutch-local promises against TransIP's current EUR 5 VPS, OVHcloud's European VPS claims, Hetzner's low-cost German and Finnish cloud, and global hyperscale platforms with enormous service breadth.

The local trust premium is real, but it is not a license to overcharge

The strongest argument for XL Internet Services was never that Dutch compute cycles are cheaper than global compute cycles. They usually are not. The stronger argument was that a Dutch cloud provider could sell control, jurisdictional comfort, support proximity and a more understandable supplier relationship. CloudOrigin's deal note says CloudVPS data remained securely hosted in the Netherlands with a Dutch company. AKD similarly emphasizes financial and government markets where cross-border protection of sensitive data is crucial. The language is deal-marketing language, but it is commercially revealing. It shows where CloudVPS thought the premium lived: customers who wanted a public or hybrid cloud but did not want an anonymous global platform to be the whole answer.

That local premium has become more, not less, relevant. The Netherlands Court of Audit reported in January 2025 that all Dutch ministries were using cloud services, that ministries did not know the type of cloud used for more than a quarter of the 1,588 services reported, and that risk assessments were missing for 84 of 126 material public cloud services: https://english.rekenkamer.nl/documents/2025/01/15/dutch-central-government-in-the-cloud. The audit was about central government, not XL Internet Services, but its conclusion changes buyer psychology across the market. It tells every serious Dutch buyer that cloud sourcing is no longer an invisible IT procurement line. It is a governance decision involving supplier concentration, service continuity, data protection, foreign access risk and the ability to understand where important workloads actually sit.

For a local provider, this is an opening. A Dutch SME, municipality supplier, healthcare software vendor, education provider or regulated services company may not need every hyperscale feature. It may need a supportable virtual environment, backups, clear Dutch or English communication, contractual confidence, and a provider that understands local compliance anxiety. A local or group-owned Dutch provider can sell the difference between "we provide a platform you can understand" and "you can choose from a thousand services and pay a specialist to manage the complexity." That difference has value.

The problem is that buyers will not pay unlimited premiums for reassurance. They compare invoices. A small software business that pays EUR 200 per month for a handful of virtual machines, backups and support can be loyal if outages are rare and support is human. The same business may reconsider if the provider cannot match basic automation, modern storage, clear APIs, snapshot tools or transparent traffic pricing. TransIP's current VPS page is useful here because it shows what a mass-market Dutch platform now treats as baseline. At https://www.transip.eu/vps/, TransIP advertises a V1 package from EUR 5 per month with 1 GB RAM, 100 GB NVMe, unlimited traffic and one snapshot; a V3 package from EUR 20 per month with 2 vCPUs, 4 GB RAM, 100 GB NVMe and unlimited traffic; and add-ons for dedicated vCPUs, disk speed, backups, offsite backups and block storage. That is not necessarily the same product as old CloudVPS. But it is the benchmark that local buyers see inside the same group ecosystem.

Local trust therefore works only when it is attached to operational substance. A Dutch company name, a Rotterdam or Eindhoven office, and a Netherlands hosting claim help win the conversation. They do not by themselves defend margin against commodity comparison. The buyer must believe that local hosting gives better control, better support, better legal fit, better migration help, better incident handling or lower total management cost. If those benefits are not visible, the local premium collapses into a price comparison, and price comparison is brutal.

Amsterdam interconnection is an asset that also raises expectations

XL Internet Services' network evidence points toward Amsterdam rather than a diffuse European footprint. PeeringDB lists "XL Internet Services B.V." at AS35470, also known as "xlshosting", with a website override of xlshosting.nl, content network type, nine IPv4 prefixes, zero IPv6 prefixes in the displayed count, a 1-5Gbps traffic level, mostly outbound traffic, European geographic scope and an open peering policy: https://www.peeringdb.com/net/3157. The same PeeringDB record lists interconnection facilities at Equinix AM1/AM2 in Amsterdam, Equinix AM3 at Amsterdam Science Park and euNetworks Amsterdam. Its API gives the same three facilities and no current public exchange connection rows for that profile: https://www.peeringdb.com/api/net/3157.

That record should not be over-read. PeeringDB is operator-maintained and, in this case, not freshly updated across every field. The current RIPE view also shows AS35470 under Signet B.V., not under a standalone XL Internet Services organization. The RIPE aut-num object at https://rest.db.ripe.net/ripe/aut-num/AS35470.json lists AS35470, as-name XL-AS, organization ORG-SI6-RIPE, status assigned, Signet maintainers, a created date of 29 November 2006, a 2020 last-modified date, and a transit-provider remark naming IT-Ernity Internet Services through AS49685. RIPEstat's overview currently describes the holder as "XL-AS Signet B.V." and says the resource is announced: https://stat.ripe.net/data/as-overview/data.json?resource=AS35470. RIPEstat's routing-status data for 3 July 2026 reports 46 IPv4 prefixes, 11 IPv6 prefixes, 26,624 IPv4 addresses and full visibility among its RIS peer sample: https://stat.ripe.net/data/routing-status/data.json?resource=AS35470.

The key point is not that XL Internet Services is a large network. It is not. The key point is that the old CloudVPS and XLS Hosting story sits in the Dutch interconnection system. Amsterdam is a powerful place to host because it concentrates networks, content providers, carriers and data centers. AMS-IX says its Amsterdam platform shows 905 connected networks and a 15.034 Tb/s peak at https://www.ams-ix.net/ams, and its connected-networks page lists 905 total connected ASNs, 1,093 customer ports and 906 IPv6 peers: https://www.ams-ix.net/ams/connected-networks. In April 2026, AMS-IX announced a new 15 Tb/s traffic peak and said the number of 400G ports had grown 65 percent over the previous year: https://www.ams-ix.net/ams/news/ams-ix-hits-new-traffic-peak-at-15-terabit-per-second.

That context helps local cloud providers. A Dutch provider near Amsterdam can offer low-latency access to Dutch eyeballs, business customers, content networks and European routes. It can buy transit and peering in a dense market. It can place backup, storage and compute in facilities that customers and auditors recognize. It can market the Netherlands as a digital hub rather than as a peripheral server location. For SMEs with Dutch customers, that is a real product attribute.

But interconnection also raises expectations. If a provider invokes Amsterdam, customers expect professional network behavior: redundant paths, sensible routing, IPv6 readiness, DDoS handling, rapid abuse response, clear maintenance communication and no mysterious congestion. The buyer may not understand every route table, but the buyer knows that "Amsterdam" is supposed to mean speed and resilience. That makes the operational bar higher. A cheap provider in a remote bargain location can sometimes be excused for occasional rough edges. A Dutch cloud provider using the country's interconnection reputation cannot.

This is a margin trap. Amsterdam gives a local provider better sales language and better technical options, but the same density lets customers compare alternatives more easily. A customer can choose a Dutch or nearby European server from OVHcloud, a German or Finnish low-cost instance from Hetzner, an Amsterdam VPS from a budget provider, a hyperscale region, or a higher-service Dutch managed provider. Interconnection lowers switching friction at the network layer even when application migration remains hard. That means local trust must be paired with enough operational differentiation to keep the buyer from treating Amsterdam as a commodity feature.

Rack and power economics are the hidden tax on the local cloud promise

The Netherlands is a world-class digital infrastructure market, but it is not a low-friction power market. CBS reported that data centers consumed 5,100 GWh of electricity in 2024, equal to 4.6 percent of the Netherlands' total electricity consumption, and that roughly 200 data centers were present, most around Amsterdam: https://www.cbs.nl/en-gb/news/2025/51/data-centres-consume-4-6-percent-of-the-netherlands-electricity. CBS also reported that large data centers consuming more than 10 GWh accounted for around 90 percent of the total electricity supplied to data centers. Emerce, carrying a Dutch Data Center Association release, said Dutch colocation capacity reached 924 MW in 2024, expected investment exceeded EUR 1.4 billion for 2025, and ongoing challenges included grid congestion and permitting: https://www.emerce.nl/wire/tien-jaar-state-the-dutch-data-centers-decennium-bloei-blokkades.

Those facts directly affect small-cloud margin. A provider like XL Internet Services did not only sell software. It sold the right to consume power, cooling, rack space, cross-connects, storage, transit, support and hardware amortization in the Netherlands. Every customer buying a small virtual server consumed a fraction of a rack, a fraction of a storage cluster, a fraction of a support team and a fraction of the provider's network risk. When power prices, grid constraints, facility prices, hardware costs or labor costs rise, the provider must either increase prices, reduce margin, consolidate platforms, automate harder or push customers into standardized packages.

TransIP's current infrastructure page illustrates the kind of cost base modern Dutch VPS customers now expect to be normal. At https://www.transip.eu/vps/infrastructure/, TransIP says its VPS platform uses network storage so a virtual server can start on a different hypervisor after a failure, automatic migrations to balance load, SSD and NVMe storage with ZFS checksums, Ceph storage clusters and three copies of all data. Its network page says VPSs are delivered in one of two availability zones, Amsterdam AMS0 or Delft RTM0, each with its own 2N power supply and network, connected by an encrypted 200Gb/s backbone; it also says its core and edge network is distributed over those zones plus Interxion and GlobalSwitch satellite locations: https://www.transip.eu/vps/network/.

That is good engineering. It is also expensive engineering. Three copies of data mean storage efficiency is deliberately sacrificed for resilience. Live migration, multiple zones, encrypted backbone capacity, BGP-based IP fabric, private networking and high-availability load balancers are not free. They require hardware, skilled staff, monitoring, testing and spare capacity. The provider cannot run at 100 percent utilization without degrading the very reliability it sells. In local cloud, a healthy gross margin is partly the price of unused capacity kept available for failure, migration and customer bursts.

This creates a hard commercial problem. SME customers often believe a virtual machine is a small thing and should therefore be cheap. Technically, one small instance may be small. Economically, the platform that keeps thousands of small instances available is not small. The margin comes from averaging usage, selling add-ons, limiting support intensity, standardizing packages and retaining customers long enough to recover acquisition and hardware costs. A customer who buys only a low-end instance, generates support tickets, uses heavy outbound traffic and leaves after a few months can destroy margin. A customer who buys several instances, backups, private networking, support and stays for years can make the same platform profitable.

XL Internet Services' acquisition path suggests the latter customer mix matters. The CloudOrigin and AKD notes emphasize public, private and hybrid cloud, managed services, financial and government customers, and single-contract service and SLA advantages. That is not pure cheap-VPS language. It is a move up the value ladder, away from commodity cycles and toward customers that value reliability, privacy, support and integration. The economic question is whether enough such customers exist to cover the Dutch facility and support cost base without making prices so high that they invite substitution.

Support is not overhead; it is the product local buyers actually buy

Small-cloud providers often talk about compute, storage and network. Many customers are really buying support. A Dutch SME that chooses CloudVPS, TransIP, Proserve, Signet or another local provider may have a technical staff member, but not a 24-hour infrastructure team. It may understand its application but not Ceph behavior, route troubleshooting, backup recovery, kernel issues, DDoS mitigation, mail reputation or the practical difference between a snapshot and a disaster-recovery plan. When something breaks, the customer does not want a global queue and a generic answer. It wants someone who knows the platform and can explain the problem in concrete terms.

The old forum evidence is weak but useful as a signal. A 2012 Tweakers thread about choosing a VPS host includes users comparing CloudVPS, TransIP, DirectVPS, Tilaa, Linode and Hetzner. One user says not to stare only at specifications and instead look at service-level agreements, resource allocation and oversubscription. Another says they had three business VPSs at CloudVPS and were positive, including how CloudVPS responded to a storage-network performance issue. A third says CloudVPS, formerly XLS Hosting, thought along with customers and responded quickly, while adding that if this did not matter a buyer could choose a cheaper foreign host with better-looking specifications: https://gathering.tweakers.net/forum/list_messages/1522354. This is not audited customer research. It is chatter. But it captures the exact tradeoff: local providers sell judgment and response, not only cores and RAM.

That support advantage is expensive. Human support does not scale like virtual machines. A well-designed control panel can reduce tickets, and automation can make standard tasks painless, but complex incidents still consume senior engineer time. Worse, better support can attract customers who require more help. If a provider is known for thinking along with customers, it may win SMEs with complicated needs, half-managed workloads and legacy applications. Those customers pay more, but they also ask more. Margin depends on pricing the service boundary clearly.

CloudVPS' movement inside team.blue illustrates one way to manage this. TransIP's 2020 blog about Dutch team.blue brands says CloudVPS was focusing on OpenStack while VPS service would run through TransIP, a fellow group member whose energy was focused on its VPS platform: https://www.transip.nl/blog/team-blue-nl-brands/. The same post says CloudVPS had been founded in 2006 in Rotterdam, was one of the first European providers to embrace OpenStack, built high availability into instances, used redundant components, stored data three times and offered three availability zones. In economic terms, the group divided the product surface: let TransIP standardize high-volume VPS, let CloudVPS specialize in OpenStack, let Proserve handle managed IT, let Signet handle connectivity. That division tries to keep support and engineering aligned with customer willingness to pay.

This is the right direction, but it reveals why standalone margin is hard. If every small provider must build a full control panel, full cloud platform, full support team, full network function, full compliance posture and full product documentation, the cost base is heavy. If those functions can be shared across a group, the margin equation improves. The downside is brand dilution. Customers who once chose XL Internet Services or CloudVPS for local identity may now see a larger group architecture and wonder which team actually owns their issue. Group scale is economically useful, but trust must be preserved at the support boundary.

Supplier dependency is the central risk beneath the local-control story

Local cloud providers sell control, but they also depend on suppliers. They depend on data centers for power, cooling and space. They depend on hardware vendors for servers, disks, network gear and replacement parts. They depend on software communities and vendors for virtualization, OpenStack, storage, operating systems and security updates. They depend on carriers and peering partners for reachability. They depend on domain registries, payment providers, certificate authorities and abuse channels. A local cloud company is local at the customer interface, but its production function is a chain.

This matters because the local-control premium can be undermined if the provider is visibly dependent on a few upstream choices. The RIPE record for AS35470 makes this concrete. The AS35470 object does not now present a standalone XL Internet Services organization; it points to Signet B.V. and Signet maintainers, with an IT-Ernity transit-provider remark. PeeringDB still names XL Internet Services B.V., but its public record is old enough to require caution. IPLocate's CloudVPS page says CloudVPS or XLS Hosting IP addresses are 100 percent in the Netherlands, but its provider classification splits CloudVPS address space across AS20857 Signet B.V. / TRANSIP-AS at 77.9 percent and AS35470 Signet B.V. / XL-AS at 22.1 percent: https://www.iplocate.io/data/hosting-providers/cloudvps. IPinfo's public AS35470 page likewise labels the current network as Signet B.V. and shows many RPKI-valid prefixes, with AS48185 team.blue NV listed as a peer: https://ipinfo.io/AS35470.

None of that is a problem by itself. It is normal after acquisitions for network records, brands, routing and product ownership to consolidate. But it changes what customers should ask. The due-diligence question is no longer simply "does XL Internet Services host this in the Netherlands?" It is "which group company operates the network, which platform hosts the workload, which support desk owns the incident, which legal entity contracts with the customer, which facilities carry the risk, and what happens if the group migrates products again?" For a small customer, those questions may be too heavy. For a regulated buyer, they are essential.

Supplier dependency also cuts into margin. If a provider controls its own facilities, it carries capital risk but has more operational discretion. If it colocates, it converts capex to recurring facility cost and supplier negotiation. If it uses group network services, it gains scale but loses some direct independence. If it depends on OpenStack and Ceph expertise, it must retain scarce engineers or accept service risk. If it uses commodity hardware, it gets purchase flexibility but faces replacement and performance variation. If it buys premium hardware, it raises depreciation. Every supplier choice changes the price floor.

The local provider's economic advantage is not eliminating dependency. It is making dependency legible and manageable for customers. A Dutch SME may prefer a local provider precisely because the provider abstracts away data-center, network and software complexity while still offering human accountability. But if the provider becomes too opaque, the advantage weakens. Transparency about platform ownership, support escalation, data location, backup geography and network operation is not just compliance language. It is a way to defend price.

SME switching costs protect margin until they become resentment

SME cloud customers are easier to win than to move. A small business may start with one VPS, add mail, add DNS, add backups, add a private network, add firewall rules, add monitoring, add certificates, add object storage and then forget how much of its daily operation depends on one provider. That creates switching costs. The customer can leave in theory. In practice it must inventory applications, copy data, reduce DNS time-to-live values, test compatibility, schedule downtime, update firewall rules, rebuild backups, change billing and hope no old integration breaks.

For local providers, switching costs protect margin. If the customer is satisfied, renewal is cheaper than acquisition. The provider can sell add-ons. The customer becomes less sensitive to a few euros per month if the platform is stable and support is trusted. That is why local hosting groups care about control panels, APIs and adjacent services. A customer that buys domains, web hosting, VPS, backups, object storage and support from one group is easier to keep than a customer who uses only one disposable virtual machine.

But switching costs become dangerous when customers feel trapped. The ACM market study page says the Dutch competition authority examined whether the cloud-services market functions properly and whether risks to prices, quality and innovation arise from provider practices or market structures: https://www.acm.nl/en/publications/market-study-cloud-services. The public page is broad, but the study sits in a European regulatory debate about interoperability, portability and cloud concentration. For XL Internet Services' market, the lesson is simple: lock-in can be a margin asset only while customers experience it as convenience. Once customers experience it as hostage-taking, the provider loses trust.

This is especially important for SMEs. A small customer has limited bargaining power and limited technical capacity. If backups are hard to export, private-network constructs are undocumented, support is slow, or pricing changes appear without a clear rationale, the customer may not leave immediately. It may, however, stop expanding with the provider, move new projects elsewhere and warn peers. The margin on the existing account survives for a time while future growth disappears. That is how a provider can look stable from a revenue-retention view while losing market relevance.

The better strategy is to make switching possible but unnecessary. OpenStack historically helped CloudVPS tell that story because it is an open cloud platform rather than a proprietary hyperscale service catalog. The CloudVPS claim to OpenStack expertise, high availability and Dutch hosting gave customers a reason to believe they were buying both local trust and some degree of architectural portability. In practice, OpenStack skills are still specialized, and moving workloads is never automatic. But the message is commercially useful: customers can trust a provider more when it does not appear to profit from making exit impossible.

This is where small-cloud providers can beat hyperscalers with a narrower promise. Hyperscale clouds offer enormous breadth, but that breadth can become complexity. A Dutch local provider can offer fewer services, clearer boundaries and a stronger service relationship. The provider says, in effect: you can understand this platform, you can talk to us, your data is in the Netherlands or Europe, and we will not push you into a service maze. That promise supports margin if it remains true.

Hyperscale and cheap-VPS substitution attack different parts of the same margin

The substitution threat is two-sided. Hyperscalers attack from above by offering breadth, global reach, managed databases, AI services, identity tools, compliance programs, developer ecosystems and procurement familiarity. Cheap VPS providers attack from below by offering enough compute at a price that makes local support look expensive. XL Internet Services and similar Dutch providers sit in the middle. The middle can be profitable, but it is squeezed.

OVHcloud's Netherlands VPS page is a good example of the lower-middle substitution offer. It markets VPS hosting for the Netherlands with European data centers, a 99.9 percent SLA, root access, unlimited data traffic outside some Asia-Pacific regions, anti-DDoS included on all VPS solutions, and bandwidth up to 2 Gbit/s for high data exchange applications: https://www.ovhcloud.com/en/vps/vps-nederland/. Hetzner's cloud page sells "affordable cloud hosting services", GDPR compliance, low-cost shared resources and dedicated-resource options for higher workloads: https://www.hetzner.com/cloud/. Hetzner also says its cost-optimized cloud instances are hosted in Germany and are designed for test, development, smaller projects and private blogs: https://www.hetzner.com/cloud/cost-optimized. ProfitServer markets Netherlands VPS locations including Amsterdam InterDC, Equinix AM11 and Serverius Meppel with prices from USD 2.9: https://profitserver.net/vps/netherlands/.

Those offers do not replace a trusted Dutch managed cloud in every case. A EUR 3.79 or USD 2.9 plan is not the same as a well-supported OpenStack platform, a private cloud engagement or a managed environment with a Dutch account team. But it changes the buyer's reference price. Once cheap VPS exists, the local provider must explain why EUR 20, EUR 50, EUR 100 or more per month is rational. The answer can be backup quality, storage reliability, support, compliance, local jurisdiction, migration help, integrated networking or predictable performance. If the provider cannot explain the difference, the customer will treat the premium as waste.

Hyperscalers create a different challenge. They may be more expensive in direct virtual-machine comparison, especially once egress, support and operational complexity are included. But they offer services a small local provider cannot match. A developer who wants managed AI, serverless functions, global edge distribution, advanced data analytics or a mature marketplace may choose AWS, Azure or Google Cloud even if a local VPS is cheaper. The Dutch local provider cannot win by pretending to have a hyperscale catalog. It must win where customers want fewer moving parts, better locality, simpler invoices and a support relationship.

The Netherlands Court of Audit's concern about cloud understanding is therefore useful to local providers, but not enough. Buyers can respond to cloud risk by choosing local providers, but they can also respond by professionalizing hyperscale procurement, using managed service partners, adopting sovereign-cloud overlays, or splitting workloads. Local providers must be part of a credible architecture, not merely a protest against foreign platforms.

That is why the old CloudVPS story remains interesting. It did not sell only commodity VPS. It sold OpenStack, high availability, Dutch hosting and privacy confidence. The group then paired it with TransIP's mass VPS, Signet's connectivity and Proserve's managed IT. That is the middle-market defense: own a specific, explainable slice of the buyer's stack and cooperate with adjacent capabilities. The standalone provider that tries to be cheap VPS, private cloud, managed service provider, connectivity provider and hyperscale alternative all at once may not have enough margin to do any of them well.

The durable margin is in trust plus operational proof, not nostalgia

XL Internet Services B.V. is not a simple "then and now" company profile. The old CloudVPS identity has been absorbed into a larger Dutch and European hosting group, while the network record shows legacy and group consolidation. The important question is not whether the old brand can be revived in isolation. It is what the XL Internet Services record says about durable local-cloud margin.

The answer is that trust still sells, but only when converted into operational proof. Dutch hosting trust comes from local data location, clear contracts, credible support, understandable risk boundaries and the ability to explain supplier dependencies. Amsterdam interconnection gives a provider a strong technical base, but it also places the provider in a comparison-rich market. Rack, power and labor costs set a price floor that cheap VPS marketing does not reveal. Support is the core product for many SMEs, but it must be priced and bounded. Supplier dependency is inevitable, but it must be transparent. Switching costs protect revenue, but only while customers feel respected. Hyperscale and cheap-VPS substitution are permanent, so the local provider must know which workloads it is not trying to win.

For XL Internet Services' current directory profile, the most defensible reading is that the company represents a Dutch cloud lineage rather than an independent growth story. It is tied to CloudVPS' early local-cloud and OpenStack position, to IT-Ernity's consolidation strategy, to TransIP and team.blue's group scale, and to Signet-linked network operations. That lineage has value because it shows how local hosting trust can survive as part of a larger portfolio. It also shows the price of survival: narrower specialization, shared infrastructure, brand integration and less standalone visibility.

The next 6 to 18 months will not be decided by whether Dutch SMEs still like local providers. Many do. It will be decided by whether local providers can make the premium legible. A buyer must be able to see why a Dutch platform costs more than a bargain VPS and why it is simpler or safer than a hyperscale account. The evidence must be visible in uptime, backup recovery, support quality, security posture, data-location clarity, migration assistance, network performance and honest communication about what the service does not do.

If local providers get that right, XL Internet Services' legacy is still commercially relevant. It shows that a Rotterdam-founded cloud specialist could create enough technical and trust value to be acquired, integrated and carried into a broader Dutch hosting stack. If they get it wrong, the same history reads differently: a reminder that standalone small cloud is squeezed between scale economies above, bargain compute below and facility costs underneath. The margin is there, but it is narrow. It belongs to providers that can turn local trust into measurable service advantage before the invoice invites comparison.