Summary

  • Laboratory of Information Technologies LLC is best read as a small Lviv technical-control business with real RIPE number-resource history, visible AS43880 routing, domain and hosting traces, and small public-sector internet-service contracts, not as a disclosed national ISP or hyperscale cloud platform.
  • The economic question is whether the company can charge enough for local engineering, hosting, registry support, reachable service and continuity to cover upstream connectivity, power backup, security handling, renewal capital and wartime uncertainty with only a thin disclosed revenue base.
  • Its strongest defensible value is accountability at the edge: a customer that needs a website, address block, domain delegation, institutional connection or small hosted service to keep working may prefer a local operator that knows the site and answers the phone. Its weakest point is the same narrowness: customers can compare the price with larger Ukrainian carriers, cloud platforms, mobile fallback, xPON-focused access providers and do-it-yourself hosting.
  • The judgment is conditional. The record supports a durable, technically literate Lviv operator with more control than a generic reseller, but the public economics show a business that must price continuity explicitly. If blackout backup, abuse work, route diversity or security response are treated as free extras, the margin disappears.

Start with one modest but unforgiving workload: a public institution in Lviv pays for internet service, a domain name, hosting, or a small network function that cannot simply disappear during a power cut. The visible invoice may be only a few thousand hryvnias. The economic liability attached to it is larger.

Someone has to keep the route clean, the server reachable, the domain delegated, the customer informed, the abuse contact alive, the upstream paid, the electricity problem solved long enough to avoid a service failure, and the renewal conversation credible when the customer asks why it should not move to a larger carrier or a cloud panel.

That is the right lens for Laboratory of Information Technologies LLC. Its public record does not describe a fast-growing broadband consolidator, a national fibre platform, or a software company with heavy recurring product revenue. It describes a Lviv limited liability company, commonly shortened in Ukrainian business records as LITECH, with a long corporate life, a RIPE NCC local internet registry identity, AS43880, several public number-resource entities, small public procurement traces, and a role in the local web, domain, hosting and internet-service economy. The investment case is therefore not about scale.

It is about whether local technical control is scarce enough, and valued enough, to fund the operating burden that war has made more expensive.

The identity boundary is unusually important because the name sounds broad. Ukrainian company aggregators tie the code 13830803 to the full legal name translated as Laboratory of Information Technologies, a Lviv address on Dzhokhar Dudayev Street, a registration date of 30 June 1992, a 75,000 UAH statutory capital figure, and a main economic activity in management of computer facilities. The same public profiles list related activities that include programming, IT consulting, other information-technology and computer-system activities, data processing, web hosting and related work.

RIPE's organisation record links ORG-LOIT4-RIPE to Laboratory of Information Technologies LLC, country UA, registry number 13830803, LIR status, Lviv, and the same telephone pattern. This alignment matters: the network record is not a stray homonym. It points back to the same corporate identity.

The control boundary is still narrower than the name suggests. The company appears as a RIPE member and resource holder, but public routing data do not show a sprawling backbone. RIPE records identify AS43880 as LITECH-AS, with imports and exports involving UARNET, Integra Media, Telecommunications Resource Center in Lviv, and AS202879. RIPEstat's current view on 28 July 2026 shows AS43880 announced and originating two IPv4 prefixes, 185.94.217.0/24 and 185.94.218.0/24.

RIPE database records also show a broader 185.94.216.0 to 185.94.219.255 allocation, sub-assignments such as ISR-NET and LITECH-INT, and a separate 193.53.89.0/24 LITECH-NET assignment with route objects for both AS43880 and AS205420. That is real technical surface. It is not proof of mass-market access reach, and it is not proof of revenue scale.

The upstream mix gives the business its first economic test. An operator with AS43880 is not merely reselling a hosting account if it manages routes, address assignments, customer prefixes, abuse contacts and domain delegation. But it still depends on upstream networks and local interconnection choices. AS43880's public aut-num imports from larger and regional Ukrainian networks, while IPinfo and third-party WHOIS views show public traces through Lviv and Warsaw measurement points.

PeeringDB, by contrast, returns no public network profile for AS43880, which means the company does not use that common venue to advertise exchange points, facilities, traffic ratios or peering policy. The absence of a PeeringDB profile is not a defect by itself; many smaller networks do without it. Economically, though, it keeps the outside buyer from seeing a strong self-published interconnection story.

