Convotis Services GmbH and the capital recovery test behind local network control

Summary

• Convotis Services GmbH is best understood as a Vienna-based managed IT, cloud, security and platform-operations company with RIPE NCC membership, not as a large standalone telecom carrier. Its public number-resource evidence is real: RIPE records show an Austrian LIR, an IPv4 /22 allocation, an IPv6 /29 allocation and an announced IPv4 route through AS1764, Next Layer.
• The capital recovery test is demanding because the Austrian legal entity's public 2024 figures show modest scale and thin profitability relative to labour, cloud operations, compliance and support obligations. The value case depends on converting local control into paid continuity, compliance, security and migration outcomes, not merely holding addresses or advertising sovereignty.
• Larger carriers, AWS, Azure, Google Cloud, public-cloud integrators and DACH managed-service groups give customers simpler alternatives. Convotis can defend pricing only where customers need accountable European operation, jurisdictional control, hybrid integration, public-sector assurance or support that a pure self-service cloud bill does not provide.
• The facts that would change the judgment are concrete: segment-level recurring revenue, retention, gross margin by cloud and security service, customer concentration, uptime and incident performance, utilisation of the 45.88.240.0/22 block, IPv6 deployment, upstream cost terms, and proof that recent portfolio changes raised rather than diluted returns.

A Vienna LIR With A Cross-Border Service Area Has To Earn Control Locally

Convotis Services GmbH starts with a geographic constraint. The Austrian company is registered at Guglgasse 15/4a in Vienna, appears in Austrian company-register mirrors under FN 239937z, and is listed in RIPE records as an Austrian Local Internet Registry. RIPE's member page gives the same Vienna address and shows service areas in Austria, Switzerland, Germany, Romania and Slovakia. That is a cross-border operating promise, but it is not the same as a pan-European carrier balance sheet.

The entity has a local administrative base, a DACH and Central European service posture, and a parent-group context that tries to turn local presence into a wider managed IT offer.

The old name matters because it explains why network records still carry the ITSDONE trace. Austrian registry mirrors show the current Convotis Services GmbH name from September 2022 and the earlier ITSDONE Services GmbH identity from October 2003 to September 2022. RIPE records likewise use the at.itsdone registry label and contact details. For readers, the practical point is continuity rather than branding: the number-resource footprint did not appear as a new marketing artifact after the Convotis name arrived. It is connected to an older Austrian IT services operation that later moved under the Convotis identity.

That makes the first economic test sharper. Convotis Services is not trying to monetise local control from a blank slate. It already has a local legal entity, address space, support contacts, staff signals and group-owned service lines. The question is whether those assets produce enough incremental value to justify the operating load they create. A local LIR has administrative obligations. A cloud and managed-services operator has 24-hour support expectations, cybersecurity controls, compliance documentation, supplier management and renewal risk.

If customers only want low-cost compute, Microsoft 365 administration or commodity internet access, Convotis has to compete with larger providers that can spread those costs across much bigger volumes.

Local control therefore has to be sold as something specific. It can mean Austrian and European accountability, support continuity for mid-sized firms, control over address allocations, hybrid network integration, direct responsibility for incident response, and the ability to combine cloud, workplace, security and platform work in one operating model. It cannot simply mean "we are local." Locality is valuable only when the buyer has a problem that becomes cheaper, safer or more reliable because a local operator carries it.

The operating boundary also protects the article from an overclaim. Austria is Convotis Services GmbH's registration and support base, while the service-area evidence reaches into neighbouring markets and group references reach across Europe. That combination can be commercially useful, but it also creates a governance question. A buyer wants one accountable supplier; the underlying delivery may involve the Austrian company, group affiliates, upstream networks, public-cloud platforms and specialist software vendors.

The economic value of local control rises when Convotis can make that multi-party delivery feel like one accountable service and falls when the customer sees only a chain of dependencies.

The Business Is Managed IT, Cloud And Security, Not A Standalone Access Network

