EVANZO e-commerce GmbH and the capital recovery test behind local network control

Summary

• EVANZO e-commerce GmbH has a verifiable German hosting and number-resource footprint: official EVANZO pages identify a Berlin company selling domain and webhosting packages, while RIPE records show a Local Internet Registry organisation, AS42730, IPv4 and IPv6 allocations, active originated routes and upstream dependence on larger networks.
• The investment case is conditional rather than automatic. EVANZO can justify local network control if the footprint lowers unit cost, improves service continuity, protects scarce IPv4 capacity and keeps SME hosting customers attached to bundled domains, webspace, email and DNS. If customers mainly compare on headline price and simplicity, larger hosting groups, partner server products and global cloud platforms put a hard ceiling on pricing power.

Germany defines both the opportunity and the constraint

EVANZO's economic problem starts with geography. The company is legally and commercially anchored in Germany, not in a borderless cloud abstraction. Its imprint lists EVANZO e-commerce GmbH at Riedemannweg 60 in Berlin, names Johann Dasch as managing director, and gives the Berlin-Charlottenburg commercial register reference HRB 117331B. The RIPE member listing and RIPE database record the same Berlin address and identify Germany as the serviced area.

That matters because the business case for local network control is strongest when the provider can sell German continuity, German support, familiar contracting and data-location comfort to small and medium-sized customers that do not want to assemble infrastructure from several suppliers.

The same geography also limits the upside. EVANZO is not presented by its own public pages as a pan-European network operator or a sovereign cloud platform with a dense enterprise sales motion. The homepage sells domain packages, webhosting, homepage packages and a Linux VPS offer supplied through partner company 1blu. The webhosting overview segments the offer into Basic, Profi and Business packages for beginners, ambitious private users and business websites. The contact page gives weekday support hours from Monday to Friday, 8:00 to 16:30.

Those facts describe a real operating business, but they also point to a bounded market: German-language SME hosting, domains, websites and email rather than high-margin dedicated connectivity or complex managed network outsourcing.

That boundary is where the capital recovery test becomes useful. Local number resources and autonomous-system control can make a hosting provider more durable. It can hold addresses, choose upstreams, set routing policy, keep DNS and web customers close to its own operating stack, and avoid depending entirely on another provider's IP plan. But those advantages are only valuable if they support revenue that customers recognize.

A small business buying a domain bundle or a webhosting package may care about uptime, email deliverability, support and cancellation flexibility; it may not pay an explicit premium because the provider holds its own LIR account or originates routes under its own AS number. EVANZO therefore has to recover the cost of control indirectly, through lower churn, better allocation of scarce addresses, operating flexibility and a package that is simple enough to survive price comparison.

The evidence does not support a heroic growth story. It supports a more modest and more testable thesis: EVANZO has a local infrastructure footprint that can be economically rational if it is used as a cost and control layer beneath recurring domain and hosting revenue. The risk is that the same footprint becomes stranded overhead if the retail proposition remains commodity-priced, if server demand is routed to partner offers, or if larger providers use scale to compress hosting margins faster than EVANZO can defend its customer base.

The company is a hosting and domain business before it is a carrier story

The public identity is clear enough. EVANZO's own site is branded around hosting. Its navigation leads with domain packages, webhosting, contact, FAQ, terms, privacy, imprint, contract termination and withdrawal. The homepage highlights a "Profi-Homepage XXL" package, domain products, basic homepages, professional homepages, business homepages and domain packages. It also advertises Linux VPS products, but the text says those are powerful Linux VPS from partner company 1blu. That distinction matters.

EVANZO's own core surface is shared hosting, domains, email, webspace and website tools; a more server-heavy virtual infrastructure product is visibly associated with another company.

The legal pages reinforce that reading. EVANZO's terms state that the company provides services for domain and hosting customers who conclude domain and hosting contracts through the EVANZO portal. The terms cover domain registrations, domain transfers, webspace, email services, IP address assignment, customer obligations and abuse handling. They do not read like a bespoke managed network outsourcing agreement. The privacy policy describes website use, customer accounts, orders for webhosting products or webspace, payment processing, cookies, order data retention and TLS protection of the order process.

