Summary

  • Internetten Teknoloji is best understood as a hybrid infrastructure supplier: a Gebze-based industrial networking distributor with project support, hotspot/logging software, ISP workflow tools and a small routed network, not as a broad hyperscale substitute.
  • The investment judgment is conditional but clear: the company can preserve attractive local margin only if it prices software, support and hosted compliance services as currency-protected managed infrastructure. If it lets lira renewals lag imported hardware, data-centre power, bandwidth and support labour, the model becomes a reseller squeezed between customers and global vendors.
  • Public evidence supports a defendable niche around MikroTik/Ubiquiti/RF/GPON projects, WiPoint hotspot subscriptions, cloud logging and ISP support. It does not yet support a claim that Internetten has the routed scale, IPv6 footprint, multi-cloud product depth or balance-sheet room to win commodity VPS or general hosting business against Radore, Turhost, Natro, TurkHosting, AWS or Azure.
  • The facts that would reverse the judgment are audited recurring software revenue, low churn, explicit supplier terms, demonstrated multi-upstream resilience, larger live hosted workload counts, and proof that WiPoint/WiRadius can expand beyond the existing hardware channel without consuming support capacity.

The renewal is the business

The economic incentive starts with a small but frequent decision: a hotel, dormitory, cafe, municipality, factory or local ISP has to renew the tools that keep users online and logs defensible. The customer does not begin by shopping for an abstract cloud. It begins with a working problem. A public Wi-Fi network must authenticate guests. A MikroTik router must be configured. A customer database or payment process must not break. A 5651 logging archive must be retained in a form the customer believes will survive a later request.

A local operator needs a supplier that will answer the phone in Turkish, ship a replacement quickly, explain whether a VSOL OLT, a MikroTik switch or a Ubiquiti bridge is the right choice, and then stand behind the installation.

Internetten Teknoloji's public materials fit that renewal moment. The company describes itself as an industrial networking distributor, not a conventional consumer web host. Its owned pages emphasize MikroTik distribution and support, Ubiquiti products, RF Elements, Wi-Fi, ISP and data-centre project work, telecom infrastructure, software, device supply and technical service. Its storefront carries routers, switches, GPON equipment, fibre accessories, PoE devices, access points, antennas, monitoring software, hotspot software and many vendor brands. Its WiPoint product sells cloud hotspot access control and annual user-count packages.

Its SysLog page sells cloud logging and two-year retention as a way to avoid local disk, power, hardware and space costs. Its WiRadius site addresses the operating pain of smaller ISPs: subscriber management, field work, devices, payments, reporting and accounting.

That bundle matters because the lowest-cost provider of a virtual server is rarely the best provider of an access-control and compliance system for a venue that wants someone else to own the messy boundary between hardware, user authentication, records and support. Internetten's chance is to make the renewal feel safer than buying parts from one marketplace, a server from another and configuration labour from a freelancer. The threat is that customers may still compare the invoice with publicly visible cloud and VPS prices.

Once a service is described as cloud, customers benchmark it against global and large local cloud offers even when the underlying job is different.

The company therefore lives between two pricing languages. To customers, especially small venues and regional ISPs, the invoice has to be legible in local budgets. On procurement, imported networking gear, vendor licences, data-centre equipment, spares and some software references are dollar- or euro-sensitive. In late July 2026, official Turkish exchange-rate data put the lira at roughly the high-forties to the dollar and mid-fifties to the euro. June 2026 inflation was still above thirty percent annually, and the housing, water, electricity, gas and other fuels category was far higher than headline inflation.

That is the margin problem in one sentence: Internetten must sell trust locally while buying resilience globally.

The right judgment is neither dismissive nor euphoric. Internetten has a real local niche if it refuses to compete as a commodity host. It can sell integration, compliance, field knowledge, spares, managed access, logging and support. It can monetize the fact that many Turkish venues and small ISPs do not want to assemble those parts themselves. But the public evidence does not show a company with the scale to absorb currency shocks casually. It shows a narrow infrastructure operator whose profits depend on renewal discipline, transparent support fees and supplier timing.

The control boundary is narrower than the brand language suggests