That leaves the proposition grounded in local control rather than transparent wholesale strength. A Lviv institution does not need Laboratory of Information Technologies to be the cheapest route to the global internet. It needs the company to know the specific service, fix the specific failure, and keep enough technical authority that the customer is not passed among a domain registrar, an access provider, a hosting vendor and an upstream carrier. The record points to this kind of work. Public procurement aggregators list small internet-service contracts, provider services, domain delegation and hosting.

A Clarity Project procurement page for April 2026 shows the Lviv Academic Spiritual Theatre "Voskresinnia" buying internet services from TOV Litech for 4,580 UAH. Opendatabot lists recent 2026 items for internet services, provider services and domain delegation and hosting, and identifies buyers such as Ukrposhta, academic institutes, Lviv public bodies and cultural institutions in the company's tender history.

The amounts are small, and that is the point. A 4,580 UAH internet-service contract does not pay for a sophisticated continuity architecture unless it is one item inside a broader book of recurring relationships. Opendatabot's aggregate financial table reports 2025 revenue of 696,300 UAH, 2025 net profit of 3,400 UAH, assets of 116,700 UAH, liabilities of 13,800 UAH and three employees. It reports 2024 revenue of 975,300 UAH and net profit of 38,100 UAH. Those numbers come from an aggregator and should not be treated as audited by the reader, but they are still economically instructive.

The disclosed scale is small enough that even modest backup power, router replacement, software licences, upstream price changes, bad debts or emergency field work can move the margin.

The cash-flow test is therefore severe. Suppose one customer buys hosting, domain handling and a basic connection. The price has to cover the direct upstream or facility cost, the employee time to provision and support it, billing and collection, domain or registry administration, equipment depreciation, electricity, security response, support during outages, and the option value of keeping the same service alive during a crisis. If the invoice is priced like commodity access, Laboratory of Information Technologies keeps the obligation but not the premium.

If it prices the service like managed continuity, it risks losing a budget-sensitive public buyer to a larger carrier, a cheaper local ISP, a national mobile fallback, a public procurement retender, or a cloud product that appears simpler to an administrator.

The wartime operating environment makes this more than an ordinary small-provider problem. Ukraine's electronic communications market has been resilient, but resilience has not been free. NCEC's 2025 report says fixed-internet revenue grew, capex rose materially, and more settlements gained optical access, but those broad market figures do not mean every small operator enjoys pricing power. NCEC's fixed-access reporting analysis points to a relatively stable fixed-access line base after a peak in 2024, while also attributing part of the change to the consequences of the full-scale invasion and reporting effects.

Freedom House describes a diverse Ukrainian ISP market and notes that the diversity of providers helped prevent a nationwide internet shutdown, while also reporting power-driven disconnections, overloaded mobile fallback, provider use of generators and serious stress on smaller ISPs.

The battlefield does not have to be near Lviv for the economics to change. The cost enters through electricity, fuel, batteries, generator logistics, damaged transmission, customer payment discipline, equipment imports, insurance, route choice, staff availability and security work. The World Bank's 2025 recovery assessment identifies vast reconstruction needs and a sharply worsened energy-damage picture. The UN Human Rights Monitoring Mission's June 2026 update describes repeated attacks on energy infrastructure through the 2025-2026 winter and emergency outages affecting millions.

Lviv regional authorities have described schedules and emergency power cuts shaped by national limits and attacks on power infrastructure. For an operator selling reachable service, every outage forces a choice: absorb the cost, reduce the promise, or charge explicitly for continuity.

That is why the product definition should be "local continuity" rather than "internet." Internet access alone is vulnerable to price comparison. Local continuity can be more defensible because it bundles several messy jobs: route and DNS knowledge, customer-specific support, hosting migration, domain paperwork, public procurement documentation, abuse handling, backup procedures and recovery after power or equipment failure. A court-document trace from 2022, in which a Lviv court sought evidence from LITech about a domain registrant, is not evidence of commercial wrongdoing and should not be read that way.

It is evidence that the company can sit in the administrative path of domain or hosting information. That kind of operational boundary has value only if customers pay for accuracy, response and retention of records.