That is the compliance footprint of an online hosting retailer.

The product set is broad inside that category. EVANZO's domain packages include .de domains, domain forwarding, email forwarding, optional DNS access and Let's Encrypt certificates on the higher plan. The Basic webhosting page advertises up to five included .de domains, up to 30,000 MB of webspace, Let's Encrypt, a homepage builder, up to 1,500 email accounts and up to 20 MySQL databases. The Profi page stretches the package up to 12 included .de domains, 120,000 MB of webspace, 8,000 email accounts and 80 MySQL databases.

The Business page offers up to 20 included .de domains, 120,000 MB of webspace, included traffic, 8,000 email accounts, 80 MySQL databases and cronjobs on a three-month contract term.

This is a familiar hosting economics model. A provider bundles a low-cost domain and website presence with enough email, database and webspace capacity to make the customer reluctant to move. The gross margin is not created by one feature. It is created by filling shared infrastructure, keeping support cost under control, minimizing fraud and abuse losses, and retaining customers long enough for acquisition and provisioning costs to amortize. In that model, network control is not the product a buyer sees. It is a production input beneath the visible service.

The central question is therefore whether EVANZO's hidden production input improves the visible offer. If address control improves deliverability, if routing control reduces outages, if scarce IPv4 resources allow dense hosting without expensive purchases, and if local support gives customers enough confidence to stay, then the footprint has economic value. If the buyer experience is indistinguishable from any other budget host, then larger providers can copy the visible bundle while spreading network and platform costs across far more accounts.

Public network records show control, not just branding

EVANZO is not merely a reseller with a hosting website. The public RIPE record identifies ORG-EeG3-RIPE as EVANZO e-commerce GmbH, country DE, organisation type LIR, with the Berlin address, phone, email, registration reference and maintainer entities. The entity was created in 2005 and last modified in May 2026. That is a durable number-resource record, not a marketing claim.

The resource evidence is also material. RIPE inverse records show multiple IPv4 allocation entities associated with EVANZO: 195.90.192.0 to 195.90.255.255, 178.254.0.0 to 178.254.63.255, 87.238.192.0 to 87.238.199.255 and 185.195.100.0 to 185.195.103.255. They also show an IPv6 allocation, 2a00:6800::/29, and the autonomous system AS42730. The AS entity is named EVANZOAS, was created in April 2007 and is marked assigned.

RIPE route objects and RIPEstat announced-prefix data show that EVANZO-originated prefixes were visible in BGP in the late-June to July 11, 2026 window, including 195.90.192.0/18, several slices of 178.254.0.0/18, 87.238.192.0/21, 185.195.100.0/23, 185.195.102.0/23 and 2a00:6800::/32.

That is enough to say EVANZO has a real routed footprint. Hurricane Electric's BGP view of AS42730 reports 11 originated and announced prefixes, 10 IPv4 and one IPv6, with RPKI originated valid counts matching the prefix count and no originated invalids shown on that page. IPinfo's third-party view classifies AS42730 as hosting, reports 35,584 IPv4 addresses and estimates 217,599 hosted domains on the ASN. Those third-party numbers should not be read as audited customer counts or revenue, but they support the idea that the ASN is being used for hosting activity rather than sitting as a dormant registration.

The caveat is equally important. Number-resource control is evidence of operational capability, not proof of economic success. A provider can originate prefixes and still fail to earn adequate returns if utilization is low, if support costs are high, if abuse management consumes margin, or if customers buy only the cheapest packages. BGP records also do not reveal whether the network is run from owned hardware, colocated equipment, leased platforms, partner facilities or a mix. They show address and routing control. They do not show gross margin, churn, customer acquisition cost, facility contracts or server depreciation.

The correct interpretation is disciplined. EVANZO has the kind of resource base that can support a local hosting provider: RIPE LIR status, IPv4 capacity, IPv6 allocation, an AS number and visible routes. The next question is whether the retail business attached to that footprint can monetize it against substitutes.

The scarce asset is IPv4, but scarcity alone is not value creation