The company's public materials position Convotis as an IT services group. The website describes digital transformation, data science and AI, cloud solutions and security services. It says more than 3,500 customers use the group's expertise across Europe and that the group operates in five countries with more than 1,000 IT experts. The Austrian support page lists Convotis Services GmbH at the Vienna address, while the general imprint also lists Convotis Holding Austria GmbH and Convotis Services GmbH separately.

The company is therefore part of a larger European services group, but the article's economic subject remains the Austrian entity and its local network-control footprint.

The service mix is broader than connectivity. Convotis markets private, sovereign, hybrid and public cloud environments; managed public cloud operation for AWS and Azure; Kubernetes management across public, private and hybrid environments; managed digital workplace; security consulting; security operations; SIEM, MDR and 24-hour SOC language; and governance around controlled cloud environments. Its Trust Center says it operates cloud environments based on data centres in the EU and Switzerland and frames security, architecture, operations and governance as linked responsibilities.

That positioning is consistent with a managed-services company that wants to own the operational layer between customer workloads and the underlying infrastructure.

The business model implied by these materials has four revenue engines. First, Convotis can earn recurring fees for cloud hosting, private-cloud capacity, backup, workplace and infrastructure operation. Second, it can earn managed-service fees for monitoring, patching, incident response, security operations and administration of public cloud accounts. Third, it can earn project revenue from migrations, platform design, digital transformation and application or data work. Fourth, it can use public-sector and regulated-industry references to win contracts where governance and evidence of control matter.

That model is not necessarily inferior to a pure carrier model. A small firm can create more value from service labour and operational knowledge than from moving packets at thin margins. But it also means the RIPE membership and address holdings are supporting evidence, not the whole business. They show a resource-holder footprint and a basis for operating controlled services. They do not prove that Convotis sells access at scale, owns metro fibre, runs a national backbone or has carrier-like economies.

The article therefore treats Convotis as a managed IT and cloud operator with number resources, rather than as a traditional ISP whose economics are dominated by subscriber line count and wholesale bandwidth margins.

The strongest commercial proposition is managed accountability. An SME that already has Microsoft, a line from a carrier, a backup product, a firewall vendor and a few hosted workloads may not need another single-purpose supplier. It may need someone to take responsibility for whether the combination works during a migration, ransomware event, audit request or staffing gap. Convotis's public service language points to that role. The hard part is pricing it. Accountability is valuable when it is backed by scope, service levels and evidence; it is expensive when it becomes unlimited problem ownership for a fixed fee.

The Number-Resource Footprint Is Real, But Narrow

The network evidence is specific enough to matter and small enough to limit the claim. RIPE's organisation entity identifies Convotis Services GmbH as ORG-ISG14-RIPE, country Austria, registration number FN239937z, org type LIR, with the Vienna address. RIPE's inetnum entity shows 45.88.240.0 to 45.88.243.255, netname AT-ITSDONE-20190620, status ALLOCATED PA, created on 20 June 2019. That is a /22, or 1,024 IPv4 addresses. RIPE's inet6num entity shows 2a07:df80::/29, also created on 20 June 2019. RIPE's membership allocation list carries the same IPv4 /22 and IPv6 /29 under at.itsdone and Convotis Services GmbH.

The IPv4 block is visible in global routing. RIPEstat's routing-status data for 45.88.240.0/22 shows the route first seen in July 2019 and last seen on the July 2026 query time, with origin AS1764 and visibility across all listed IPv4 RIS full peers at that time. The RIPE route object also records origin AS1764. That means the address block is not only registered; it is announced through an upstream autonomous system. The block is real operational inventory.

The IPv6 evidence is different. RIPE records show an allocated IPv6 /29, a large address pool by customer-addressing standards. But RIPEstat's prefix overview and routing-status data did not show the aggregate announced at query time. That does not mean Convotis has no IPv6 services anywhere, because more-specifics, customer assignments or private arrangements can require deeper technical validation. It does mean the public evidence does not support a claim that the /29 aggregate is broadly visible in global routing. The conservative conclusion is that Convotis has an IPv6 allocation but the public aggregate-announcement evidence is weak.

