Summary
- Digital Raadgivning AS, commonly branded as DIRA, is best understood as a Norwegian SME-focused IT partner with hosting, support, Microsoft 365, security, equipment and continuity services, not as a pure access ISP. Its RIPE NCC membership, IPv4 and IPv6 allocations, and routing through Blix Solutions give it a real resource-holder footprint, but those facts alone do not prove telecom access revenue or independent network scale.
- The strongest evidence for differentiated demand is customer continuity. DIRA publishes references from organisations such as Renas, A Bygg, Civita, Kirkens SOS, Forlagssentralen, Fafo, Greenbit, Starco and Visma Real Estate/Webmegler, with use cases that emphasize uptime, security, local support, hosting, Microsoft administration and outsourced IT responsibility.
- The financial picture is respectable for a small service business: public registry-derived accounts show about NOK 45.3 million of 2025 revenue, a 10.6 percent operating margin, NOK 4.8 million of operating profit, 14 employees and an equity ratio above 40 percent. That is profitable, but it is still far below the scale of cloud platforms and larger Nordic managed-service groups.
- The investment case depends on whether Nestit ownership and DIRA's local trust can turn hosting and managed IT into packaged, repeatable services without losing the relationship intensity that customers appear to value. The judgment would change materially if DIRA disclosed durable contracted recurring revenue, customer retention, gross margin by hosting and support line, customer concentration, or evidence that its own resource position materially lowers customer cost or improves service quality versus cloud and larger MSP alternatives.
The incentive is to stay essential where hyperscale is too blunt
Management's incentive at Digital Rådgivning AS is not to outbuild Microsoft, Amazon, Google, Telia, Telenor, Blix or the national managed-service integrators. That contest would be unwinnable.
The incentive is to remain the party that smaller and mid-sized customers call when standardized platforms meet messy operating reality: an old line-of-business application that still needs remote desktop delivery, a construction site that needs secure access for many temporary users, a charity whose volunteers need support outside normal office assumptions, a research foundation that needs safe access to data from home and fieldwork, or a distributor whose downtime has immediate commercial cost.
That is the economic opening. Below cloud scale, value is not created by owning a generic rack, a small IPv4 block or a Microsoft reseller relationship on its own. Value is created if customers pay for accountability: someone local enough to understand their workflow, technical enough to manage networks and hosted environments, and disciplined enough to keep security, backup, endpoint policy and support working as one service. DIRA's public positioning is built around that promise.
Its website describes the company as an IT partner delivering "Total Teknisk Trygghet" from strategy and planning through products, services and support. Its service pages cover Microsoft 365, support, security, equipment, hosting and a structured process that starts with mapping and evaluation before moving to advice, implementation and operations.
The danger is that the same promise can become a cost trap. Customers want personal service, broad competence and low risk, but they may not want to pay enough to fund a small provider's full operating burden. DIRA has to keep people skilled across Microsoft 365, endpoint security, networking, backup, hosting, user support, mobile, meeting-room equipment and legacy applications. It has to buy or rent data-centre capacity, maintain hardware, coordinate upstream network services, carry professional liability for customer operations, and remain responsive enough that customers do not drift to a larger MSP or direct cloud platform.
If each customer environment is bespoke, growth adds complexity as well as revenue. If services are standardized too aggressively, DIRA risks becoming another reseller in a market where the platform owner captures much of the margin.
The 2026 acquisition by Nestit Group changes the incentive but does not eliminate the trade-off. DIRA's own acquisition note says the company became part of a Nordic IT and office-solutions group that keeps local brands, staffing and customer relationships while adding broader resources, purchasing power, cross-selling and service packaging. MVI's release frames the deal as Nestit's first add-on acquisition in Norway and a step toward building a stronger platform in the Oslo region. That gives DIRA a path to scale benefits it could not easily build alone.
It also introduces the standard consolidation test: can a local-service company become more efficient inside a group without becoming less local to the customers who bought the service in the first place?
DIRA is an IT partner with a resource-holder footprint, not a pure access network
The company identity matters because the article's economic question is about resource-holder status, not simply about IT consulting. Public Norwegian registry data identifies Digital Rådgivning AS as a limited liability company registered in January 2001, founded on 2 January 2001, based at O.H. Bangs vei 17 in Høvik, Bærum, with business classification 46.500, wholesale of information and communication technology equipment. The official registry page also points to www.dira.no and shows the company as registered in the VAT and business registers. Public registry-derived company pages list 14 employees and Lars Johnsen as general manager; DIRA's own acquisition article says Johnsen had been sole owner until the sale to Nestit.
The operating boundary is broader than that industry code implies. DIRA's own materials describe an IT partner for small and medium-sized businesses, with services spanning Microsoft 365, support, security, equipment, hosting, backup, endpoint and network administration, and advisory work. The "about" page says the company was established with a vision of delivering cost-effective IT solutions to SMEs and that more than 150 customers use DIRA for digital and technical needs. The support page positions DIRA as an outsourced IT department.
The equipment page includes networks, PCs, mobile, meeting rooms, camera surveillance and access systems. The security page emphasizes Microsoft 365 configuration, endpoints, backup, access control and user training. The process page describes recurring mapping, advice, implementation and operations.
The resource-holder evidence is specific. RIPE NCC's public member list includes Digital Raadgivning AS as a Norway-based member. RIPE Database records identify ORG-DRA11-RIPE as Digital Raadgivning AS, country Norway, organisation type LIR, with Norwegian registration number 982 848 210. RIPE records show the IPv4 allocation 185.12.72.0 - 185.12.75.255, netname NO-DIRA-20121205, status ALLOCATED PA, created in December 2012. They also show the IPv6 allocation 2a02:e340::/29, netname NO-DIRA-20121116, status ALLOCATED-BY-RIR, created in November 2012.
Route objects show origin AS50304, and RIPEstat currently associates the IPv4 /22 with AS50304, holder Blix Solutions AS. RIPEstat's announced-prefix data for AS50304 shows 185.12.72.0/22 and 2a02:e340::/32 visible in the current observation window.
That evidence establishes a meaningful operational footprint. A company with RIPE LIR status and directly registered number resources is not merely selling laptops. It has had enough network-facing operations to justify address resources and route objects. But it does not automatically establish DIRA as an independent access ISP. AS50304 is Blix Solutions AS, and both the RIPE records and live routing evidence point to Blix as the origin network for the visible DIRA prefixes.
DIRA's own hosting page says its secondary data centre is located at Blix on Alnabru, and the RIPE records list Blix contacts and Blix maintainers alongside DIRA in technical and route-maintenance fields. The better reading is that DIRA holds resources and operates hosting/customer environments using upstream and data-centre partners, rather than controlling a full access network from last mile to transit.
That distinction is central to value. Resource-holder status can help a hosting provider preserve address continuity, manage customer migrations, run private-cloud services and avoid complete dependence on hyperscale public IPv4 pools. It can also become a small fixed cost and administrative obligation if the company cannot tie the resources to differentiated customer demand. DIRA's address footprint has economic meaning only if it helps customers buy continuity, control, latency, isolation or migration flexibility that they cannot get as cheaply or reliably from cloud-native substitutes.
The revenue pool is recurring service, not address ownership
DIRA's revenue pool appears to be recurring managed IT and hosting, supported by project work and product supply, rather than monetisation of addresses by themselves. The company's own service pages are explicit about the customer problem: SMEs have fragmented IT, many vendors, weak internal competence and growing security exposure. DIRA offers to become the single accountable partner across Microsoft 365, support, devices, network, hosting, backup and security. That is a managed-service logic.
Customers do not pay primarily for the existence of an IPv4 /22; they pay because a provider packages infrastructure, tools and judgement into a lower-risk operating model.
The customer references reinforce this. Renas is described as relying on DIRA for data security, Microsoft licences, databases, data warehouse, private cloud, backup, meeting-room operation and support around sensitive member and transaction data. Civita is described as using DIRA for server, network and Microsoft 365 services, and as having moved data from a physical server into a cloud solution with DIRA. Kirkens SOS is described as using DIRA for Office 365 licence and access administration, Intune setup on employee and volunteer machines, support for staff and volunteers, and advice around other technical suppliers.
Forlagssentralen is described as relying on DIRA for local networks, servers, infrastructure, network components, routers, switches and backup, with critical round-the-clock operations for publishers and online retailers.
These examples are commercially important because they show willingness to outsource technical accountability, not just buy equipment. They also show a pattern of services with contractual durability. A customer that depends on DIRA for endpoint management, licence administration, backup, network changes, support and hosted workloads faces operational switching costs. The switching cost is not a legal lock-in by itself; it is the accumulated knowledge of customer systems, users, routines and failure modes.
A support desk that understands a customer's meeting rooms, access rights, old applications and executive tolerance for downtime can be more valuable than a cheaper generic ticket queue.
At the same time, the evidence does not show customer-level revenue, gross margin or contract length. DIRA publishes strong customer stories, but those stories are promotional and selective. They prove that named customers exist and that DIRA has delivered valued work; they do not prove how much each customer pays, whether revenue is monthly recurring, whether prices are indexed, or whether the service mix is margin-accretive. A customer can be a useful reference and still represent low-margin support labour.
A hosting customer can be sticky and still require expensive hardware refreshes, backup storage, software licences and on-call capability.
The public financials show a business that has grown and remained profitable, but not at platform scale. Firmadatabasen, citing registry accounts, lists 2025 operating revenue of about NOK 45.3 million, operating costs of about NOK 40.5 million, operating profit of about NOK 4.8 million, annual profit of about NOK 3.8 million and operating margin of 10.6 percent. The same page shows revenue of NOK 42.9 million in 2024, NOK 39.0 million in 2023 and NOK 39.1 million in 2022. That pattern suggests modest growth with improved 2025 profitability. It does not suggest explosive software economics.
For a people-and-infrastructure service company, a double-digit operating margin is healthy; for a platform business, it would not be especially high.
The economic question is therefore not whether DIRA's resource footprint has value in isolation. It is whether resource control, hosting know-how and customer intimacy improve the economics of recurring service. If the address and hosting assets make DIRA harder to replace, reduce third-party public-cloud charges, or allow it to sell resilient private-cloud and hybrid services at a margin, they support value creation. If they merely accompany a labour-intensive support business, they are a cost of being credible in the infrastructure layer.
Customer evidence points to continuity demand, but not concentration disclosure
The best evidence for DIRA's differentiated demand is the nature of the customer problems it describes. Renas processes electronics waste and battery volumes on behalf of thousands of member companies and is described by DIRA as requiring high security, uptime and data handling. A Bygg works across large construction projects with many external contacts needing digital access, and DIRA's case study says the work includes internal systems, routines, software upgrades, network and systems setup at construction sites, and continuous monitoring.
Forlagssentralen distributes for roughly 200 publishers and online retailers; its case describes local networks, servers, routers, switches and backup as business-critical. Kirkens SOS operates crisis services with employees and a large volunteer base; its case describes support and device management as tied to round-the-clock operations.
These are not glamour workloads, but they are economically useful. Customers with operational continuity needs are often willing to pay for prevention. The Starco case is especially revealing. DIRA's customer story says Starco's CFO described downtime in high season as potentially costing hundreds of thousands of kroner per hour and that IT platform, redundancy, backup and documentation mattered in a sale process. That is the kind of use case where infrastructure advice has board-level relevance.
If DIRA can repeatedly demonstrate that its work lowers outage probability or improves due-diligence readiness, it can earn value beyond commodity support.
The Visma Real Estate/Webmegler hosting reference points in the same direction. DIRA's case says Visma wanted to move self-operated servers for Webmegler and Webtemp to a third party, reduce risk, free internal time and secure more stable operations. The described solution includes scalable resources, redundant environments, proactive monitoring and support, with fixed and variable cost elements.
Whether every detail is independently verifiable is less important than the type of demand it represents: a customer with a business application that is not simply turned into a commodity SaaS overnight, but also no longer wants to carry all server-operation risk internally.
The relationship evidence also spans time. DIRA says it has more than 150 customers. Several customer cases describe long histories: Civita since 2006, Forlagssentralen since DIRA's start, Renas with a history reaching back roughly 25 years, and Starco with DIRA involved through a decade-plus growth journey. Long relationships support the case that DIRA sells trust and continuity. They are also an economic warning. Long relationships can be underpriced if they were built in an earlier cost environment and never repriced fully for security, cloud licensing, personnel and backup demands.
A local provider can carry "friend of the company" expectations that larger providers resist.
The missing piece is concentration. DIRA's public material names strong customers, but it does not disclose revenue distribution. A small provider with NOK 45 million of revenue could be well diversified across 150 smaller accounts, or it could be meaningfully dependent on a handful of hosted and managed-service customers. The difference matters. A diversified book makes customer churn less dangerous but may require heavy support coordination. A concentrated book can produce attractive margins if workloads are standardized, but one lost account can move the operating margin.
The acquisition article's list of customers, and the volume of customer references, are encouraging, but they are not a substitute for contracted revenue data.
This is where the judgment has to remain explicit. DIRA has evidence of real customer demand, including business-critical continuity use cases. It does not have public evidence of enough contract durability, customer diversification or gross margin by customer segment to prove that the demand is economically differentiated. The current fact pattern supports a cautiously positive view of customer relevance, not a definitive conclusion that DIRA can price above its cost of complexity.
Hosting gives DIRA control, but also makes it carry fixed operating risk
Hosting is the part of DIRA's model that most directly connects resource-holder status to customer economics. The company's hosting page describes "DIRA Sky" as a traditional Remote Desktop Services solution for customers that still need on-premise applications but do not want to run the infrastructure themselves. It says customers can choose shared or isolated environments, that all servers are separated behind a firewall in isolated environments, and that customers work on dedicated nodes.
The same page describes private cloud and traditional hosting for customers needing rented resources, plus advice, development and operations.
That position is commercially coherent. Many SMEs do not migrate cleanly from local servers to pure SaaS. They have accounting systems, property systems, databases, integrations, document workflows and access-control patterns that make hybrid operation rational. A local provider can host legacy or specialized workloads, pair that with Microsoft 365, manage backups and endpoints, and provide one support path. In such a context, DIRA's address resources and network relationships may help with stable service delivery, customer isolation, migration control and continuity.
The infrastructure claim is also concrete. DIRA says it has built two robust data centres with modern hardware and good uptime. It identifies the primary centre as Digiplex Ulven and the secondary as Blix at Alnabru, and says it offers daily off-site image backup to hosting customers plus layer-2 connections between customers and the data centre for performance. Blix's own public material shows why Blix is relevant to DIRA's operating surface: AS50304 has broad peering, transit, data-centre services, local network fabric, BGP operations, LIR services and Oslo data-centre capacity.
Blix's BDC Oslo page describes a facility with 1,000 square metres-plus footprint, 1.5 MW capacity, ISO 27001 certification, renewable hydro power, on-site security and multiple dark-fibre providers.
Control, however, is not the same as cost advantage. Hosting requires hardware refresh cycles, backup storage growth, monitoring, patching, electricity exposure through data-centre pricing, licences, security tooling, incident response and support. A small provider can design a better fit for a customer than a hyperscale cloud dashboard, but it cannot match hyperscale purchasing power or automation breadth. If DIRA's hosted environments are too customized, each account becomes a mini-platform with its own maintenance burden.
If they are standardized, customers may ask why they should not use Azure Virtual Desktop, Windows 365, direct SaaS or another managed provider.
Microsoft's own Azure Virtual Desktop materials show the substitute clearly. Azure Virtual Desktop provides secured Windows desktops and apps, usage-based compute, no long-term commitments, multi-session options and eligibility through Microsoft 365 Business Premium and other licences. That is not a perfect replacement for every DIRA environment. Customers still need architecture, migration, governance, identity, backup and support. But it caps pricing power. DIRA must justify why its private or hybrid hosting is better for a particular workload than a direct or managed Azure path.
Public IPv4 economics complicate the picture. AWS, Google Cloud and Azure all make clear that public IPv4 addresses are not free in the public cloud; AWS introduced a charge of USD 0.005 per IP hour for all public IPv4 addresses from February 2024, Google lists charges for static and ephemeral external IP addresses, and Azure charges for public IPv4 resources or prefixes except in some bring-your-own-address contexts. DIRA's own IPv4 resources can therefore have operational value if they let customers avoid some public-cloud address friction or preserve address reputation and continuity. Yet a /22 is only 1,024 addresses.
It is not a giant asset base, and it does not remove the need for good service design.
The conclusion is that hosting can differentiate DIRA, but only if capacity discipline is strong. The fixed-cost base has to be spread across enough repeatable hosted workloads. Backup and security need to be packaged, not reinvented. Hardware and data-centre commitments need enough utilization to avoid margin drag. A small private-cloud business is attractive when customers buy resilience and support together; it is vulnerable when customers compare only compute and storage line items.
RIPE resources help availability and switching costs only when tied to managed workloads
DIRA's RIPE position is a useful evidence point because it shows operational history and administrative competence. RIPE NCC does not simply hand out number resources without a registry relationship and process. Digital Raadgivning's organisation record as a LIR, the IPv4 /22 allocation, the IPv6 /29 allocation and the route objects through AS50304 all indicate a long-lived network-resource footprint dating back to 2012. RIPE NCC's member list places the company among local Internet registries serving the Norwegian market.
The question is how that resource position turns into customer value. In the strongest case, a provider with its own allocations can offer stable addresses for hosted customer environments, preserve routing continuity through migrations, manage reverse DNS and abuse processes, use IPv6 without waiting for a cloud-provider constraint, and avoid dependence on rented addresses with uncertain reputation. For customers that run externally reachable services, strict allow lists, legacy integrations or partner connectivity, address continuity can matter.
It can also support a cleaner exit from one hosting platform to another if the provider controls the numbering and routing plan.
In the weaker case, resources are mostly symbolic. Many SME customers never ask whose address block is used behind a hosted desktop, Microsoft 365 tenant or backup service. They care that the service works, that access is secure, that support answers quickly and that invoices are predictable. If the customer does not perceive address continuity as a risk reducer, DIRA cannot charge much for it directly. The cost of RIPE membership is also not zero. RIPE's 2026 charging scheme sets an annual contribution of EUR 1,800 per LIR account, with additional charges for certain independent resources and ASNs.
For DIRA's scale, the direct RIPE fee is not huge, but it is part of a broader compliance and operational overhead.
The routing evidence points to both value and dependence. RIPEstat shows the DIRA IPv4 prefix announced under AS50304, and bgp.tools lists 185.12.72.0/22 and 2a02:e340::/32 as visible under Blix Solutions AS. bgp.tools also lists Blix with two upstreams, extensive peering and high Norwegian rankings across peer, cone, host and IPv6-space metrics. Blix's own site emphasizes its BGP network, multiple redundant internet connections, extensive peering, native IPv6 and carrier-neutral data-centre options. That gives DIRA a stronger operating base than a provider relying on a single generic hosting account.
It also means DIRA is not fully independent at the network layer. If Blix is the origin network for DIRA's advertised resources, DIRA's resilience and economics depend in part on Blix pricing, performance, incident handling and strategic continuity. That is normal in regional hosting markets. Few small IT providers operate every layer themselves. But it affects margin. The provider that owns the end customer but depends on upstream and data-centre partners needs enough gross margin after those partner costs to fund support and investment.
The practical read is that RIPE resources improve DIRA's credibility and optionality, but they are not a moat by themselves. They become a moat only when paired with customer workloads that are hard to move, contracts that reward uptime, and operational processes that reduce failure cost. Otherwise, resource-holder status is infrastructure hygiene in a market where customers buy outcomes.
Supplier concentration is visible in Microsoft, data-centre and Blix dependencies
DIRA's model has visible supplier concentration, and that concentration is not inherently bad. The company serves SMEs, and SMEs increasingly standardize on Microsoft 365, Teams, Exchange Online, OneDrive, SharePoint, Intune, Defender and related identity/security tools. DIRA's Microsoft 365 page says it handles licences, training, configuration, security and support. Its security page says many firms already pay for Microsoft 365 but do not use the built-in security functions well, and DIRA helps activate and tailor those tools. Its customer cases repeatedly reference Office 365, Microsoft 365, Intune and Microsoft licences.
That dependency is rational because Microsoft is the control plane for many SME work environments. Microsoft Intune is marketed as cloud-based endpoint management across Windows, Android, macOS, iOS and Linux, and Defender for Business is specifically designed for small and medium businesses up to 300 users, offering endpoint protection against ransomware, malware, phishing and other threats. DIRA can create value by configuring those tools, enforcing policies, managing devices, training users and responding to incidents. The customer buys local operational competence wrapped around a global platform.
The downside is that platform owners compress margins over time. Microsoft can bundle more security, management and support features into Business Premium or higher-tier subscriptions. It can push customers toward direct cloud administration, partner marketplaces, Azure Virtual Desktop, Windows 365 and standardized security baselines. DIRA benefits from Microsoft adoption, but it also depends on Microsoft pricing, licensing changes, product roadmaps and partner economics. The more a service is merely licence administration, the easier it is to replace.
The more it involves customer-specific security posture, endpoint cleanup, workflow design, user support and incident response, the stronger DIRA's position.
Data-centre and network suppliers create another concentration layer. DIRA identifies Digiplex Ulven as its primary data-centre location and Blix at Alnabru as its secondary location. Blix appears in RIPE technical and routing context and originates DIRA's visible resources through AS50304. Blix's public materials show strong network capabilities, but the strategic implication for DIRA is clear: resilience depends on partner quality, and margin depends on partner pricing. If colocation, cross-connect, transit, backup or power costs rise faster than DIRA can reprice contracts, hosting margin will compress.
Hardware and mobile dependencies add still more exposure. DIRA's equipment page says it helps customers with networks, PCs, mobile, meeting rooms, camera surveillance and access systems; it also describes DIRA as a certified Telia partner for business mobile management. Hardware resale and mobile administration can deepen customer relationships, but they can also carry low margins and working-capital needs. The risk is that DIRA becomes responsible for a broad technical estate while capturing only modest margin on the underlying products.
Nestit ownership may reduce some supplier pressure. DIRA's acquisition article says joining Nestit creates opportunities around purchasing, cross-selling and service packaging. A Nordic group with more than NOK or SEK-scale purchasing volume may negotiate better terms, share security expertise and standardize tools. But group scale also tends to reveal which services are genuinely profitable. If DIRA's local model works because staff absorb complexity informally, Nestit will need to professionalize delivery without breaking the culture of responsiveness.
The economic answer is not to eliminate supplier concentration. That would be unrealistic. The answer is to own the customer relationship and the integration logic. DIRA needs Microsoft, Blix, data-centre facilities, hardware vendors and mobile carriers to be inputs, not the product. If customers believe they are buying DIRA's judgement and accountability, supplier concentration is manageable. If customers believe they are buying the same platforms they can buy elsewhere, DIRA becomes a price-taker.
Unit economics improved in 2025, but scale remains below platform economics
The public numbers show a company that is profitable but small. Firmadatabasen's registry-derived accounts show 2025 operating revenue of NOK 45.3 million, up from NOK 42.9 million in 2024 and about NOK 39 million in both 2023 and 2022. Operating profit rose to NOK 4.8 million in 2025 from NOK 2.4 million in 2024, with 2025 operating margin at 10.6 percent. Annual profit was NOK 3.8 million, EBITDA was NOK 6.0 million, total assets were NOK 14.7 million and equity was NOK 6.5 million. The equity ratio of 44.3 percent and liquidity ratio of 1.6 suggest a balance sheet with some resilience, not an overlevered roll-up target.
Those figures support three observations. First, DIRA is not a distressed company chasing an acquisition because the stand-alone model failed. It appears to have grown revenue modestly and improved profit in 2025. Second, the margin is good enough to show customers pay for value above pure labour reimbursement. Third, the scale is still below the threshold where platform economics dominate. A company with 14 employees and NOK 45 million of revenue can be very valuable to its customers, but it cannot spread engineering, security operations, automation and procurement overhead the way a larger MSP or cloud provider can.
Revenue per employee, using the 14-employee figure, is roughly NOK 3.2 million. That can be read in two ways. It is healthy for a small IT services and hosting company that also resells equipment and licences. It also implies that a meaningful portion of revenue may pass through to suppliers, hardware, software, data-centre and subcontracted inputs. Without gross margin disclosure, revenue per employee cannot be treated as a pure productivity metric. A reseller-heavy business can show high revenue per employee with lower gross margin; a specialized managed-service business can show lower revenue per employee but higher recurring gross margin.
Capital intensity is also ambiguous. The balance sheet shows tangible fixed assets around NOK 1.8 million in 2025, down from NOK 2.9 million in 2024 and NOK 3.7 million in 2023. That suggests the business is not carrying a huge owned-infrastructure asset base relative to revenue. But hosting can still require regular replacement and off-balance operational commitments through colocation, software, backup and leased services. The company's own acquisition article says recent years included major investment in technical solutions and that hosting, storage and especially AI challenge customer costs and security.
That phrasing implies DIRA sees investment pressure even if public balance-sheet line items look manageable.
The margin risk is therefore not immediate insolvency; it is strategic compression. Public cloud continues to standardize compute, storage, identity, endpoint management and virtual desktop delivery. Security vendors automate more of the baseline. Larger MSP groups can bundle procurement, SOC, service desk, field services and cloud migration. DIRA must keep enough specialized value at the customer interface to defend its margin. The 2025 improvement shows the company can be profitable under current conditions.
It does not prove the margin can withstand a longer period of wage inflation, cloud repricing, security tooling cost, customer bargaining and acquisition-integration demands.
This is why Nestit matters. A larger group may add purchasing benefits, shared tooling, professional services depth and cross-border knowledge. It may also push for revenue growth toward group targets. If that growth is achieved by adding standardized recurring service to DIRA's local relationships, margins can improve. If it is achieved by taking on more complex customers without delivery standardization, the cost base will expand with the revenue.
Cloud substitution caps pricing power unless DIRA sells accountability
The credible substitutes for DIRA are not theoretical. A customer can buy Microsoft 365 directly, use Intune and Defender, move desktops and legacy applications to Azure Virtual Desktop, host new applications in Azure, AWS or Google Cloud, buy mobile services directly from a telecom operator, hire a larger MSP, or keep a small internal IT generalist and use specialist contractors. DIRA has to win against those alternatives on a total-cost-and-risk basis, not just on familiarity.
The cloud argument is particularly sharp for hosting. Azure Virtual Desktop promises secure remote desktops and apps, usage-based pricing, multi-session options and Microsoft licence eligibility. Windows 365 offers a more SaaS-like cloud PC model. AWS and Google Cloud provide compute, storage, networking and backup primitives globally. For many greenfield workloads, a local private-cloud or RDS environment will not be the obvious default. Customers building new software, using modern SaaS applications or wanting elastic scale can bypass a local hosting provider.
But substitution is not the same as displacement. Many SMEs do not want to manage Azure cost controls, identity policies, endpoint baselines, backups, conditional access, device compliance, mobile enrolment, role-based access, disaster recovery and vendor support themselves. They can buy the platform directly but still need an operating partner. DIRA's opportunity is to turn cloud substitution into managed cloud advisory and operations.
If customers ask "why not Azure?", DIRA's answer cannot be "because we have servers." It has to be "because this workload, risk profile and support need are better served by this mix of private hosting, Microsoft cloud and managed operations."
Public IPv4 pricing gives DIRA one narrow but real talking point. AWS charges for public IPv4 addresses, Google Cloud charges for static and ephemeral external IPs according to status, and Azure charges for public IPv4 resources in multiple configurations. Bring-your-own-IP and provider-controlled address plans can be economically relevant for address-heavy workloads. However, most DIRA customers are unlikely to be address-heavy enough for this alone to drive procurement. Address control is a supporting factor, not the headline.
Local support is the stronger differentiator. Greenbit's case describes DIRA simplifying a fragmented IT environment, improving meeting rooms, consolidating telephony administration and supporting infrastructure across offices, petrol stations and car washes in Eastern Norway. Civita's case emphasizes a long relationship, periodic on-site consultant presence, cloud migration and fast remote support. Kirkens SOS emphasizes support for employees and volunteers around services that need to work around the clock.
These are contexts where a direct cloud provider is not a full substitute because the work is organisational and operational, not just technical.
Pricing power therefore depends on how DIRA frames value. If the offer is "we can host and support the same tools," larger providers can undercut or outbundle. If the offer is "we carry the operational downside for your specific workflow," DIRA can defend margin. That requires contracts that translate accountability into revenue: monthly managed-service fees, security packages, backup and continuity tiers, response-time commitments, project governance and periodic reviews.
The customer must understand that paying DIRA is not buying generic labour; it is buying a lower probability of disruption and faster recovery when disruption happens.
The discipline is to avoid strategy as marketing. A broad list of services is not a strategy. DIRA's strategy is credible only if it allocates resources toward the services where local knowledge, hosting control and Microsoft/security competence reinforce one another. It should not chase every hardware, telecom, advisory, security, cloud and support opportunity equally. The margin risk below cloud scale is that breadth becomes obligation without pricing.
Regulation and security raise the floor for competence, not the ceiling for margins
Norway's regulatory environment reinforces the importance of operational competence, but it does not automatically create a moat for DIRA. Nkom says providers of public electronic communications networks or services have a duty to register their activities, including providers that install, operate and give access to public electronic communications networks, providers of public telephone services, and providers of transmission capacity. Nkom also supervises telecommunications providers, manages frequencies and numbering resources, and investigates competition issues in electronic communications markets.
DIRA's public evidence does not establish that it is a public ecom provider in those categories; its resource and hosting activities simply mean the boundary should be understood carefully.
The practical regulatory exposure is broader than telecom registration. Customers increasingly expect compliance around data protection, access control, backup, endpoint security, incident handling and supplier management. DIRA's security page names phishing, ransomware, data breaches, Microsoft 365 security features, network and endpoint security, backup, emergency preparedness, access control and training. The A Bygg, Renas, Civita, Fafo and Kirkens SOS cases all revolve around sensitive data, uptime or user access. This is where compliance becomes demand.
A construction company with thousands of external contacts, a research foundation handling data in fieldwork, or a crisis-service charity with volunteers cannot treat IT as discretionary plumbing.
Security demand helps DIRA because SMEs usually lack internal specialist depth. Microsoft Defender for Business is aimed at small and medium-sized businesses, but buying a licence does not configure policy, train users, clean up legacy access rights or integrate backups. Microsoft Intune can manage and protect endpoints, but it still requires design and ongoing administration. DIRA's value sits in implementation and operations. Security becomes sticky if DIRA can show customers that posture improves over time and that incidents are handled quickly.
Security also raises costs. A provider that promises ongoing monitoring, backup, endpoint protection, Microsoft tenant hardening, user support and incident response needs skilled staff and tooling. It needs documentation, escalation routines and insurance-aware processes. It may need to support customers outside office hours when a critical service fails. Customer expectations rise faster than willingness to pay if security is sold as a generic included feature. That is a classic MSP margin trap.
The new ownership context could help again. A Nordic group can share security templates, procurement, professional development and response playbooks. It can spread specialist knowledge across portfolio companies. But portfolio scale can also attract customers with higher security expectations. If DIRA moves upmarket under Nestit, contract discipline will matter more. Larger customers often demand better reporting, tighter service levels and lower unit prices.
Regulation and security therefore raise the minimum bar. They make amateur IT support less acceptable and increase demand for providers like DIRA. They do not guarantee premium economics. The ceiling on margin comes from the ability to convert competence into packaged recurring revenue, not from the mere existence of compliance pressure.
Unofficial market signals show consolidation, not a stand-alone moat
The clearest market signal is the Nestit acquisition. DIRA's own note and MVI's announcement both describe a Nordic consolidation strategy for locally rooted IT companies. DIRA says Nestit had 19 companies in the Nordics, more than SEK 1 billion in revenue, backing from MVI, and a target of SEK 1.5 billion in revenue by 2028. The article says Nestit would preserve local brands, identities, staffing and customer relationships while giving DIRA access to broader resources and a Nordic network. That is the buyer's thesis: local MSP brands have customer trust, but the economics improve when grouped.
This signal should be read carefully. Acquisition interest validates that DIRA has something worth buying: a customer base, a local brand, technical staff, recurring work, hosting know-how and Norwegian market presence. It also suggests that the market sees scale as increasingly important. If the best way for DIRA to grow is to join a group, that is not evidence of a stand-alone resource-holder moat. It is evidence that the moat is partly local and relational, while procurement, tooling, security and cross-selling benefits require group scale.
The broader network market sends a similar signal. bgp.tools lists many Norwegian networks, hosting providers, telecom operators, IT service firms and data-centre-connected organisations with autonomous-system footprints. Blix itself ranks highly in Norwegian network metrics and lists extensive peering and network services. Larger telecom and hosting names appear across rankings and public sources. In that environment, DIRA is not structurally scarce as a network operator. Its scarcity, if any, comes from local customer knowledge and integrated delivery.
There are also informal signals in the customer cases. Customers praise fast response, familiarity, cost focus, practical advice and the feeling that DIRA behaves like an internal resource. Those signals are subjective and come from DIRA's own marketing pages, so they should not be treated as independent proof. But they are directionally consistent across many cases. The same themes appear with customers in research, construction, publishing logistics, crisis services, energy retail, policy debate, waste recycling and real estate software.
That breadth suggests DIRA's repeatable demand is not a single vertical; it is the need for trusted outsourced IT in organisations too complex for ad hoc support but too small or focused to build a full internal technology department.
The absence of broader public controversy is also worth noting in a limited way. Public searches surfaced acquisition, customer and registry evidence, not obvious sanctions, insolvency or major public incident signals. That is not proof of clean operations, and it should not be overstated. It simply means the public fact pattern available for this article does not show a material adverse market signal.
The unofficial-signal conclusion is disciplined: market chatter and public positioning point to consolidation value and customer trust, not to a protected infrastructure franchise. DIRA's challenge is to turn the former into the latter through service packaging, retention, careful customer selection and a cost base that benefits from Nestit scale.
The facts that would change the judgment
The current judgment is that DIRA has enough differentiated demand to be economically relevant, but not enough public evidence to prove that resource-holder status itself creates durable value above the cost base. The company looks like a credible, profitable local IT and hosting provider with sticky customers and a real network-resource footprint. It does not look like a scaled infrastructure platform.
The margin risk is that fixed hosting costs, Microsoft and data-centre dependencies, security tooling, wage pressure and customer-specific support complexity leave it as an infrastructure price-taker unless it converts local trust into standardized recurring services.
Several facts would make the conclusion more positive. The first is contracted recurring revenue. If DIRA disclosed that a high share of revenue is monthly recurring, under multi-year managed-service or hosting contracts, with renewal rates above 90 percent and price-indexing clauses, the customer-continuity thesis would be materially stronger. The second is gross margin by service line. If hosting, backup and managed security carry attractive gross margins after colocation, software, hardware depreciation and support costs, resource-holder status would look economically productive rather than merely operational.
The third is customer diversification. Evidence that no customer accounts for an uncomfortable share of revenue would reduce concentration risk. The fourth is documented uptime, incident response and recovery performance. Proof that DIRA materially reduces customer downtime would support premium pricing.
Evidence around resource use would also matter. If DIRA can show that its IPv4 and IPv6 resources are used by high-value hosted customers, support portability, lower public-cloud address cost, preserve address reputation or make migrations easier, the RIPE footprint becomes more than an artefact of history. Conversely, if the address space is lightly used, routed primarily for legacy reasons, or not connected to revenue-generating workloads, it should be treated as a minor supporting asset.
Nestit integration is another swing factor. A positive case would show shared purchasing, security tooling, automation and specialist support improving DIRA's margin without weakening local customer relationships. Cross-selling into Nestit's Nordic base could make DIRA's infrastructure and hosting competence more valuable. A negative case would show integration overhead, brand dilution, staff turnover or a push into larger but lower-margin accounts.
The facts that would make the judgment worse are equally clear. A major customer loss, unmanaged churn after the acquisition, declining hosting utilization, rising data-centre costs, inability to reprice Microsoft/security support, or evidence that DIRA relies on a few low-margin hardware and licence resale accounts would shift the picture toward price-taker risk. So would a finding that customers use DIRA mainly for commodity support while strategic cloud decisions move elsewhere.
For now, DIRA's incentive is obvious and rational: remain the accountable operator for customers who are too operationally exposed to manage IT casually, but too small to build everything internally. The company has public evidence of customer trust, a useful resource-holder position and a profitable recent year. The open question is whether that is enough to earn returns below cloud scale. The answer depends less on the address block than on contract discipline, service packaging and the ability to make customers pay for avoided downside before the downside appears.