The strongest asset in the record is not the company name or the website bundle. It is the IPv4 inventory and the right to manage addresses under a RIPE LIR framework. RIPE's own IPv4 run-out page states that its remaining IPv4 pool was exhausted in November 2019 and that networks in its region can no longer receive new unused IPv4 addresses from RIPE. Growth often requires transfer-market purchases, address sharing technologies such as CGNAT, or IPv6 deployment. For a hosting provider, that makes address control strategically useful even if it is not visible on an invoice.

A domain and shared-hosting provider can often place many websites behind shared addresses, but IPv4 still matters. Mail reputation, dedicated IP requests, legacy customer configurations, name-server infrastructure, VPN use, customer control panels, SSL edge cases, abuse containment and server products can all create demand for clean and manageable address space. EVANZO's terms reserve flexibility over IP addressing: the company says IP addresses it assigns may be changed with one day's notice and customers have no claim to a particular address. That contractual language protects the provider's operating flexibility.

It lets EVANZO manage scarcity and abuse risk without promising every customer permanent address control.

That flexibility is economically rational, but it has a customer-experience tradeoff. A customer that needs stable IP addressing, strict deliverability, complex DNS or application-level continuity may see a one-day address-change right as a limitation. A small website customer may not care. A more technical customer may compare the EVANZO package with VPS, root server or cloud providers that expose more infrastructure control. The same clause that protects EVANZO's unit economics can push higher-value technical customers toward alternatives if they need stronger guarantees.

RIPE's 2026 charging scheme shows that the formal LIR fee itself is not the largest cost. The annual contribution per LIR account is EUR 1,800, with separate charges for certain independent resources and ASN assignments, plus a sign-up fee for new members. That is a meaningful fixed compliance and membership cost for a small provider, but it is not the full cost of network control. The larger cost sits in engineering, monitoring, abuse handling, routing policy, upstream contracts, server operations, security work, customer support, replacement hardware and management time.

IPv4 scarcity creates option value. EVANZO can use addresses to keep hosting density under its own control, avoid buying every address on a transfer market, and preserve flexibility as customers change. But scarcity does not automatically translate into pricing power. If the customer buys "website plus email" and sees several providers offering broadly similar packages, the IPv4 value is captured only if it lowers EVANZO's cost or improves retention. The asset earns its cost when it supports durable recurring revenue. It fails when it merely sits behind a commodity price list.

The retail price envelope is tight

EVANZO's visible pricing leaves little room for narrative premium. The domain page shows Basic-Domain at EUR 1.99 per month and Profi-Domain at EUR 19.99 per month, including VAT. The Basic webhosting packages are listed at EUR 26.99 and EUR 29.99 per month. The Profi range runs from EUR 29.99 to EUR 39.99 per month. The Business range runs from EUR 39.99 to EUR 49.99 per month. Contract terms vary by package, with Business packages on three-month terms and Profi packages on six-month terms, and the pages describe cancellation with one month's notice to the end of the contract term.

That price envelope is large enough to support a small hosting business if utilization is high and support is efficient. It is not large enough to absorb unmanaged complexity. A EUR 39.99 or EUR 49.99 monthly plan that includes many domains, large webspace allocations, email accounts, databases, traffic and support can be profitable only if actual usage is much lower than theoretical capacity for most customers. That is the normal shared-hosting assumption: the package advertises headroom, but the provider earns money because most small-business sites do not consume the full theoretical resource bundle every month.

The risk is that support and abuse do not scale as elegantly as disk space. A small business website with email can generate password resets, deliverability complaints, malware cleanup, DNS misconfiguration tickets, billing questions and domain-transfer issues. EVANZO's contact page gives limited weekday phone support hours, which may help contain cost, but it also limits the premium-service story. The terms promise minimum availability of 99% per year, excluding announced and planned maintenance. That is a baseline continuity promise, not a high-availability enterprise commitment.

A 99% annual floor allows more downtime than customers in critical applications would tolerate, while commodity website customers may accept it if the price and package are attractive.