The company's RIPE profile adds another piece. A local internet registry membership can support address management, assignments, reverse DNS, routing and customer allocations. The 185.94.216.0/22 allocation and the 193.53.89.0/24 LITECH-NET assignment give Laboratory of Information Technologies more durable technical standing than a simple website designer. The current RIS view, however, shows only two AS43880-originated /24s, while other associated address space appears routed through other ASNs or carries separate customer descriptions.

That mixed footprint is not a weakness if the business model is local service and managed network resources. It is a weakness if the company wants the market to believe it controls a large, independent infrastructure platform.

One useful example is the 185.94.217.0/24 record, which RIPE labels ISR-NET and describes as Institute for Space Research while maintaining LITECH routing control in the route object. That is not a retail broadband signal. It is closer to an institutional connectivity or resource-management signal. The 185.94.218.0/24 LITECH-INT record is more directly tied to Laboratory of Information Technologies. The 193.53.89.0/24 record is assigned PI to LITECH-NET and has route objects for AS43880 and AS205420.

Together they describe a business that can host and connect specific institutions or workloads, but also one where the public record must be read prefix by prefix. The right conclusion is not "large ISP"; it is "small operator with verifiable resource-control tasks."

That distinction shapes the competitive set. Laboratory of Information Technologies competes upward against national carriers and larger Ukrainian operators with more power equipment, broader peering, larger support teams and better marketing. It competes sideways against local fibre and wireless providers that may be more visible to households during blackouts. It competes downward against a customer deciding to put a site on a low-cost cloud host, delegate a domain elsewhere, use a SaaS product, or rely on mobile connectivity when the fixed link fails.

It may also face specialised local IT firms that can bundle web development, cybersecurity, accounting and procurement support without owning much network surface. To win, the company has to make its controlled boundary more valuable than each substitute.

Ukraine's blackout-era customer behaviour raises the bar. LUN and Ukraine's digital authorities promoted maps of providers that can operate during outages, especially providers using energy-efficient optical technologies. Regional public messaging has told residents to choose xPON-capable providers, power their home equipment and use national roaming or public resilience points when mobile service is overloaded. Large mobile and fixed operators advertise batteries and generators. Kyivstar, for instance, publicly presents a resilience message around batteries, generators and backup power.

Laboratory of Information Technologies cannot match that scale in public presentation. Its better path is to serve customers whose demand is not "coverage everywhere" but "this service must stay reachable and someone local must own the recovery."

The pricing problem is uncomfortable because public procurement pushes in the opposite direction. Small public contracts often describe generic internet or hosting services. Procurement systems make price visible and scope compact. That is useful for transparency, but it can understate continuity cost. If a theatre, library, water utility, postal branch, research institute or local department buys a cheap service item, the buyer may still expect wartime support, clear communication and quick repair. The operator can try to keep the relationship by doing unpaid work, but that creates a quiet subsidy.

The economic test asks whether the scarce function is being paid for. If not, the business is converting staff diligence into customer savings rather than shareholder or reinvestment capacity.

The revenue figures make that subsidy risk concrete. A company with hundreds of thousands of hryvnias in annual revenue and a few employees has little room for repeated unpriced exceptions. It cannot carry much spare equipment. It cannot dedicate a large security team. It cannot easily finance generator fleets. It cannot absorb many customers who delay payment because public budgets are disrupted. It cannot replace many routers or batteries in one month without bending the balance sheet. It can survive if its customer base is loyal, local, low-churn and willing to pay for continuity tasks that larger providers underserve.

It becomes fragile if each customer treats the service as interchangeable and each outage turns into unpaid custom work.

Security is another cost that hides inside small invoices. Public AbuseIPDB pages and web-scanner pages connect some Laboratory of Information Technologies or associated prefixes with low-confidence, low-volume reports of bot, port-scan or web-abuse activity. Those reports are not proof that the company is negligent; the pages themselves show low or zero confidence on some items, and any hosting or access network can have compromised customer equipment. The economic lesson is that address space and hosted workloads require abuse handling.

Someone must receive the report, determine whether it is real, contact the customer, preserve service, avoid overblocking, and keep the network's reputation clean enough that mail, websites and public services remain usable. That labour must be priced somewhere.

The same applies to domain and hosting records. Third-party web intelligence pages associate websites such as local government, cultural or private domains with LITECH-related infrastructure or AS43880 hosting. These pages are imperfect, sometimes stale, and should be treated as signals rather than authoritative customer lists. Still, they fit the business model implied by public procurement: a small local operator whose value sits in keeping ordinary institutional web services reachable. The economic danger is that such customers care most when something breaks, but budget least when everything works.