The company's legal and operating evidence should be separated carefully. Public directory data records the limited company as established in January 2014, registered in Gebze and classified around wholesale trade of computer hardware, peripherals and software. Company-owned pages, meanwhile, claim a longer operating history around MikroTik products since 1999 and Ubiquiti since 2009. The fair reading is that Internetten is presenting a long-running business lineage or team experience, while the currently named limited company has a later formal registration.

That distinction matters because a company selling infrastructure trust benefits from age, but the economic analysis should not treat an unaudited brand-history claim as audited corporate continuity.

The public contact page is useful in another way: it gives a concrete operating base in Gebze/Kocaeli, a trade registry number and MERSIS number. This is a local Turkish company with a visible commercial address, not an anonymous cloud storefront. Its physical operating context is also important. Gebze sits inside a dense industrial and logistics corridor near Istanbul and Kocaeli, where factories, logistics sites, municipal facilities, campuses, warehouses and small operators can need network projects. That local density helps explain why the company talks about project design, installation and support rather than only online checkout.

On the network side, the boundary is also visible. AS208095 belongs to Internetten Teknoloji. Multiple network-intelligence sources show three originated IPv4 /24s, 768 IPv4 addresses and no observed originated IPv6 prefixes. Hurricane Electric reports all three originated prefixes as RPKI valid. IPinfo names one range as CORE-WIPOINT-NETWORK and another as Internetten's RIPE-registered address space. CIDR Report sees the AS as an origin network with no transit address space.

PeeringDB self-reports a wider interconnection story: 10-20 Gbps traffic, balanced ratios, an open peering policy and presence at COMNET Datacenter Istanbul, PremierDC Istanbul and Radore Istanbul.

The discrepancy between observed BGP sources and PeeringDB's larger self-reported prefix numbers should not be overplayed, but it should not be ignored. Operator-maintained interconnection databases can contain stale, aspirational or differently counted data. Observed BGP data, in contrast, shows what the internet can see. The visible picture is of a small, controlled network useful for hosted software, logging, management systems and perhaps customer services, not a large general hosting platform. That is not a weakness if the business is WiPoint, SysLog, ISP tooling and project support.

It becomes a weakness only if the company tries to sell itself as a broad cloud alternative to customers who need deep redundancy, many regions, IPv6 maturity, large transit diversity or self-service elastic compute.

The operating boundary is therefore local and practical. Internetten appears to control enough infrastructure to run niche services and support products tied to its channel. It does not appear to control enough public infrastructure to set the market price of compute. The company can win when the control point is a configured customer site, a venue's login flow, a logging archive, an ISP CRM process or a hard-to-source network component. It will struggle if the control point is a standard VM, a generic web-hosting renewal or a simple price-per-gigabyte comparison.

Revenue is a bundle, not a single product

Internetten's strongest economic feature is that its revenue can attach to several points in the same customer workflow. A small ISP or venue may buy physical devices, installation advice, project design, a WiPoint licence, cloud logging, monitoring, warranty service, spares and later upgrades. That is a better structure than pure hardware resale because the customer relationship does not end when the box ships. It is also better than pure software in a market where local physical deployment still matters. The hardware sale creates the customer. The software and support renewals create the margin opportunity.

The WiPoint product makes this visible. The product page describes a Mikrotik-powered cloud hotspot for public internet access, with authentication methods such as manual users, national-ID verification, SMS, integrations, social login and email approval. The package page prices annual licences by concurrent-user bands. The store page also lists annual WiPoint packages in lira, from small packages up to 500 online users. The presence of both dollar-denominated package tables and lira storefront prices is not a clerical curiosity. It is the business problem rendered as a price card.

The company knows the service has to be understood in global currency terms, but local customers may renew in lira.

The unit economics of this kind of product are attractive only if support does not rise linearly with users. A 25-user hotspot and a 500-user hotspot can both use similar product architecture, but the larger site may require more configuration, more integration, more troubleshooting, more reputational exposure and more pressure when authentication fails during peak usage. The annual subscription can scale well if the product is stable and onboarding is standardized. It can become a support trap if every sale includes hidden manual work that was not priced into the renewal.