The pricing also has to compete with simpler server substitutes. EVANZO's homepage sends Linux VPS demand to 1blu, and 1blu's own VPS page advertises entry pricing that starts materially below many shared-hosting packages. AWS Lightsail publishes simple Linux/Unix virtual server plans starting at a low monthly dollar price. A technical buyer who wants server control can choose a VPS or cloud instance, then add DNS, email or a managed control panel separately. A non-technical buyer may prefer an all-in-one shared-hosting bundle.

EVANZO's pricing power therefore depends on being simple for the second buyer without losing too much of the first buyer to VPS and cloud substitutes.

This is why visible growth and value creation must be separated. Adding hosted domains can look impressive while revenue per domain remains thin. Selling larger bundles can raise headline monthly revenue while support cost and capacity promises consume margin. The value-creating outcome is not "more domains" by itself. It is more retained accounts that use the platform predictably, require manageable support, and allow EVANZO to fill its network and hosting infrastructure at a return above the cost of capital and operations.

Upstream dependence narrows the control claim

AS42730 gives EVANZO routing control, but it does not make EVANZO independent of larger networks. The RIPE aut-num entity lists import and export relationships with AS25394, AS3356 and AS8220. RIPEstat's neighbour view for AS42730 shows AS3356 and AS8220 as observed neighbours. RIPEstat identifies AS3356 as Level 3 Parent, LLC and AS8220 as Colt Technology Services Group Limited; AS25394 is MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG. Hurricane Electric's BGP view similarly shows Level 3 Parent and Colt among observed peers, while the RIPE policy entity still lists MK Netzdienste.

This is a classic regional-provider structure. EVANZO controls its AS and originates its prefixes, but global reach depends on upstream transit or related interconnection supplied by larger networks. That is not a flaw. Almost every smaller hosting network buys upstream connectivity. The economic issue is bargaining power. If a provider has only a narrow set of upstream choices, transit price, technical quality, route diversity and outage exposure become supplier risks. If it has more carriers, exchange ports and facility options, local control becomes more defensible.

Public PeeringDB lookup did not return a network profile for AS42730. That absence does not prove EVANZO lacks exchange connectivity; not every network publishes a PeeringDB profile and records can be incomplete. It does mean the public evidence for open peering policy, facilities, exchange points and traffic ratios is thin. For an investor, customer or competitor analysis, that matters. EVANZO's public resource record is stronger than its public interconnection disclosure.

Supplier dependence can still be compatible with value creation if EVANZO uses upstreams intelligently. A small hosting provider can benefit from having its own AS even when it buys transit: it can multihome, move traffic, renumber less often, maintain its own route objects, publish RPKI authorizations and separate address control from any one carrier. But the advantage depends on execution. Two larger upstreams may provide adequate resilience for a hosting footprint if contracts, capacity and monitoring are well managed.

They may be limited public evidence if the company sells higher-criticality applications or if a single routing problem can disrupt a large share of revenue.

The concrete proof would be operational, not rhetorical: multiple active upstreams, documented failover, clean route-origin validation, low packet-loss history, stable prefix announcements, transparent incident handling and customer retention during outages. The public BGP record gives a partial positive signal, especially on originated prefixes and RPKI validity shown by third-party views. It does not show capacity headroom or the economics of transit contracts.

Customer concentration is unknown, so hosted-domain signals must be handled carefully

EVANZO does not publish customer count, revenue, churn, gross margin, account concentration or segment mix on the public pages reviewed. That silence is normal for a private German hosting provider, but it limits the strength of any economic conclusion. The analysis has to work from product design, network evidence and third-party signals rather than audited business metrics.

IPinfo estimates 217,599 hosted domains across AS42730 and identifies 5,678 IP addresses associated with hosted domains. That is a useful market signal because it suggests the ASN is attached to a meaningful shared-hosting footprint. It is not a customer count. One paying customer can hold many domains; one domain can be parked, dormant, bundled or unmanaged; some hosted domains may be low-revenue or legacy accounts; and third-party domain attribution can misclassify or lag. The same IPinfo page tags the ASN as hosting, reports little day-night traffic variation typical of hosting or datacenter networks, and shows German geography.

Those signals support the footprint thesis, but they do not tell us whether EVANZO earns attractive margins.