A continuity provider needs contracts that recognise the value of quiet operation before the emergency, not only complaints after failure.

Regulation adds another layer of obligation. Ukraine's Law on Electronic Communications requires providers to take technical and organisational measures to ensure network and service security, preserve continuity and prevent unauthorised access. The same law establishes emergency and wartime operational management for communications networks. NCEC's register rules and later amendments require providers to keep and verify registry information. Cabinet measures on wartime resilience address reserve power, local-government cooperation, fuel and maintenance arrangements for communications equipment.

These rules are necessary in a country under attack, but they turn continuity from a nice-to-have into an operating expectation. For a small provider, compliance is not a theoretical legal paragraph; it is staff time, documentation, equipment and readiness.

There is a positive side. Because Ukraine's communications ecosystem is fragmented and diverse, small operators can matter. RIPE's analyses of the Ukrainian internet have repeatedly highlighted resilience and the importance of distributed network structure. RIPE NCC also made clear during the war that authoritative number-resource registration should remain stable and that Ukrainian members should not lose resources because wartime circumstances disrupt payment or administration. That institutional stability helps companies like Laboratory of Information Technologies.

It keeps the resource layer reliable enough that local operators can keep working even when power, routes or customer budgets are unstable.

The value created by this stability is still local and conditional. A public-sector customer in Lviv may not need a global cloud provider if it needs a modest site, domain, mailbox, connection or small hosted service, especially where local support and procurement familiarity matter. Laboratory of Information Technologies has a plausible advantage in that niche: long corporate history, RIPE-aligned identity, local contacts, visible network resources, and evidence of selling to public and cultural institutions. The advantage is not that it can outspend Kyivstar, Ukrtelecom, Datagroup-Volia, Vodafone, UARNET or local fibre challengers.

It is that it can reduce the customer's coordination cost when several small technical obligations meet in one incident.

Customer concentration is the question the public record cannot fully answer. Opendatabot lists top procurement buyers and aggregate tender sales, but it does not disclose the full private customer base or the durability of recurring contracts. If a few institutional buyers provide most visible tender revenue, procurement timing and budget cuts can dominate cash flow. If the company also has a base of private hosting, domain, academic, local-business and institutional customers outside public tenders, the economics may be more stable than the public procurement view implies.

Without full accounts or customer-level disclosure, the judgment has to stay bounded. The evidence supports a real operating niche, not a precise revenue-quality conclusion.

Capital renewal is the harder hidden test. Network-resource control can look asset-light in public filings, especially when the visible service is routing, hosting or domain administration. But reliable service needs routers, switches, UPS units, batteries, generators or generator access, cooling, spare parts, monitoring, security tools, backup storage, replacement drives, and staff who can repair or migrate systems. Imported equipment and currency exposure can make replacement more expensive than the old tariff assumed.

Ukraine's sector-wide capex growth shows that larger players are investing, but a small operator cannot assume the whole market's capex capacity is available to it. It must either earn its own renewal cash or accept slow deterioration.

The supplier side is equally important. AS43880's registered import/export relationships show dependence on upstream and adjacent networks. Those relationships may be stable, but they still define the resilience ceiling. If an upstream path is impaired, a small operator's promise depends on alternate routing, customer tolerance, and the physical path to reach the upstream. If a larger carrier raises prices or changes commercial terms, Laboratory of Information Technologies cannot easily pass through every increase to small public contracts.

If cloud providers make hosting cheaper and easier, the company has to sell support and accountability, not storage as a commodity. If local fibre providers advertise blackout survivability, it has to show why its narrower service still deserves renewal.

The best strategy is therefore not to chase generic volume. It is to sell named continuity packages that match the actual risk. One package is managed domain and hosting continuity for public institutions: verified delegation, backup DNS, contact records, restore procedures and documented response times. Another is small institutional connectivity: address management, route monitoring, power-continuity disclosure, escalation contacts and a clear statement of what is and is not redundant. A third is local web and mail stewardship for organisations that cannot manage multiple vendors.

In each case, the offer must include what the customer pays for during normal months, not just emergency heroics.