SysLog is a related but different opportunity. Its public page sells cloud logging as a way to avoid local disk, power, hardware and space. That is a clean value proposition under Turkish inflation: let the customer avoid a local appliance and store logs in a managed service. But the service provider then inherits the cost curve. Storage, retention, backup, security, data-centre power and incident response become Internetten's problem. If the product is priced as a compliance-critical managed service, this can be profitable.

If it is priced like a cheap add-on to sell routers, the company will be carrying an inflation-linked obligation on a weak revenue base.

WiRadius extends the relationship further into ISP operations. Its public page describes a CRM-style system for internet service providers, including subscriber management, field tasks, device management, accounting, payment and reporting. For small ISPs, these workflows are sticky because replacing them can disrupt billing and support. If Internetten's broader network of 100+ ISP relationships is real, WiRadius-type software can convert a hardware channel into recurring operational software. But there is no public audited revenue, churn or user-count disclosure. The opportunity is visible; the scale is not.

That distinction drives the article's judgment. Internetten should not be valued or analysed as if every listed product category automatically creates recurring gross margin. A storefront with many SKUs can be high revenue and low margin. A project team can be busy and still not compound. The compounding element is the renewal layer: hotspot licences, logging, managed support, ISP workflow tools and possibly monitoring. The company's challenge is to make those renewals explicit, priced, contractual and indexed enough to survive cost shocks.

Pricing exposes the currency mismatch

The strongest public pricing evidence is also the most uncomfortable. WiPoint's own package page displays annual prices in dollars plus VAT: $100 for 25 users, $160 for 50, $200 for 100, $330 for 200, $470 for 300, $550 for 400 and $740 for 500, with higher packages quoted. The store page presents WiPoint packages in Turkish lira. The broader wi.com.tr and wi.tr storefronts show networking hardware in lira. Competitors in Turkish hosting often show prices in both currencies or promotional dollar terms. This is the price environment Internetten must navigate.

If the company indexes too aggressively to the dollar, some local customers will feel the service is unaffordable or arbitrary. If it holds lira renewals too long, a few months of exchange-rate movement and inflation can erase the expected gross margin. The problem compounds because the cost base is not one input. Imported routers and access points move with global vendor pricing and currency. Replacement stock ties up working capital. Bandwidth and data-centre charges reflect wholesale telecom and facility economics. Power is exposed to regulated tariffs and energy inflation.

Support labour is domestic but rises with inflation and competition for capable network technicians. Payment processing and tax rules add friction.

The visible competitors set ceilings. Radore advertises entry cloud servers from a low dollar monthly price, dedicated servers from a higher dollar monthly price and colocation from a lira monthly price. Turhost, Natro and TurkHosting advertise low-cost VPS, VDS, hosting and dedicated products, frequently with promotional discounts and either dollar or dual-currency display. AWS and Azure create the global reference model: pay-as-you-go compute or hourly VM pricing, with storage, transfer, operating-system and address components broken out separately. A customer that only needs a server has many cheaper-looking alternatives.

Internetten's answer cannot be to pretend those alternatives do not exist. It has to show that the comparison is wrong for its core jobs. A WiPoint renewal is not just a VM. It is authentication, venue-specific login options, MikroTik integration, logging expectations, customer support and legal comfort. A SysLog renewal is not just disk space. It is retention, search, reports, security and a customer belief that records will be there when needed. A MikroTik project is not just a router. It is product selection, configuration, support, spares and practical familiarity with Turkish small-ISP conditions.

That argument works only if the invoice explains the bundle. An unofficial complaint-source snapshot is relevant here because one complaint alleged extra service or technical fees after buying router and hotspot products. The complaint count is small and unverified, so it should not be treated as proof of a broad problem. But as a market signal it highlights the core commercial risk: if customers think they bought a product and then discover they also need paid configuration, the company may be charging correctly but communicating poorly. In a high-inflation market, every hidden support hour becomes a dispute risk.

The best pricing architecture would separate hardware, configuration, managed service, retention, support tier and renewal indexation. That may reduce the charm of a simple storefront price, but it protects margin and trust. The worst architecture is a lira sticker that silently assumes expensive support, imported spares and cloud retention will be absorbed later. That is how a local infrastructure provider becomes busy but unprofitable.