The package design implies customer concentration risk may be more dispersed than enterprise hosting, but that cannot be confirmed publicly. Shared webhosting and domain packages typically serve many small accounts. That can reduce single-customer dependency but increase operational noise: many small customers, many low-value tickets, many domains, many renewal decisions, and ongoing abuse screening. If EVANZO has a long tail of small accounts paying between EUR 1.99 and EUR 49.99 per month, the business depends on process discipline.

Billing, renewals, support scripts, abuse handling and automation may be more important to margin than any single large customer.

There is also market-dependence risk. EVANZO's public offer is heavily tied to websites, domains and email. Eurostat's 2025 enterprise cloud statistics show that more than half of EU enterprises used paid cloud services, with email, office software and file storage among the most common use cases. That cuts both ways. It validates demand for outsourced digital infrastructure, but it also means customers increasingly expect cloud-style self-service, bundled productivity tools, integrated security and elastic capacity. A traditional hosting provider can survive if it serves customers who want simpler website presence.

It loses relevance if those customers shift their whole workflow to SaaS suites and no longer view webhosting as a separate strategic purchase.

The evidence that would reduce uncertainty is straightforward: paying account counts, renewal rates by product tier, average revenue per account, support tickets per account, abuse rates, domain renewal retention, email-deliverability metrics and the share of revenue tied to EVANZO-owned network resources. Without those facts, hosted-domain counts should be treated as directional evidence of activity, not proof of economic strength.

Larger providers make simplicity the real battleground

EVANZO's real competition is not one single carrier. It is a menu of alternatives that make the buyer's life simpler. Large hosting groups can bundle domains, email, site builders, certificates, performance features, support and cloud upgrades under one brand. Server specialists can sell low-cost virtual machines with fast provisioning. Global cloud platforms can offer elastic compute, managed databases, storage and developer ecosystems. Managed-service providers can hide infrastructure entirely and sell outcomes.

IONOS is the clearest scale comparison in the German and European context. Its 2025 annual report says revenue rose to EUR 1.3169 billion and total customers reached 6.63 million. It describes a portfolio covering domain registration, web hosting, website builders, dedicated servers, productivity tools and cloud solutions, supported by infrastructure with more than one million processor cores across 29 data centers. It also lists brands such as STRATO, arsys, fasthosts, home.pl, World4You, united-domains and InterNetX.

EVANZO does not need to match that breadth to survive, but it has to compete against the buyer expectation that such scale creates: lower friction, more integrations and a path from basic website to cloud workload without changing suppliers.

1blu is especially relevant because EVANZO points server demand there. The 1blu imprint lists the same Berlin address and Johann Dasch as managing director. Its VPS page advertises Linux VPS plans with KVM or Virtuozzo options, SSD storage, traffic included and a low entry price. Its root-server page advertises virtual root servers on KVM with fixed resources, Frankfurt am Main as server location and traffic included. For EVANZO, this can be a sensible group or partner strategy: EVANZO keeps the domain and shared-hosting proposition, while more infrastructure-heavy server demand is handled by a related specialist offer.

The risk is that it also reveals where the more technical customer may go instead of buying deeper EVANZO service.

AWS Lightsail adds the global substitute. It offers simple virtual private server pricing and packaging for users who do not want the full complexity of AWS. A buyer who can manage a small server can compare EVANZO's hosting bundle with a cloud VPS plus domain and email tools. That comparison does not automatically favor the cloud, especially for non-technical SMEs. But it sets a pricing reference. If a buyer sees compute, storage and transfer available at low monthly prices from a global platform, a local provider must justify its premium through convenience, support, data location, bundled domains, email or trusted continuity.

The strategic lesson is blunt: local control is not enough. It must be converted into customer simplicity. EVANZO's advantage, if it has one, is not being bigger than IONOS or AWS. It is being sufficiently local, sufficiently bundled and sufficiently operationally steady for German SME customers that prefer an all-in-one website, domain and email provider. The danger is being neither premium enough to charge for service nor scaled enough to win a pure price contest.

Regulation and abuse handling are cost centers as well as trust signals