This distinction matters for capital recovery. IPv4 scarcity can help a resource holder because a /22 is more valuable than a new entrant's default position in a post-runout market. RIPE's waiting-list policy gives eligible new LIRs only one /24 from recovered addresses, and only if they have not previously received an IPv4 allocation. Convotis's /22 therefore represents a more useful pool than the current waiting-list baseline. But 1,024 IPv4 addresses are still not enough to build a large hosting or broadband business by themselves.

They can support management addresses, customer services, hosted workloads and operational continuity. They cannot alone create durable pricing power unless attached to services customers cannot easily move.

Operational hygiene is part of that value. A provider using its own address space has to keep assignments clean, contacts accurate, abuse handling responsive and routing stable. Poor reputation or weak response can turn an address asset into a customer-service liability. The benefit of the /22 is therefore not only numerical scarcity; it is the ability to provide stable, governed addressing inside a broader service relationship. That is a modest but real advantage for customers with firewall rules, partner allowlists, remote-access arrangements or hosted services that dislike frequent renumbering.

Routing Dependence Makes Local Control A Shared Product

Convotis's IPv4 prefix is announced by AS1764, which belongs to Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH. That is not a flaw; it is a normal operating choice for many managed IT and hosting companies. It does, however, define the real control boundary. Convotis holds the address allocation, but public routing evidence points to a specialist Austrian network operator as the origin. Local network control is therefore shared between Convotis's resource and customer-service layer and Next Layer's routing, peering and facility footprint.

Next Layer's public materials describe it as an owner-operated Austrian ISP that designs cloud, network and server infrastructure for business clients. Its homepage lists 2025 sales volume of EUR 27.66 million, 76 employees, more than 20 years in the market and four data-center locations. Its PeeringDB entry for AS1764 shows a network-service-provider profile, 1-5 Tbps traffic level, balanced traffic ratios, IPv4 and IPv6 support, and multiple exchange points and facilities, including Austrian and European locations.

That profile gives Convotis an upstream route to broad connectivity without requiring Convotis Services GmbH to build a comparable network platform itself.

The upside is capital efficiency. Convotis can focus capital and attention on customer platforms, security operations, service management, cloud governance and application continuity while relying on an established connectivity provider for reach. A small or mid-sized operator often creates better returns this way than by buying every layer of the stack. The downside is margin sharing and operational dependence. If the upstream supplier controls routing, peering, facility access and some technical response paths, Convotis must price its service to cover both its own operational costs and supplier costs.

It must also absorb customer accountability when a dependency fails outside its direct control.

This is why the article does not equate the RIPE resource with full network independence. Convotis has more control than a reseller with no number resources. It can identify and administer its own allocation, create a stable customer-addressing base and maintain continuity under its own corporate identity. But the market-facing service is still a composite product. Customers experience uptime, route quality, cloud performance, support response and compliance assurance as one service. They rarely pay extra because one component is locally registered unless that component reduces risk they can understand.

Scale Claims Must Be Separated From The Austrian Entity's Balance Sheet

The Convotis group talks like a European platform: more than 3,500 customers, over 1,000 IT experts, operations across five countries, acquisitions in managed services and cloud, and strategic focus on AI, sovereign cloud and cybersecurity. Those facts are relevant because group reputation, references and delivery capability can help the Austrian entity win work. They are not the same as the Austrian entity's own economics.

Public Austrian financial mirrors show Convotis Services GmbH as a much smaller balance-sheet entity. Firmenatlas reports 2024 total assets of about EUR 5.7 million, equity of about EUR 476,000, an equity ratio of 8.4 percent, working capital of about negative EUR 284,900, operating profit of about EUR 124,900 and annual surplus of about EUR 145,900.

The same source shows personnel expense of about EUR 6.8 million, other operating expenses of about EUR 4.0 million, depreciation and amortisation of about EUR 316,100, intangible assets of about EUR 1.4 million, tangible fixed assets of about EUR 107,200 and liabilities of about EUR 4.3 million, including a large amount owed to affiliated companies.