Hardware margin is useful but not durable enough

The catalogue is broad enough to make Internetten commercially relevant. MikroTik routers and switches, Ubiquiti access points and bridges, RF Elements antennas, VSOL GPON gear, fibre accessories, PoE devices, monitoring software, TP-Link, Huawei, Mimosa, Ruijie and other brands give the company a practical role for regional operators that need parts and advice. The storefront's lira prices also show a customer can buy individual components without waiting for a bespoke project. That helps liquidity and market reach.

But hardware resale alone is a hard place to make durable profit. The product is often searchable. Customers can compare similar devices from multiple sellers. A reseller must carry inventory, handle returns, manage warranty claims, answer technical questions and keep prices current. In a volatile currency environment, stale stock can help if bought before depreciation, but it can also trap capital in slow-moving items. Fast-moving items can disappear exactly when customers need replacements. Warranty timing can consume support hours that were not included in the gross margin.

Importers and distributors may face customs, shipping and vendor allocation constraints that a customer never sees.

The company's official pages say technical support is part of its value proposition. That is credible and important. MikroTik and Ubiquiti products can be powerful but require configuration skill. Small ISPs and venues may prefer a supplier that can recommend an access point, routerboard, antenna, GPON splitter, PoE arrangement and hotspot plan together. The more complex the project, the more Internetten can escape pure price comparison. The more standardized the product, the more it is dragged back into commodity retail.

This is why the software layer is not optional. It is the economic protection for the hardware channel. WiPoint can turn a venue router sale into an annual service. SysLog can turn a compliance requirement into retention revenue. WiRadius can keep ISP customers inside the ecosystem after the initial deployment. Monitoring and support can make the customer less likely to switch suppliers over a small hardware discount. The company's catalogue is the entry point; the renewal stack is the defence.

The risk is that each defence carries its own cost. A hotspot service creates authentication support. A logging service creates retention and security obligations. A CRM creates uptime and data-integrity expectations. A monitoring product creates alert fatigue and response expectations. If Internetten prices these as cheap attachments, it increases revenue but weakens margin. If it prices them as managed infrastructure, it may lose some price-sensitive customers but keep the ones that value continuity. For this company, smaller but cleaner recurring revenue may be better than wide but underpriced support exposure.

The network evidence supports a niche service node

AS208095 is a useful reality check. Three observed IPv4 /24s and 768 addresses are enough to run services, customer management systems, logging endpoints and perhaps some hosted workloads. They are not enough to imply a large-scale cloud platform. The lack of observed IPv6 originated prefixes in the main network-intelligence sources is also notable. In 2026, IPv6 absence is not fatal for local venue services, but it signals that the company is not presenting itself as a cutting-edge global cloud network.

PeeringDB's facility list is more encouraging. Presence or declared interconnection at COMNET Datacenter Istanbul, PremierDC Istanbul and Radore Istanbul places the company inside real Istanbul data-centre geography. Its self-reported 10-20 Gbps traffic level, if current, suggests more than a dormant ASN. But the absence of public exchange entries in the viewed PeeringDB snapshot and the small observed route set mean resilience questions remain. For managed logging and hotspot access, a small but well-run network can be enough. For customers expecting cloud-region resilience, it is not.

The strongest network signal is naming. The 45.159.28.0/24 range is identified as CORE-WIPOINT-NETWORK. That ties the routed resources to the software product rather than only to generic hosting. The 94.124.73.0/24 record ties the resource holder to Internetten's RIPE organisation and abuse contact. These are the traces one would expect from a company running its own service layer for customer products. They are not the traces one would expect from a large public cloud.

That has strategic consequences. Internetten should use its network to control the critical service components it understands: authentication, logs, management panels, update services, monitoring and support access. It should be cautious about offering low-margin general hosting that consumes IPs, support and abuse-handling capacity without deepening the core customer relationship. Hosted domains counted against the ASN appear small in public data. That is not bad if the company is intentionally not chasing generic hosting.