Hosting providers sell continuity, but they also absorb legal and operational friction. EVANZO's imprint includes a contact point under Regulation (EU) 2021/784 for terrorist content online, with German and English listed as communication languages for that specific channel. Its terms give EVANZO the right to block access to unlawful or abusive customer homepages or servers until unlawful components are removed, and to terminate in cases of illegal or abusive use.

The privacy policy identifies EVANZO as data controller, lists data collected during website visits and orders, describes customer-account creation, payment processing and ten-year retention of address, payment and order data due to commercial and tax requirements.

These details matter economically. Abuse handling is not a side issue for a hosting network. Malware, spam, phishing, copyright complaints, unlawful content, compromised CMS installations and domain disputes can consume support time and damage IP reputation. If a provider controls its own addresses, reputation problems land directly on its own resource base. That creates both incentive and cost: EVANZO can manage its own hygiene, but it must also police customers effectively enough to keep prefixes useful for email and hosting.

The 99% availability floor in EVANZO's terms also reveals the risk allocation. It is a clear baseline promise, but not a premium enterprise service-level agreement. Planned and announced maintenance is excluded. Free services may be discontinued. EVANZO reserves broad rights to change or improve services when doing so benefits the customer base, server stability, security, performance, legal compliance or license compliance. These clauses are rational for a shared-hosting operator because they protect the platform. They also show that the product is designed for mass hosting, not bespoke high-availability engineering.

From a buyer's perspective, regulation and abuse handling can become a trust advantage if EVANZO communicates competence and resolves issues quickly. German address, German contact, clear legal notices and local support can matter to smaller customers who do not want to navigate a global platform. From a cost perspective, the same obligations can erode margin if many low-price accounts produce high compliance workload.

The strategic test is whether EVANZO can automate enough of the risk. Strong onboarding, domain validation, abuse monitoring, backups, malware scanning, email reputation management, clear escalation paths and predictable support workflows can turn compliance into a manageable cost. Weak automation turns the same obligations into margin leakage. The public record shows EVANZO acknowledges the regulatory environment and sets customer obligations. It does not show how efficient the control system is.

The partner structure may be rational, but it complicates the story

EVANZO's homepage sends Linux VPS demand to 1blu, and the 1blu imprint shows common address and management with 1blu GmbH. This is not a minor footnote. It suggests a product architecture in which EVANZO handles one part of the hosting funnel while related or partner offers handle VPS, root server and dedicated server demand. That can make economic sense. A provider can avoid duplicating product engineering, billing complexity and support specialization across separate brands. It can also segment buyers: EVANZO for domain and shared-hosting customers, 1blu for more server-oriented customers.

The complication is capital recovery. If EVANZO owns or controls valuable network resources, but higher-intensity server products are marketed under another brand, then EVANZO's own article-level thesis must be limited. The question is not whether the wider group can recover infrastructure cost through multiple brands. The question here is whether EVANZO e-commerce GmbH's local-control footprint earns its cost through the EVANZO domain and hosting proposition. The public evidence does not reveal internal cost sharing, intercompany contracts, asset ownership, facility leases or customer migration paths between EVANZO and 1blu.

The partner structure can be an advantage if it reduces stranded cost. EVANZO does not have to present every server SKU under its own brand. A customer outgrowing shared hosting can be referred to 1blu, keeping the relationship within a related commercial orbit. The customer sees a path from simple web presence to VPS or root server without EVANZO having to dilute its own positioning. If billing, support and infrastructure are coordinated behind the scenes, this could improve lifetime value.

It can also weaken EVANZO's pricing power. A buyer who arrives for a domain package and then needs a VPS may learn that the server product is not EVANZO's own flagship offer. The buyer may then compare 1blu not only with EVANZO, but with Hetzner, IONOS, AWS Lightsail and other server providers. The more technical the customer becomes, the more likely the buying decision shifts from local hosting convenience to price, performance, control-panel quality, API support, backups, uptime history and data-center location.

The right conclusion is conditional. Partner routing is not evidence of weakness by itself. It may be an efficient portfolio decision. But it means EVANZO's defensible economics likely sit in bundled SME hosting, domain retention and resource-backed continuity rather than in a broad stand-alone cloud expansion story.