The professional implication for buyers is to ask better questions. Does the service depend on AS43880's originated prefixes or another ASN? Is the address space allocated, assigned, customer-specific or merely hosted? What happens during a four-hour, ten-hour or multi-day power outage? Which upstream paths are available? Is the domain contact current? Are backups tested? What is the response time for abuse reports? Are public procurement descriptions broad enough to pay for resilience, or do they buy only a cheap commodity? These questions are not hostile.

They are the questions that turn a local provider from an invisible cost into an accountable continuity partner.

For Laboratory of Information Technologies, the incentive is to resist being too modest. Small providers often survive by solving problems quietly and undercharging for the knowledge embedded in that quiet work. Wartime Ukraine punishes that habit. When millions can be affected by energy outages, when mobile networks can overload during blackouts, when citizens are encouraged to select resilient fixed providers, and when regulators expect providers to keep accurate records and continuity measures, the work is no longer just "internet service." It is local infrastructure maintenance.

The price has to say so, or the balance sheet will carry obligations that the invoice did not fund.

There is also a reputational opportunity. The company can use its RIPE-aligned identity and long history to reassure customers that it is not an ephemeral vendor. It can show the difference between a hosted website that happens to resolve today and a maintained service with accountable routing, domain, backup and support processes. It can publish clearer service descriptions, resilience limits and customer responsibilities without pretending to be larger than it is. In a market where trust is damaged by outages, cyberattacks and war-related uncertainty, clarity itself can be a product. The customer may pay more if the boundary is explicit.

The risk is that clarity also exposes limits. If the company cannot provide meaningful backup power, route diversity, monitored hosting or rapid recovery, then a premium continuity claim would be dangerous. The right posture is careful: say what is controlled, what is dependent on upstreams, what is backed up, what is best-effort, what requires customer-side power, and what costs extra. That careful uncertainty is more credible than a heroic promise. In wartime infrastructure, overclaiming is not only a marketing flaw. It creates operational and reputational liability when an outage proves the gap.

Facts that would change the judgment are straightforward. Stronger evidence of recurring private hosting or managed-service contracts would improve the revenue-quality view. Published resilience data, backup-power commitments, tested recovery procedures or independent customer references would support a premium continuity thesis. Evidence of broader peering, facility diversity, IPv6 deployment, RPKI deployment, or a detailed PeeringDB profile would strengthen the network-control argument.

Conversely, evidence that most revenue is low-price procurement, that customers churn to larger providers, that AS43880's active originated space declines, that abuse or outage reports rise, or that the company cannot fund equipment renewal would weaken the thesis.

The present judgment is balanced. Laboratory of Information Technologies LLC matters because it sits at the practical edge where local Ukrainian institutions need small but important services to keep working. Its RIPE records, route objects, public procurement traces and corporate identity establish more than a paper profile. They show a company with real technical responsibility. But responsibility is not the same as economic protection. The business is defensible only if the customer understands that the valuable thing is not a cheap megabit, a simple domain record or a small hosting line.

The valuable thing is one accountable local boundary during disruption.

The unit economics can be put into three plain cases. In the first case, Laboratory of Information Technologies sells a commodity line or a simple hosting account and keeps no explicit continuity premium. The gross margin may look acceptable in a quiet month because upstream capacity, shared servers and routine support are spread across many small accounts. The problem appears when a fault consumes engineer time, a customer needs a restore, a regulator or complainant expects an abuse response, or an outage requires customer-specific communication. The marginal cost of that exception can exceed the profit on several months of a small contract.

If the customer sees only a cheap line item, the operator has little room to recover the cost later.

In the second case, the company sells a managed local service whose price includes named operational obligations. That means the customer pays for a support boundary, not only for capacity. The operator can then justify a higher monthly charge for record maintenance, monitoring, backup procedures, route review, documentation and escalation. This is the strongest case for the company because it aligns the public evidence with the business model. A small LIR with real route objects, local contacts and institutional procurement experience can be valuable if the buyer's alternative is a set of disconnected vendors.

The risk is sales discipline. If the contract language still says only "internet service" or "hosting" while the buyer expects managed continuity, the economics fall back into the first case.

In the third case, the company becomes a bespoke emergency fixer. This can produce loyalty, but it is not automatically a good business. A small team can be pulled into urgent restorations, custom migrations, customer education, power workarounds and procurement paperwork without enough recurring revenue to make the work repeatable. Emergency work also creates selection risk: the customers most likely to ask for exceptions may be the customers least willing or least able to pay for resilience in advance. The company should be cautious about turning goodwill into a shadow balance sheet.