It would be bad only if management believed the routed network could become a major cloud business without significant capital, upstream diversity and operational investment.

Network scale also affects customer concentration. A company with a small service network can be highly dependent on a handful of product lines or support-heavy accounts even if it has thousands of dealers. The official 100+ ISP and 5,000+ dealer claims sound broad, but they do not reveal revenue concentration. Ten active ISP software accounts could matter more than thousands of occasional hardware buyers. A few demanding municipal, hotel or dormitory deployments could absorb disproportionate support. Without revenue disclosure, the correct stance is to treat channel breadth as positive but not conclusive.

Suppliers define the ceiling on control

Internetten's supplier mix is both the moat and the constraint. MikroTik, Ubiquiti, RF Elements, VSOL, Huawei, Mimosa, Paessler, Ruijie, Juniper and other brands give the company a broad problem-solving toolkit. Customers can ask for access, backhaul, switching, GPON, monitoring, fibre and hotspot components in one place. That is valuable in a fragmented local market. It also reduces dependence on a single product family at the catalogue level.

But dependence does not disappear; it moves to procurement terms, warranty rules, vendor roadmap changes and exchange rates. If a vendor changes regional distribution, runs short on a popular model, adjusts licence terms or reprices in hard currency, Internetten has to pass the cost through or absorb it. If customers perceive the company as the guarantor of every device, the support burden can remain even when the margin was mostly captured by the original vendor. The more the company claims technical support as a differentiator, the more it must fund that support properly.

There is also a subtle risk in vendor-branded expertise. A distributor that is excellent at MikroTik and Ubiquiti projects can become strategically tied to the preferences of a customer segment that loves those platforms. That is fine for small ISPs and budget-conscious venue deployments. It is less helpful when customers move to fully managed Meraki-style, UniFi cloud-managed, hyperscale, telecom-integrated or managed-security alternatives. The company's answer should be vendor fluency plus service neutrality: sell the outcome, not only the box.

The house-brand and software pieces help. WINET products, WiPoint and the associated software ecosystem are where Internetten can own more of the margin. They also create responsibility. A reseller can blame vendor lead times; a software operator owns the service promise. That is why Internetten's margin defence requires operational maturity. If it wants to earn software multiples, it must behave like a software and managed-service company: clear service levels, renewal discipline, visible support scope, retention policies, change management and customer communication.

The public evidence does not show whether that maturity exists. It shows enough to make the thesis plausible. Official product sites, routed resources, package pricing and ISP references suggest real operating activity. The absence of public financials, audited customer counts, support metrics and uptime data limits confidence. The right analytical stance is to give credit for the niche while demanding proof before assigning broad cloud economics.

Competition comes from both sides

Internetten faces competition from below, beside and above. From below, small resellers and freelancers can sell routers, install Wi-Fi, configure MikroTik and quote cheaply. Some will not carry the same support or compliance burden, but customers often notice the low upfront price first. From beside, Turkish hosting and data-centre companies advertise VPS, VDS, dedicated servers, colocation and managed hosting with clear entry pricing. Radore, Turhost, Natro and TurkHosting all create reference prices for compute and hosting. From above, AWS and Azure define the global language of elastic compute, hourly billing and modular infrastructure.

The company should welcome some of this competition because it clarifies where not to fight. Internetten should not try to be the cheapest virtual server. The local hosting market already has providers built for that. It should not try to mimic AWS. It lacks the scale, regions, product breadth and capital base. Its better alternative is to sell the part AWS does not solve for a small Turkish venue: choosing and configuring the access hardware, authenticating local users, keeping logs, integrating with property or school systems, and handling support in the customer's language and time zone.

Local hosting competitors still matter because they can attack the infrastructure layer underneath Internetten's software. If a customer believes SysLog or WiPoint is just a server with storage and a login page, they will compare it with a cheap VPS. Internetten has to make the managed-service difference concrete: retention integrity, ease of use, venue workflows, reporting, legal comfort, support response and integration. If those are real and visible, the company can price above commodity hosting. If they are vague, the customer will arbitrage the service against cheaper compute.