Those figures do not prove distress. They do show a service company where labour and operating expenses absorb most of the gross economic room. If EUR 11.2 million of raw result is used as a rough operating scale indicator, the reported operating profit is a little over one percent of that figure. That is a thin margin for a business that markets high-availability, security-sensitive services. The surplus helps, but it does not create obvious excess capital for heavy independent infrastructure build-out.

The unit economics must therefore be judged through returns on reuse. A data-center rack, a managed cloud platform, a SOC shift, a service desk, a backup environment and a block of IPv4 addresses are profitable only when reused across enough customers at contract prices that reflect risk. The Austrian entity's balance sheet suggests it should avoid vanity ownership. If it owns too much unused infrastructure, capital sits idle. If it owns too little, it becomes a pure integrator with weak differentiation. The right zone is a controlled operational layer that is narrow enough to finance and deep enough to matter.

Unit Economics Depend On Contracts That Bundle Labour, Risk And Uptime

Convotis's public offer is labour-heavy. Cloud governance, managed public cloud, Kubernetes operation, security consulting, managed detection and response, workplace support and platform transformation all require skilled staff. Karriere.at describes Convotis Services GmbH as active in internet, IT and telecom, founded in 2003, with 101 to 500 employees, and lists skills such as IT support, cloud, SAP consulting, IT consulting and Office 365. Hokify and other job-board pages also reflect support, engineering, SAP, infrastructure and development roles.

These are useful unofficial market signals: they point to a people-based operating model, not an automated commodity platform with near-zero marginal cost.

That creates a pricing problem. Customers often compare managed-service offers to the visible cost of public cloud, a Microsoft licence, a broadband line or an in-house engineer. The provider must then explain why its fee covers more than raw capacity. In Convotis's case the answer has to be continuity, accountability, incident response, architecture, compliance, integration and local service. The provider is not merely reselling AWS or Azure. Its managed public cloud materials describe governance, monitoring, security hardening, backup, policy-as-code and cost control.

Its Kubernetes offer includes provisioning, lifecycle management, security, observability and disaster recovery across public, private and hybrid environments. Those are labour and process products.

The margin depends on contract discipline. A fixed monthly managed-service fee can be attractive when workloads are stable, automation is mature and incidents are below expected levels. The same fee can become unattractive if customers understate complexity, require bespoke integrations, generate frequent support tickets, delay standardisation or resist price increases. Security services have a similar shape. A SOC and MDR service can earn premium revenue, but only if alert triage, escalation, documentation and customer obligations are clearly scoped.

Otherwise the provider carries open-ended risk for a price negotiated as if the service were a simple subscription.

Convotis's 2024 Austrian financial profile makes this more than an academic concern. Personnel costs were the largest visible expense category. Other operating expenses were also substantial. If the company wants local control to pay, it must turn fixed technical and staffing capacity into repeatable services. Bespoke heroics may win praise but destroy returns. Standardisation, automation and firm service boundaries are not operational preferences; they are the economic mechanism by which a small local platform can survive against larger substitutes.

The same logic applies to project work. A migration project can fund expertise and create a later managed-service contract, but project-only revenue is lumpy. It can also consume senior engineers who should be improving repeatable platforms. The value-creating sequence is clear: a project lands the customer, standard architecture reduces delivery variation, managed service turns the project into recurring revenue, and operational data improves the next engagement. If the sequence breaks, growth can look busy without compounding.

The Austrian financials make that distinction important because there is not enough reported profit cushion to absorb many poorly scoped contracts.

Capital Recovery Runs Through Reuse, Not Pure Address Scarcity

There is a tempting but incomplete argument that IPv4 scarcity gives Convotis natural pricing power. The RIPE waiting-list position for new entrants and the existence of only a /24 path for eligible new LIRs do make older allocations useful. A /22 can support more customer environments than a /24 and can reduce dependence on rented address space. It can also preserve continuity when customers need stable address ranges for allowlists, VPNs, firewall policies, B2B integrations or externally visible services.