The risk is mistaking routed scale for pricing power

The most tempting mistake is to look at 35,584 IPv4 addresses, more than 200,000 hosted-domain signals and active BGP announcements and call that scale. It is scale of a kind, but not necessarily the kind that creates pricing power. Hosting economics can produce large technical counts with thin revenue per entity. A parked domain, a low-traffic website, a legacy email account and a business-critical application do not carry the same willingness to pay.

EVANZO's visible price points suggest a business that competes on value bundles rather than bespoke premium service. Included domains, included traffic, large stated email-account allowances and large webspace numbers are useful sales tools, but they can create an arms race. Competitors can match or exceed headline package limits, especially if most customers do not use the full allowance. The provider with the better automation, lower support burden and larger purchasing scale can win even if every provider's offer looks generous.

There is also a substitution problem inside the customer's budget. A small business can spend on a website package, a SaaS website builder, a cloud productivity suite, marketplace storefront tools, social commerce, a managed WordPress provider, a local agency hosting bundle or a cloud VPS. EVANZO's offer has to remain relevant inside that stack. A domain and email bundle is sticky, but not invulnerable. If the customer's website becomes a marketing sidecar to social platforms and SaaS tools, webhosting becomes less strategic.

If the customer's website becomes mission-critical, the customer may demand managed application performance that a commodity shared-hosting bundle does not provide.

Network control can defend against some of this pressure. It can improve service continuity, give EVANZO more control over address reputation, support local routing and keep the provider from being captive to a single upstream or wholesale host. But the public evidence also shows upstream dependence on much larger networks and limited public interconnection disclosure. EVANZO can control its prefixes, but not the entire path to the customer.

The risk is therefore a middle-position squeeze. EVANZO may be too operationally real to have the asset-light simplicity of a pure reseller, but not large enough to match the product breadth of IONOS or the global developer ecosystem of AWS. It can still be a good business if it owns a loyal SME niche. It becomes vulnerable if it must keep prices low while carrying the cost of network operations that customers do not explicitly value.

What would prove the footprint earns its cost

The judgment should change if EVANZO can show concrete evidence that local control changes customer economics. The first proof would be retention. If customers with domains, email, webspace and DNS stay materially longer than customers on simple domain-only packages, the bundle is working. If churn is low even after contract terms shorten, then local service and operational continuity may be creating real value.

The second proof would be utilization and margin. EVANZO would need to show that its IPv4 and hosting resources are filled efficiently without creating support overload. High address utilization, clean abuse metrics, stable mail reputation, low incident frequency and controlled support tickets per account would show that the network footprint is productive rather than ornamental. In a business with low visible monthly prices, efficiency matters more than brand story.

The third proof would be supplier resilience. The public record shows upstream relationships with large networks and observed neighbours including Level 3 Parent and Colt. Stronger evidence would include diversified active upstream capacity, measurable failover performance, clear maintenance communication and no material customer impact from upstream incidents. Public PeeringDB disclosure or facility transparency would also improve confidence, though absence of such disclosure is not proof of operational weakness.

The fourth proof would be product progression. EVANZO needs a way to keep customers as their needs mature. If customers move from domain packages to Basic, Profi or Business hosting and then into related server products without leaving the commercial orbit, the partner structure has strategic value. If growing customers leave for IONOS, Hetzner, AWS, DigitalOcean or agency-managed hosting, then EVANZO's network footprint mainly supports a low-growth legacy base.

The fifth proof would be pricing discipline. A provider that owns scarce resources should not have to chase every discount if customers value continuity. Evidence of stable average revenue per account, successful upsell into higher packages, low refund pressure and low bad-debt or abuse losses would support the case. If prices must fall while support and network costs rise, the resource base does not protect value.

Until those facts are public, the most defensible view is measured. EVANZO has more infrastructure substance than a thin marketing site. RIPE, RIPEstat, BGP and IPinfo evidence all point to a real German hosting network with meaningful address resources and active routing. But the capital recovery case is unproven. The footprint can earn its cost only if it supports durable, low-friction, locally trusted hosting revenue that larger carriers and cloud platforms cannot easily strip away with cheaper, simpler alternatives.