Competitors also reveal cost inflation. TurkHosting's 2026 price-update notice is useful because it explicitly ties service price increases to data-centre and operator cost increases, not only to margin expansion. This is one competitor speaking for itself, not the whole market. But it supports the broader point: infrastructure costs are rising for everyone. Internetten cannot assume that local customers will accept price increases merely because costs rose. It has to attach increases to tangible continuity: compliance retention, support, uptime, hardware availability and reduced operational risk.

There is an opening in that environment. Hyperscale clouds are strong for developers and scalable applications, but they are often overkill or operationally alien for a small venue's guest Wi-Fi compliance problem. Big local hosts can sell servers and colocation, but may not want the long tail of MikroTik configuration and venue-specific hotspot workflows. Small freelancers can configure cheaply, but may not provide a durable service desk or logging continuity. Internetten sits in the middle. The middle is profitable only if it is disciplined.

Regulation is a moat only when operationalized

Turkey's 5651 framework and the 2017 regulation for internet bulk usage providers create a clear demand signal. Public internet providers and venues must care about access records, filtering, log integrity and administrative obligations. WiPoint and SysLog speak directly to that anxiety. A hotel, dormitory, cafe or municipality may not want to interpret legal details or build logging systems itself. A packaged cloud hotspot and logging service can reduce perceived risk.

Regulation can therefore be a moat. The moat is not the law itself; competitors can read the same law. The moat is operational translation. Internetten can bundle compliant login flows, MikroTik configuration, cloud retention, reports and support into a product that a venue understands. If it does this well, regulation creates renewal demand and reduces churn because customers fear breaking a working compliance setup.

But regulation also raises the cost of mistakes. If logs are missing, corrupted, hard to search or retained in a way customers distrust, the service promise weakens quickly. If the company handles identity information, phone numbers or social login data, privacy and security expectations rise. If support is slow during an audit, customer anger may be disproportionate to the annual fee. Compliance products produce sticky revenue only when customers believe the provider is more reliable than their own local workaround.

This is why the company's cloud-service economics must include support and assurance, not just storage. A two-year retention promise consumes infrastructure and process. Authentication choices require maintenance as APIs, messaging providers and identity-check methods change. Reports must be understandable. Backups and access controls must be tested. The public sources show product claims, not operational proof. The analysis should therefore recognize the moat while treating it as unproven until service metrics are available.

Geopolitics and vendor supply add another layer. Turkey's local infrastructure market can benefit from data-sovereignty and local-support preferences, but many of the devices are global products. Hardware lead times, import rules, customs, sanctions regimes, vendor channel shifts and currency controls can alter availability. A local provider that knows how to source alternatives can turn this into value. A provider that depends on one supply path can be squeezed.

Support capacity is the hidden margin line

The most important cost line may not be bandwidth or servers. It may be support utilization. A reseller can show gross margin on a router sale, a software operator can show recurring revenue on a hotspot licence, and a hosting provider can show monthly revenue per server. But if technicians spend hours explaining configuration, chasing warranty claims, restoring access, dealing with angry venue managers or clarifying charges, the real margin falls below the advertised margin.

Public unofficial signals should be handled carefully. Sikayetvar showed only four wi.com.tr complaints in the viewed snapshot, which is not enough to infer systemic failure. The allegations are unverified. Still, the themes are exactly where the economic risk sits: return handling, delayed service and extra technical fees after router/hotspot purchases. For a company whose value proposition includes technical support, these are not peripheral issues. They are the place where pricing, expectation-setting and operations meet.

The company can turn this risk into an advantage if it productizes support. A basic package might include device sale and documentation only. A configuration package might include defined setup work. A managed package might include monitoring, hotspot, logging, updates and response commitments. A premium ISP package might include WiRadius workflows and escalation. Clear tiers let customers choose. They also protect the company from giving away engineering labour to save a sale.

The alternative is dangerous. If the sales process implies that support is included but the delivery process discovers that configuration is extra, customers feel misled. If support is included without limits, technicians become the shock absorber for every currency, vendor and customer problem. If support is priced case-by-case, renewal trust suffers. In infrastructure services, ambiguity is a hidden discount.