But address scarcity is not a full business model. Many customers do not know how many public IPv4 addresses their managed-service provider controls. Many workloads can run behind NAT, in hyperscaler environments, with managed load balancers or through cloud-native addressing. Some customers value continuity and auditability more than address ownership. Others care only about application availability and price. A local address block helps when it is attached to sticky workloads. It does little if customers can move to a global cloud account with cheaper scaling and no interest in the provider's own addressing.

The same is true for sovereign cloud. Convotis markets European and Swiss data-centre foundations, controlled dependencies and legal factors such as the US CLOUD Act. That can matter to public-sector, health, finance, industrial and compliance-sensitive buyers. Yet sovereignty language has to be translated into paid features: where data is processed, who has access, how identities are controlled, how incidents are reported, how backups are restored, how supplier risk is documented, and how exit is handled.

Buyers will not always pay a premium for broad sovereignty claims if they can obtain adequate compliance statements from Microsoft, Amazon, Google, IONOS, T-Systems, OVHcloud or another regional provider.

The most plausible capital recovery path is bundled reuse. The IPv4 /22 supports hosted and managed services. The IPv6 /29 gives future addressing headroom if activated and marketed properly. The upstream relationship provides reach. The group cloud and security capabilities add customer value. The support desk and engineering teams provide service continuity. The question is whether those pieces are used across enough customers with enough standardisation to produce attractive returns. If each contract is bespoke, the cost base follows revenue upward and value creation stalls.

Supplier Dependence Narrows Pricing Power

Convotis operates in a supplier-rich environment. Its own materials explicitly describe managed public cloud services for AWS and Azure. Its cloud pages discuss private, hybrid and public models. Its Trust Center discusses controlled dependencies on external services. Its public routing evidence points to Next Layer for the IPv4 origin. Its security services use SIEM, MDR and SOC concepts that typically involve software platforms, threat feeds, endpoint tools and cloud telemetry. This is a modern managed-service reality: the provider is paid to assemble, govern and operate dependencies, not to eliminate them.

Supplier dependence can be commercially positive. It allows Convotis to offer AWS, Azure, private cloud, Kubernetes, workplace and security services without financing every physical and software layer. It gives customers choice. It also lets Convotis focus on governance, integration and support, which may be where mid-market customers need the most help. A customer that lacks cloud engineers may value a provider that can manage Azure cost, identity, backup, monitoring and policy more than a provider that owns a data hall.

The pricing ceiling is still set by alternatives. AWS and Azure partners can be swapped. Large telecom operators can bundle connectivity, cloud access, workplace and security. Global system integrators can absorb complex transformation work. Local IT houses can compete on relationship and response time. Next Layer and other Austrian infrastructure providers can sell connectivity and hosting directly. If Convotis's service is perceived as an account wrapper around third-party platforms, pricing power is thin. If it is perceived as a controlled operating model that reduces outages, compliance risk and staff burden, pricing power improves.

This is where supplier terms become strategic. A small provider must negotiate bandwidth, hosting, software, security tooling and public-cloud resale terms well enough to leave room after support labour. It must avoid passing through public-cloud costs with no advisory margin, and it must avoid taking fixed supplier commitments without customer commitments that match them. The worst case is clear: the provider takes platform and support risk while the buyer keeps cloud-style flexibility and procurement pressure.

The best case is also clear: Convotis becomes the accountable operating layer for customers whose complexity is high enough that a pure self-service model is costly in practice.

Supplier dependence also affects the sales narrative. If a customer is already committed to Azure, the provider must show why Convotis-managed Azure is better than a direct Microsoft partner, internal administration or a larger systems integrator. If a workload runs in a Convotis private or sovereign environment, the provider must show why that environment is safer, more controlled or more responsive than direct hosting from an infrastructure specialist. If traffic depends on an upstream network, the provider must show how escalation, redundancy and responsibility are handled.

These are not minor details; they decide whether Convotis can charge for orchestration rather than appear as a reseller.

Customers Buy Continuity, But Can Also Buy Simpler Substitutes

The customer problem Convotis wants to solve is real. Eurostat reported that 52.74 percent of EU enterprises used paid cloud computing services in 2025, with e-mail, office software and file storage dominant among purchased cloud services. Among cloud-using EU enterprises, 77.25 percent purchased at least one infrastructure-as-a-service element, and roughly a quarter used platform-as-a-service development or deployment environments. Cloud is no longer a frontier product for enterprises; it is ordinary operating infrastructure.