In a wartime market, unpriced emergency capacity is a form of capital commitment.

Power continuity deserves its own economics. For a national operator, batteries, generators and field logistics can be treated as a portfolio investment. For a small Lviv operator, each resilience layer is more discrete. A UPS for core equipment, fuel for a generator, backup arrangements at a hosting site, spare optics, replacement routers and mobile staff time all compete with ordinary payroll and upstream bills. The customer may not see these costs until the lights go out. The operator has to decide whether to publish service tiers that distinguish ordinary best-effort access from continuity-supported service.

Without such tiers, it may be judged against the largest providers' advertising while earning the smallest providers' revenue.

Route diversity has the same character. The RIPE aut-num entity records several import relationships, but public route policy text is not the same as a paid, physically diverse, tested resilience plan. A buyer that truly needs continuity should ask whether its service survives the loss of one upstream, whether DNS and hosting remain reachable when one path fails, and whether the company can document the dependency chain. Laboratory of Information Technologies should welcome those questions where it has answers, because they create a reason to charge for engineering.

If the answer is that some services are best-effort and dependent on upstream conditions, that answer is still valuable. It avoids selling insurance that the company does not have.

The cloud substitute is more subtle than a simple price comparison. A public institution can move a website, mail service or application to a large cloud or mainstream hosting provider and gain scale, tooling and recognised brands. It can also lose local procurement familiarity, local language support, domain-administration help, direct telephone escalation and a single party that understands its specific legacy setup. Laboratory of Information Technologies wins only where the second list matters more than the first. That is a narrower market than "cloud competition", but it is a real one.

Many small organisations do not need a sophisticated global architecture. They need someone competent to keep a modest estate working and to explain failure in practical terms.

The strongest customer profile is therefore an institution with low tolerance for confusion but limited internal technical staff: cultural organisations, research offices, local public bodies, utilities, libraries, local business sites and domain-dependent services. These customers may not generate large revenue individually, but they can generate durable relationships if the company sells reliability, documentation and support as part of the product.

The weakest profile is a price-sensitive buyer that can switch to a mass-market fibre line, a mobile router, a cloud panel or a national provider without caring who manages the underlying resource boundary. Laboratory of Information Technologies should not subsidise that buyer beyond the value of the relationship.

Monitoring should focus on a few observable signals. The first is whether AS43880 continues to originate 185.94.217.0/24 and 185.94.218.0/24, and whether associated LITECH address space remains cleanly documented. The second is whether public procurement continues to show only small generic line items or begins to show more explicit resilience, hosting, domain, support and continuity scopes. The third is whether customer-facing pages, registry records and contact details remain current.

The fourth is whether Ukrainian regulatory measures keep raising the practical cost of continuity through reserve-power, registry or emergency-readiness expectations. The fifth is whether public market signals show more abuse reports, outages or customer complaints than a small operator can absorb quietly.

The decision implication is not to overstate the company. Laboratory of Information Technologies should not be valued or assessed like a scale fibre consolidator. It should be assessed like a small infrastructure steward whose asset is accountable technical control in a specific city and institutional ecosystem. That stewardship can be profitable if priced with restraint and precision. It can also become a low-margin trap if every customer receives continuity-grade attention while paying commodity tariffs. The difference will not be visible in the ASN alone.

It will be visible in contract language, renewal behaviour, service tiers, equipment discipline, customer concentration and the company's willingness to say no to uneconomic support obligations.

Wartime uncertainty cuts both ways. It can make local providers more important because national-scale systems are stressed, customer circumstances are irregular, and a familiar operator can solve practical problems quickly. It can also make them less stable because energy costs, spare-part availability, staff strain and payment cycles deteriorate faster than small invoices can be repriced. A careful judgment must hold both truths at the same time. The company has enough verified control to matter, but the environment can turn that control into liability unless customers pay for the readiness they expect.

That makes the economic answer conditional but not evasive. Laboratory of Information Technologies can command enough margin to fund power, repair, security and renewal if it sells local technical control as a paid continuity service. It cannot do so if it lets every service be compared with commodity access, self-service cloud hosting or a larger operator's headline tariff. The company has the evidence of control; the open question is whether the contracts convert that control into cash before the next outage, upstream change or renewal cycle asks for money.

Sources