This is especially true in the target verticals. Hotels, dormitories, schools, cafes and municipalities do not call when everything is calm. They call when guests cannot log in, when records are needed, when a router has failed, when a technician is on-site, or when management is angry. The support event has urgency. The provider either planned for that urgency in the price or gives away margin at the moment of maximum pressure.

The judgment

Internetten Teknoloji can maintain hosting and software margin ahead of currency risk, but only as a disciplined local managed-infrastructure company. It should not be judged as a cheap host. It should not be judged as a hyperscale challenger. The public record supports a company with meaningful local channel knowledge, a broad industrial networking catalogue, visible software products, a small service network and regulatory-demand alignment. That is enough for a defensible niche.

The niche is attractive because the customer problem is not purely technical. It is operational and legal. A venue or small ISP wants internet access to work, logs to be retained, users to authenticate, devices to be available, and someone to answer when the system fails. Internetten can monetize that trust if it keeps the bundle intact. Hardware brings the customer in. Software creates recurrence. Support preserves trust. Local regulation raises the cost of switching away from a working setup.

The niche is fragile because the company does not control enough of the global cost stack. Imported devices, vendor licences, exchange rates, data-centre power, bandwidth, domestic wages and facility charges can move faster than lira renewals. Competitors advertise low cloud and VPS prices that can make customers question managed-service invoices. A small routed network can support niche services, but it cannot make Internetten immune from wholesale infrastructure economics. The company's bargaining power is local intimacy, not scale.

The best strategic posture is therefore selective. Internetten should preserve margin by emphasizing WiPoint, SysLog, WiRadius-like workflows, managed support and project integration. It should use hardware as a channel and proof of expertise, not as the only profit engine. It should avoid underpriced commodity hosting unless that hosting directly supports a sticky compliance or operations product. It should make support scope explicit, index renewals transparently and maintain supplier diversity.

It should also invest in observable network resilience, including multi-upstream clarity and IPv6 readiness, because trust products become less credible when the underlying network looks too small or dated.

The clear judgment is this: Internetten's economics work if the company charges for solved local complexity; they break if it sells complexity at hardware-retail margins. The difference may not show up in revenue. It will show up in renewal quality, technician utilization, complaint patterns and whether the company can raise prices without losing the customers that matter.

What would reverse the judgment

Several facts could make the view more positive. First, audited or management-disclosed recurring revenue from WiPoint, SysLog and WiRadius would matter more than storefront catalogue breadth. If software renewals are growing, churn is low and support hours per customer are falling, Internetten would deserve to be viewed as a managed software-and-infrastructure operator rather than a reseller.

Second, evidence of strong supplier terms would reduce currency risk. If the company buys key hardware with protected pricing, vendor credit, local warranty support or fast replenishment, it can survive lira volatility better than a simple reseller. If it has to prepay imported stock or absorb warranty labour without compensation, the risk is higher.

Third, network resilience would change the infrastructure reading. More visible upstream diversity, public exchange participation, meaningful IPv6 deployment, larger live service footprint and transparent uptime practices would support a broader cloud-substitution claim. The current public BGP footprint is adequate for a niche service node, not for a large hosting thesis.

Fourth, support metrics would be decisive. If Internetten can show response times, defined support tiers, low unresolved warranty backlog and high renewal satisfaction, the complaint risk fades. If public complaint themes grow around hidden fees, slow service or failed returns, the model is likely underpricing support or communicating it poorly.

Fifth, customer concentration matters. A broad dealer count is not the same as diversified recurring revenue. The bullish case requires many renewing venues and ISPs, not only many one-time buyers. A few large support-heavy accounts could make reported revenue look healthier than underlying margin.

Finally, the macro backdrop could move either way. A stabilizing lira and lower inflation would make lira renewals easier to manage. Further depreciation, energy-cost pressure or vendor repricing would force faster pass-through. The company cannot control that macro path. It can control whether its contracts, support tiers and product mix are built to survive it.

Until those facts are available, the prudent conclusion is narrow but constructive. Internetten Teknoloji is a real local infrastructure intermediary with a plausible software margin story. It is not yet, on public evidence, a broad cloud competitor. Its success depends on staying honest about that boundary.

Sources