That helps Convotis because ordinary infrastructure still fails, costs too much, becomes insecure and needs integration. Mid-sized firms may not have enough internal staff to design hybrid cloud, enforce identity controls, manage backup, operate Kubernetes, run a SOC and respond to regulatory audits. Public institutions and regulated companies may also need evidence that services are operated under European legal and governance assumptions.

Convotis's European Commission AIOD reference is relevant because it describes a sovereign platform, identity and access work, DevOps environment, marketplace integration, private-cloud operation in Europe and scalable compute for public-sector and research users. The DeployAI project itself is backed by the EU Digital Europe programme and involves a consortium across multiple countries.

The same market also creates substitution risk. The largest global cloud providers keep getting larger. Synergy Research reported that Amazon, Microsoft and Google accounted for 63 percent of worldwide enterprise spending on cloud infrastructure services in Q3 2025. In Europe, the same research group estimated that European providers held around 15 percent local market share, while Amazon, Microsoft and Google accounted for 70 percent of the regional market. That does not mean local providers are doomed. It does mean they are not winning by outspending the hyperscalers.

Local and regional providers win narrower jobs. They win where the buyer needs proximity, migration help, contractual accountability, local-language support, custom integration, hybrid infrastructure, or a credible sovereign-cloud posture. They lose when the buyer wants elastic scale, global region coverage, advanced platform services, procurement consolidation or the lowest unit cost. Convotis's economic problem is to choose the former cases and avoid being dragged into the latter on unfavourable terms.

Regulation Helps The Case Only If Compliance Becomes A Paid Feature

Regulation can support Convotis's value proposition, but it does not automatically create profit. The EU's NIS2 Directive broadens cybersecurity obligations across critical sectors, adds risk-management and incident-reporting requirements, and raises the board-level importance of cybersecurity. In Austria, the WKO describes NISG 2026 as coming into force on 1 October 2026, affecting around 4,000 companies and institutions from 18 sectors, with risk-management duties, incident reporting and supply-chain security obligations.

It also notes that service providers and suppliers of affected organisations can be contractually pulled into risk-management measures.

That creates a commercial opening for managed security, compliance documentation, monitoring, backup, incident response and supplier-risk evidence. Convotis already markets security architecture, SOC operations, SIEM-enabled detection, governance, compliance and traceability. Its Trust Center frames security, architecture and operations as linked, and says certain SOC 2 reports are provided on request rather than publicly. If customers need to show auditors and boards that their IT and cloud suppliers are controlled, Convotis can sell evidence, process and accountability.

The risk is cost without price. NIS2 can force providers to maintain better documentation, stronger supplier controls, incident procedures, governance meetings, training, logs, audits and evidence. Those are real costs. If Convotis bundles them into legacy service fees without repricing, regulation compresses margin. If it turns them into clear paid service tiers, regulation can improve retention and pricing. The difference is contract design.

Geopolitical and jurisdictional concerns add another layer. Convotis talks about European and Swiss data-centre operation, legal access controls and the US CLOUD Act. Some buyers will value that posture. Others will accept standard public-cloud compliance frameworks. Convotis must avoid overclaiming. A European operator can reduce some jurisdictional and operational risks, but it still depends on external software, hardware, upstream connectivity, public-cloud services and security tools.

A defensible compliance offer must show which layers are locally controlled, which are outsourced, which are governed by contract, and how evidence is produced when something goes wrong.

The customer benefit is clearest when regulation changes procurement behaviour. A finance, health, public-sector or industrial buyer may no longer be satisfied with a low-cost hosting quote if board accountability, incident reporting and supplier-chain evidence are on the table. That gives Convotis room to sell documented operation, restore testing, access governance and support escalation as economic insurance. The company still has to prove that insurance is cheaper than hiring internally or buying from a larger operator. Regulation opens the door; it does not remove the comparison.

Unofficial Signals Point To Skills Demand Rather Than Proof Of Pricing Power

The useful unofficial signals are hiring and market-positioning signals, not rumours. Public job and employer pages describe Convotis Services GmbH as an internet, IT and telecom employer in Vienna, with a service portfolio that includes classic IT infrastructure, hybrid cloud, high-end IT security, SAP-related services and innovation work. They list employee bands, support roles, cloud and IT consulting skills, salary examples in older postings and multiple Austrian or German locations. These materials support the view that Convotis sells skilled IT operation and project capability.

They do not prove pricing power. A busy hiring page can indicate growth, staff churn, skills scarcity or a need to replace capacity after portfolio changes. A broad role mix can indicate cross-selling opportunity, but it can also indicate complexity. Salary examples show that customers ultimately fund a European labour base. If customers compare Convotis only to cloud self-service prices, those labour costs are hard to recover. If they compare Convotis to hiring, training and retaining their own cloud, security and infrastructure staff, the economics look better.

M&A signals also need careful handling. Convotis and third-party advisers have publicised acquisitions and divestments: MCON Managed Services, SENTINEL and METRO CLOUD, swiss cloud computing, and a 2026 sale of Austrian and Slovenian SAP business to Aricoma. Convotis's own January 2026 strategic realignment says it is concentrating on digital transformation, AI, sovereign cloud and security after selling the SAP business. That is a coherent strategic direction. It also raises an execution question. Acquisitions can add customers, expertise and capacity. They can also add integration costs, overlapping systems and uneven margins.

The conservative reading is that Convotis is trying to move away from broad IT-services sprawl toward cloud, security and platform operations. That direction matches market demand and regulatory pressure. It also requires managerial discipline. A services group that grows by acquisition can report visible expansion without creating value if integration costs, customer overlap and labour intensity offset revenue. The Austrian entity's narrow margin leaves little room for unfocused growth.

What Would Prove The Local-Control Footprint Earns Its Cost

The current evidence supports a cautious thesis. Convotis Services GmbH has real operating substance: legal registration in Vienna, active support contacts, RIPE NCC LIR status, a public IPv4 /22, an IPv6 /29, public cloud and security service lines, and group references in public-sector and managed-service work. It also faces a hard capital-recovery test because its public Austrian financials show modest assets, thin profit and a labour-heavy cost base. The company can earn local control only if it monetises continuity, compliance and hybrid operation more effectively than larger carriers and cloud substitutes can commoditise them.

Several facts would materially improve the judgment. The first is segment-level recurring revenue from Austrian and cross-border cloud, security and managed infrastructure contracts, separated from one-off project work. Recurring revenue with low churn would show that customers pay for the operating layer, not only for migrations. The second is gross margin by service line, especially private or sovereign cloud, managed public cloud, security operations and workplace services. Without margin by line, visible growth can hide weak economics.

The third is utilisation of the number-resource footprint. How many customer environments, hosted services, management systems or high-value integrations rely on 45.88.240.0/22? Is the IPv6 /29 actively assigned through more-specifics, customer plans or future services? Does address control reduce churn or support premium contracts? The fourth is customer concentration. A few public-sector or large enterprise contracts can validate capability, but they can also create renewal risk.

The fifth is supplier economics: upstream bandwidth and routing terms, public-cloud resale or management margins, security-tool costs, and the degree to which supplier commitments are matched by customer commitments.

Operational facts would matter as much as financial ones. Uptime records, incident response times, backup restore performance, security event handling, audit outcomes and customer-renewal evidence would show whether Convotis's local operating promise is more than positioning. Evidence of standardised service tiers, automation, reusable architecture and disciplined scope control would also improve the case because those are the levers that turn skilled labour into scalable margin.

Until those facts are public, the right conclusion is balanced. Convotis Services GmbH is not a hollow directory listing and not merely a brand shell. It is a real Austrian IT services operator with number-resource evidence and a relevant cloud/security proposition. But local network control is not self-justifying. It has to be converted into priced risk reduction for customers who value European operation, continuity and accountability enough to pay more than the simplest carrier or hyperscale substitute.