Solusi Integra Datakom and the small price of making Jakarta connectivity boring

The first cost is not bandwidth

The hard number is 512. APNIC's RDAP record for 103.171.184.0/23 identifies a 512-address IPv4 allocation to PT Solusi Integra Datakom, marked active, under the name IDNIC-INTRAKOM-ID, with the company described as a corporate/direct IDNIC member in Bekasi (https://idnic.rdap.apnic.net/ip/103.171.184.0/23). IPinfo reads the same autonomous system, AS142374, as an Indonesian ISP with 512 IPv4 addresses, a large IPv6 allocation surface, 26 hosted domains and three recently pingable addresses from Jakarta (https://ipinfo.io/AS142374). PeeringDB, meanwhile, places AS142374 in the 1-5Gbps traffic band, with two listed facilities and five exchange connections, including a 10G IIX-Jakarta entry in its public API output (https://www.peeringdb.com/api/net/28165?depth=2).

That is not a large national carrier footprint. It is enough, however, to reveal the business problem. A customer does not care that an ISP has 512 IPv4 addresses in a registry table. The customer cares whether one branch office, one school, one warehouse, one clinic or one public-sector site can be connected by the promised date, monitored after installation and repaired without being passed from a wholesale access provider to a router vendor to an internal IT team. The cost of that promise begins with an access handoff and a support obligation. Bandwidth is only one input.

Solusi Integra Datakom's public brand, Intrakom, sells exactly that middle layer. Its website describes "Reliable Connectivity & Digital Infrastructure for Your Business" and puts network infrastructure, hardware and software, artificial intelligence, managed services, certified engineers, flexible service options and support in one storefront (https://www.intrakom.co.id/). The network-infrastructure language is broad: fibre-optic network development, network-device installation, security systems, server integration and data-centre integration. The support language is equally practical: 24/7 technical support, fast response and SLA assurance, MRTG and network monitoring, certified engineers on call, preventive and corrective visits, and multiple support channels through WhatsApp, email and hotline (https://www.intrakom.co.id/).

The governing economic question is therefore not whether Intrakom owns enough national backbone to fight Indonesia's largest carriers. It almost certainly does not. The better question is whether a small licensed ISP and integrator can earn an integration margin by making other people's access, routers, data-centre rooms, security appliances and local interconnection usable for customers who want one accountable party. In Indonesia, where the number of internet users is vast but fixed broadband remains underpenetrated by global standards, that boring middle can be valuable.

APJII reported that Indonesia had 221,563,479 internet users in 2024, equal to 79.5% penetration against a 2023 population base of 278,696,200 (https://apjii.or.id/berita/d/apjii-jumlah-pengguna-internet-indonesia-tembus-221-juta-orang). The World Bank's ITU-based data put Indonesian fixed-broadband subscriptions at only 4.92 per 100 people in 2024 (https://api.worldbank.org/v2/country/IDN/indicator/IT.NET.BBND.P2?format=json&per_page=10). Those two numbers explain why access itself is a competitive commodity while dependable enterprise delivery is not. There are many people online; there are still many premises where the hard work is getting a dependable fixed line, local failover, a manageable router, a usable SLA and a support response that fits the customer's operating hours.

For Intrakom, the price of integration is the cost of being the party that takes the call. A raw link can be bought from a carrier. A switch can be bought from a distributor. A firewall can be installed by a contractor. The margin appears when a customer pays one operator to combine those pieces, document them, watch them, and turn an outage into an accountable service event rather than a blame exercise.

Identity sits between South Jakarta and Bekasi

The company's public identity is clearer than a casual search suggests, but the addresses tell a useful story. Companies House Indonesia lists PT. Solusi Integra Datakom as an Indonesian limited liability company, business registration number 1177934, registered on June 30, 2021, with a South Jakarta address at Ruko Plaza 3 Pondok Indah Blok A Nomor 5B, Jalan TB Simatupang Nomor 5, Pondok Pinang, Kebayoran Lama (https://companieshouse.id/solusi-integra-datakom). An LEI lookup gives the legal name PT SOLUSI INTEGRA DATAKOM, entity status active, registration authority entity ID 1240000613102, initial LEI registration in April 2026, and the same South Jakarta legal and headquarters address (https://www.lei-lookup.com/record/926900193C2A334F2D68/).

The operating and internet-resource trail points eastward. APJII's IDNIC member page lists PT Solusi Integra Datakom with registration number 1034, brand name INTRAKOM, membership type Keanggotaan Penyelenggara, licence type ISP, domain INTRAKOM.CO.ID, and an office address at Jalan Ujung Harapan Kavling Alikhlas 13 no 97, Bahagia, Babelan, Kabupaten Bekasi, West Java (https://www.apjii.or.id/anggota/idnic?legality=&name=&page=113). APNIC's ASN RDAP record for AS142374 carries the same Bekasi address, the name IDNIC-INTRAKOM-AS-ID, active status, registration on August 16, 2021, and an abuse mailbox at abuse@intrakom.co.id (https://rdap.apnic.net/autnum/142374). PeeringDB's organization record also puts PT Solusi Integra Datakom at Jalan Ujung Harapan Alikhlas 13 No 97, Bekasi (https://www.peeringdb.com/org/30669).

That split should not be overread. Small Indonesian technology firms often combine a formal commercial address, a practical technical address and customer-facing Jakarta coverage. What matters is that the records are mutually intelligible. South Jakarta is the legal and commercial face. Bekasi appears in IDNIC, APNIC and PeeringDB as the internet-resource address. Intrakom's website footer returns to the South Jakarta Ruko Plaza 3 Pondok Indah address (https://www.intrakom.co.id/). Together, the records support the simple conclusion that Intrakom is an Indonesian private company with a public ISP identity, a Jakarta-area commercial presence and a Bekasi resource trail.

The public company page on LinkedIn adds the market positioning: PT Solusi Integra Datakom, with the brand Intrakom, describes itself as a managed-service provider operating in information technology and internet services, with an 11-50 employee size band and headquarters in South Jakarta (https://id.linkedin.com/company/pt-solusi-integra-datakom). LinkedIn is not a statutory record, but it is useful as a signal of how the company sells itself to employees, customers and partners. The important phrase is not "ISP"; it is managed services. Intrakom wants to be read as the party that manages the customer's technology surface, not merely the party that announces a route.

This identity matters because the article should not pretend that every small autonomous system is the same. Some small ASNs are hobby networks. Some are hosting shells. Some are access providers with a few neighbourhood routes. Intrakom's footprint looks like a commercial access and integration company: a registered Indonesian company, an APJII/IDNIC membership, an active ASN, a small but real address allocation, public exchange entries, an ISP licence description in APJII's member page, and a website that sells project execution, monitoring and support.

A small route table can carry a wide promise

AS142374 is modest in visible routing terms. BGP.tools lists PT Solusi Integra Datakom as active and allocated under APNIC, a carrier network in Indonesia, originating two IPv4 prefixes and three IPv6 prefixes, with upstreams including PT Parsaoran Global Datatrans and PT Fakta Jabbar Industri in the page reviewed for this essay (https://bgp.tools/as/142374). The two IPv4 routes are 103.171.184.0/24 and 103.171.185.0/24; the IPv6 routes visible through public observers include 2400:a060::/48, 2400:a060:1::/48 and 2400:a060:14::/48 (https://bgp.tools/as/142374). APNIC's IPv6 RDAP record shows 2400:a060::/32 as an allocated portable block for PT Solusi Integra Datakom, described as an internet service provider in Bekasi, registered in August 2022 (https://idnic.rdap.apnic.net/ip/2400:a060::/32).

The address count and the product promise have different scales. Five announced prefixes do not make Intrakom a broad national network. But small-route evidence can still carry commercial weight if the customer problem is local integration. A mid-sized business does not always need a carrier with millions of mobile subscribers. It needs a provider that can deliver a line, terminate it, assign addresses where needed, monitor the link, configure the router, secure the site, escalate to an upstream and send a technician when remote diagnosis fails.

PeeringDB gives the public interconnection view. It lists Solusi Integra Datakom as a Cable/DSL/ISP network with AS142374, IRR set AS-142374, IPv4 and IPv6 prefix fields both entered as 1000, traffic in the 1-5Gbps range, balanced traffic ratio, Asia Pacific scope, open peering policy, no ratio requirement and no contract requirement (https://www.peeringdb.com/net/28165). The public API shows two facilities: Datacenter APJII-Cyber and IDC 3D, both in Jakarta Selatan. It also shows exchange entries for OpenIXP / NiCE, JKT-IX Main, CXC Jakarta, IIX-Jakarta and EdgeNXT, with IIX-Jakarta shown at 10,000 Mbps and the other listed PeeringDB exchange speeds at 1,000 Mbps (https://www.peeringdb.com/api/net/28165?depth=2).

Those PeeringDB entries are not audited service performance. They are self-maintained and should be treated as public network declarations. They are still economically meaningful. A provider that appears at multiple Jakarta exchanges has more ways to keep local traffic local, more potential to reduce paid transit exposure, and more operational complexity to manage. The EdgeNXT public customer page separately lists Solusi Integra Datakom as a full member, joined in 2024, at EdgeNXT CGK3 Jakarta with a 10 Gbits entry, location APJII-Cyber, and IP addresses 103.61.232.47 and 2001:df1:d440:1::47 (https://care.edgenxt.com/index.php/customer/detail/107). Packet Clearing House's IIX-Jakarta page identifies 123.108.8.21 as AS142374, PT. SOLUSI INTEGRA DATAKOM, at the Indonesian Internet Exchange in Jakarta (https://www.pch.net/ixp/details/110).

Public sources do not fully agree on every speed and adjacency. IPinfo, for example, counted five peers and one upstream on its page, while BGP.tools showed a broader peer/upstream picture at the time of review (https://ipinfo.io/AS142374 and https://bgp.tools/as/142374). That difference is not a scandal; route-observer methodologies differ, and BGP visibility changes. For a buyer, though, the mismatch is a useful reminder. The value of Intrakom's interconnection story depends not on a static page count but on current port contracts, route-server sessions, transit commits, upstream SLAs and operational monitoring. Those are the documents a serious customer would ask to see before treating the route map as resilience.

The product is a managed installation, not a slogan

Intrakom's site says more about the business model than the routing table does. The product language is intentionally broad. Network infrastructure covers stable, secure and scalable connectivity, including fibre build, device installation, security systems, server integration and data-centre integration. Hardware and software covers licences, network-management platforms, digital-security systems and operational applications. Artificial intelligence is presented as a combination of generative AI and computer vision for automation, security and operational efficiency (https://www.intrakom.co.id/).

The breadth could look unfocused. In a different context it might be. For an Indonesian SME, institution or branch-network customer, however, that breadth is the point. The customer often does not want to separately procure access, cabling, a router, a firewall, endpoint licences, monitoring and a support contractor. It wants a working site. Intrakom's "Managed Services" section says systems and networks are managed proactively, stably and optimally. Its support section promises 24/7 technical support, SLA assurance, MRTG/NMS monitoring, certified engineers on call, preventive and corrective visits, and multiple support channels (https://www.intrakom.co.id/). The vocabulary is service-operator vocabulary: watch the link, dispatch the person, close the ticket.

This is where the margin can survive even as access prices compress. A line itself is vulnerable to commodity pricing. Indonesia's largest fixed-broadband operator shows the same pressure at scale: Telkom Indonesia's 9M25 information memo reported that IndiHome ARPU declined 9.4% year on year to Rp216,700, reflecting customer movement toward internet-only packages rather than bundled IPTV and telephone products (https://www.telkom.co.id/minio/show/data/lampiran/1761838522183_original_TLKM-9M25-Info-Memo.pdf). Intrakom is not IndiHome, and consumer ARPU is not an enterprise managed-service price. But the direction matters. Pure access becomes harder to defend when customers learn to compare headline speed and monthly charge.

Managed integration changes the comparison. A customer site might need a local access loop from a wholesale fibre partner, a router, a firewall, a Wi-Fi design, monitoring, an IP plan, cabling, user handover, documentation and on-site rescue. The monthly bill can then include a bundle of things that are not easily compared on a consumer price table. Intrakom's site displays partner logos including HSP, IDC, APJII, Fiberstar, iForte, Fibermedia, Ruijie, Commscope and Sophos, alongside client or customer logos including Jupiter, ASEAN, Agrinesia, Megadata, Gunung Ringgit, Imigrasi, Unilever and Ragam (https://www.intrakom.co.id/). The site does not provide contract scope, dates or revenue by account, so those logos should be treated as public marketing claims rather than independent proof of active work. Still, they tell the commercial story Intrakom wants to tell: it sits between access owners, equipment vendors, institutions and customers.

The project-manager hiring signal strengthens that reading. In a public LinkedIn post one month before this article date, an Intrakom HR account advertised for a Project Manager to drive execution for Connectivity and ICT projects. The responsibilities began with handling execution from purchase order received by sales until project completion, coordinating internal teams and customers, ensuring timeline, quality and target delivery, monitoring progress and maintaining communication with stakeholders (https://www.linkedin.com/posts/mutya-kristy-sulba-6790b4219_hiring-projectmanager-ict-activity-7463545378714324992-60be). A single job post does not prove growth. It does show what kind of work creates bottlenecks: not just routing packets, but turning a signed customer order into a finished site.

That is the economic core. Intrakom's scarce resource is not merely IPv4. It is coordination. Someone has to know which fibre partner can reach a building, which device model is in stock, which upstream ticket matters, which route is abnormal, which customer contact can approve a visit, and which engineer is free after dark. Large carriers can do this with scale. Small integrators can do it with attention, local knowledge and a narrower customer book. The risk is that the same attention is hard to scale without adding labour.

The integration margin has costs of its own

The integration margin is attractive because it changes the product from a commodity line into a managed outcome. It is also expensive because it turns the provider into the customer's operating buffer. Intrakom's public site promises monitoring, certified engineers, preventive visits and corrective visits (https://www.intrakom.co.id/). Every one of those promises carries a cost. Monitoring requires tooling and people who know when an alarm matters. Certified engineers require hiring, training and retention. Preventive visits consume travel time before there is an outage. Corrective visits consume time during the worst possible moments, when the customer's business is already disrupted and patience is scarce.

Small-provider economics are often misunderstood. A small ISP does not necessarily lose because it lacks national scale. It loses when it carries the cost structure of a managed provider while customers price it as a commodity provider. Intrakom's website therefore has to convert support labour into perceived value. If a customer believes the service is just a line, it will compare Intrakom with the cheapest access supplier. If the customer believes the service is a managed connectivity outcome, it will compare Intrakom with the cost of managing multiple vendors itself.

Indonesia's market structure gives both opportunities and pressure. APJII's 2024 internet-user number shows mass demand. The World Bank's low fixed-broadband subscription figure shows room for fixed access growth. But the Telkom ARPU trend shows that many access customers are price-sensitive, and competition pushes even national operators toward simpler, cheaper internet-only plans. For Intrakom, the rational response is not to outspend the national carriers. It is to choose customer segments where installation quality, multi-vendor coordination and support responsiveness matter more than a small monthly discount.

The APJII and IDNIC records imply another cost: compliance and abuse handling. APNIC's ASN record includes an abuse mailbox, abuse@intrakom.co.id, and places the AS under IDNIC/APJII resource administration (https://rdap.apnic.net/autnum/142374). IPinfo marks the prefixes as RPKI valid on its AS142374 page, with the two IPv4 /24s covered by valid route-origin authorization at the time of its scan (https://ipinfo.io/AS142374). That is good hygiene. It is not free. A provider that sells connectivity to many customers must keep routing records, contact data, abuse processes and address assignments clean enough that upstreams, exchanges and customers trust it.

Public address scarcity is especially sharp for a provider with only a visible /23 of IPv4. In practice, not every customer needs public IPv4 addresses, and NAT, IPv6 and provider-managed designs can reduce pressure. But enterprise customers still ask for reachable services, VPN endpoints, whitelisting, firewall rules and static-address arrangements. A 512-address block can support a small managed-access business, but it is not a deep pool. If Intrakom grows into more hosting, more direct customer allocations or more public-service work, address discipline becomes a unit-economics question: which customers deserve scarce public addresses, and what price or contract length justifies the allocation?

This is one reason a managed-access provider's economics cannot be read from subscriber count alone. A customer with one office link, a managed firewall, a static address, remote monitoring and periodic visits may be more valuable than several customers buying a cheaper unmanaged line. The higher-value customer consumes engineering time but also gives the provider a reason to charge for more than a port. The lower-value customer can fill bandwidth but create little room for support cost, address scarcity, supplier tickets or bad-debt risk. Intrakom's public material gives no revenue split, but the service menu points toward the higher-value version of the business: managed systems, security, data-centre integration and responsive support rather than a pure residential access ladder.

The accounting discipline is unforgiving. Before the first monthly invoice becomes profitable, a provider may have spent sales time, site-survey time, procurement time, configuration time, travel time and customer-training time. If the installation is simple and the customer stays for years, those costs amortise quietly. If the customer churns after a short contract, disputes the bill, or asks for repeated support outside the agreed scope, the provider can lose money even if the nominal monthly price looks attractive. That is why the project-manager hiring language is economically significant. A project manager who compresses the time from purchase order to completion is not only improving customer experience; that person is shortening the period in which costs accumulate before recurring revenue stabilises (https://www.linkedin.com/posts/mutya-kristy-sulba-6790b4219_hiring-projectmanager-ict-activity-7463545378714324992-60be).

Supplier choice shapes the same calculation. Intrakom's own website puts access and vendor partners in public view, but it does not say which supplier is used for which customer, which links are leased, which are resold, which are physically diverse, or which contract carries penalty rights if service fails (https://www.intrakom.co.id/). If a provider buys last-mile access from one partner, transit from another, equipment from a distributor and security support from a vendor, the customer may still see one Intrakom service. The hidden risk is that each supplier has its own maintenance window, ticket process and commercial priority. Intrakom's margin is the fee for absorbing that complexity. Intrakom's vulnerability is that it cannot fully control every external component.

The business therefore resembles a small general contractor more than a simple utility. A building owner does not pay a contractor only for cement and cable. It pays for sequencing, accountability and fault resolution. In connectivity, the same principle applies: the line must arrive before the router can be tuned; the address plan must be ready before VPN rules can be set; the customer contact must approve an outage window before a cutover; the monitoring system must know which alarms matter before support can be efficient. The provider that does this well becomes sticky. The provider that fails turns every invoice into a renegotiation.

The credible failure is a handoff that stops being boring

The failure scenario for Intrakom is not a dramatic national blackout. It is a handoff that stops being boring. Imagine a Jakarta-area business with several branches using Intrakom because the company can combine access, routing, security equipment, monitoring and on-site help. Sales has received the purchase order. A project manager is coordinating the branch rollout. A wholesale fibre partner must deliver the access loop, an upstream path must carry traffic cleanly, a firewall must be configured, and the customer expects the site to open on Monday.

If the access right is delayed, the whole chain stalls. If the supplier changes a handoff, the device configuration has to be revised. If an upstream route shifts and latency rises, Intrakom owns the customer conversation even when another network caused the change. If the NOC has too many alarms and too few skilled engineers, the customer experiences the company as unresponsive. If a technician cannot visit during the window the customer can grant building access, the SLA becomes a piece of paper. The economic damage is not only the immediate support cost. It is the lost trust that makes the next renewal a price auction.

The public records point to exactly those dependencies. PeeringDB lists facilities and exchanges, not the underlying commercial contracts (https://www.peeringdb.com/api/net/28165?depth=2). Intrakom's website lists partners and support promises, not supplier SLAs or customer renewal rates (https://www.intrakom.co.id/). The LinkedIn project-manager post highlights timeline, quality and completion from purchase order through delivery, which is precisely where an integration provider's operational risk sits (https://www.linkedin.com/posts/mutya-kristy-sulba-6790b4219_hiring-projectmanager-ict-activity-7463545378714324992-60be). The gap between the public claim and the private contract is where the underwriting work belongs.

One should not punish a private company for not publishing everything. Small providers rarely disclose churn, gross margin, wholesale access contracts, NOC staffing, address-assignment policy, route incidents or ticket response distributions. But a serious buyer or large customer should not confuse public web presence with operational proof. The test is whether Intrakom can show current port invoices, upstream agreements, partner supply arrangements, recent SLA reports, trouble-ticket histories, preventive visit logs, customer references and security/abuse processes. Without those, the company remains credible but hard to price.

Regulation is also part of the product

For an Indonesian ISP, regulatory standing is not background paperwork. It is part of the product customers are buying. APJII's member page places PT Solusi Integra Datakom in the ISP licence category and gives a public membership identity under the Intrakom brand (https://www.apjii.or.id/anggota/idnic?legality=&name=&page=113). APNIC and IDNIC records place the same company in the internet-numbering system, with an ASN, IPv4 and IPv6 resources, abuse contacts and maintainers (https://rdap.apnic.net/autnum/142374; https://idnic.rdap.apnic.net/ip/103.171.184.0/23). These records are useful not because they are glamorous, but because enterprise customers need a provider that can stand behind its service with recognized internet-resource administration.

The regulatory and resource layer also affects day-to-day operations. Abuse reports need a reachable mailbox. Route-origin records need to be kept correct. Contact details need to remain current. Address assignments need to be defensible. A serious customer may never read RDAP records, but it benefits when the provider maintains them properly. If abuse handling is poor, addresses can acquire a bad reputation. If route records are neglected, reachability can suffer. If a contact goes stale, escalation takes longer. The APNIC records show the minimum public accountability surface; they do not show whether internal processes are strong enough under stress.

Indonesia's internet geography raises the value of local exchange participation. Traffic that stays local can be faster, cheaper and easier to diagnose than traffic that wanders through distant transit paths. PeeringDB's five exchange entries and the corroborating IIX-Jakarta and EdgeNXT pages therefore matter even though Intrakom is small (https://www.peeringdb.com/api/net/28165?depth=2; https://www.pch.net/ixp/details/110; https://care.edgenxt.com/index.php/customer/detail/107). The provider is not claiming global scale. It is claiming a place in the Jakarta interconnection fabric where local traffic and customer support expectations meet.

There is a geopolitical and operational edge to this as well. Indonesian enterprises and public institutions increasingly care where data, support and network operations sit, not only whether a link is fast. A local provider with Indonesian legal identity, local APJII standing and Jakarta-area support can be easier for such customers to contract with than a remote cloud or foreign hosting supplier. That does not make Intrakom immune to larger competitors; it gives it a different basis for trust. Locality can be a commercial asset when the customer values Indonesian procurement fit, reachable engineers and familiar escalation paths.

But locality can also trap a provider. Customers may expect national-carrier reliability from a smaller company because both sell internet access. Regulators and exchanges may expect professional abuse handling even if the support team is small. Vendors may expect timely payment. Engineers may expect career progression. The public evidence suggests Intrakom has the building blocks of legitimacy; the private test is whether the business can carry those obligations without thinning the support quality that makes the service attractive.

Competition comes from both carriers and integrators

Intrakom faces competition from at least four directions. The first is the national and large regional carrier set: companies with deeper networks, stronger procurement standing, broader brand recognition and more direct fibre reach. They can bundle access, mobile, fixed broadband, data centre and enterprise services at a scale Intrakom cannot match. The second is the specialist ISP set: local or regional providers that can undercut price in specific districts or serve residential and SME customers with a leaner cost base. The third is the systems-integrator set: firms that do not own meaningful network resources but can sell devices, security, cabling, managed services and cloud projects. The fourth is internal IT, especially for customers large enough to manage carrier contracts and equipment themselves.

Intrakom's defence is to be good enough in all the adjacent layers. It does not need to be the cheapest raw ISP if it is the most convenient accountable provider for a customer that wants a complete site. It does not need to be the deepest systems integrator if it can combine network reach, IDNIC resources, support and local interconnection. It does not need to beat a national carrier on backbone scale if it can respond faster in a building, a branch or a mid-sized project.

The partner list on Intrakom's site points to this strategy. Fiberstar, iForte and Fibermedia suggest last-mile and fibre-ecosystem dependencies; Ruijie, Commscope and Sophos suggest equipment, structured cabling and security solution work; APJII and IDC point to internet-community and data-centre context (https://www.intrakom.co.id/). The list is not a contract ledger. It is a map of the dependencies Intrakom must manage. Each partner can extend the company's reach. Each partner can also become a source of delay, margin compression or blame if the customer expects Intrakom to own the full result.

The company's AI offering should be treated cautiously. The website says Intrakom offers AI combining generative AI and computer vision for automation, security and operational efficiency (https://www.intrakom.co.id/). There is not enough public evidence to judge whether AI is a substantial revenue line, a developing product, or a branding extension attached to broader IT services. In the economics of this company, AI is not the anchor. The anchor is still connectivity and integration. AI may help sell a digital-infrastructure bundle, but the durable question is whether the company can deliver and support customer sites.

There is also no public evidence of a large downstream network base. PeeringDB and IPinfo do not show a rich set of downstream customers for AS142374; IPinfo reported no downstreams on its page at the time reviewed (https://ipinfo.io/AS142374). That matters. A wholesale or carrier-of-carriers business would be valued differently. Intrakom's public evidence fits better with a retail/enterprise ISP and managed-service integrator that uses exchanges and upstreams to improve service quality for its own customers rather than to sell transit at scale.

The most dangerous competitor may be the one that looks administratively easier, not the one that looks technically stronger. A large carrier can tell a procurement department that the access link, billing, escalation and compliance paperwork all come from one national-scale name. A systems integrator can tell the CIO that it will manage the devices and applications while leaving the carrier contract untouched. Intrakom has to persuade the customer that its middle position is not an extra layer of complexity but the layer that removes complexity. That sales argument depends on proof: faster installations, better incident handling, clearer documentation, more usable monitoring and an engineer who understands the site.

This is why the company should not chase every adjacent product simply because it can. AI, cyber security, hardware, software, data-centre integration and connectivity all fit the website narrative, but each line needs skill and support depth. For a small provider, breadth is profitable only when the products reinforce the same customer relationship. A managed firewall attached to an Intrakom access link can deepen the account. A speculative AI project with no link to the provider's operating strengths could distract scarce engineering time. The best version of the company uses adjacent services to make the connectivity account stickier, not to become a thin reseller of every technology category.

Scale therefore has two meanings. Network scale is limited by the public route evidence. Account scale may be more important. If Intrakom can grow from one link to several sites, from access to managed security, from installation to monitoring, and from a project to a multi-year support relationship, then the company's small ASN can support a larger economic relationship than its route table implies. If it sells one-off projects without renewal depth, the route evidence remains interesting but the business is less durable.

What the public signals say about customers

Customer evidence is both promising and incomplete. Intrakom's website displays client logos, including public-sector, consumer-brand and business names, and it places those logos alongside a partner list and regulatory-compliance/vendor-integration logos such as LKPP, Inaproc, Transjakarta and PAM Jaya (https://www.intrakom.co.id/). The public page does not say whether each logo reflects a current contract, a past project, a procurement registration, a framework listing or a broader business association. A careful reader should therefore not infer current recurring revenue from the logos alone.

Still, the types of logos matter. If Intrakom serves institutions, public bodies, consumer brands or multi-site businesses, the value proposition is likely less about low-price residential access and more about dependable project execution. Public-sector and institutional customers tend to value paperwork, accountability, installation discipline, support escalation and procurement fit. Private enterprise customers tend to value uptime, documentation, predictable monthly costs and one party that can coordinate the vendor mix. Both groups reward the operator that reduces the customer's internal coordination burden.

LinkedIn's company-size band of 11-50 employees is also telling (https://id.linkedin.com/company/pt-solusi-integra-datakom). It suggests a company large enough to have sales, technical, HR and project functions, but small enough that hiring and retention matter. A single project manager can materially change throughput if the company is juggling multiple installations. A single senior network engineer can materially change incident quality. The business can feel highly responsive when the right person is available and fragile when too much depends on a few people.

The public hiring post is therefore more than a recruitment note. Its responsibilities run from purchase order to project completion, with internal-team and customer coordination, target delivery, progress monitoring, documentation and reporting (https://www.linkedin.com/posts/mutya-kristy-sulba-6790b4219_hiring-projectmanager-ict-activity-7463545378714324992-60be). That is the operating model in miniature. Intrakom sells a result; project management is how the result becomes billable without burning the margin in delay and rework.

The absence of broad customer-review evidence is not automatically negative. Many Indonesian enterprise connectivity relationships do not leave public review trails. A large customer may complain privately, through a procurement office or by switching provider at renewal. That makes public chatter a weak instrument here. The better signal is the combination of published services, route evidence, APJII/IDNIC standing, exchange presence and hiring needs. It says the company is real and operational; it does not prove customer concentration, renewal quality or profitability.

What a buyer would pay for, and what it would demand

A buyer, lender, acquirer, large customer or regulator would pay for the parts of Intrakom that reduce uncertainty: an active Indonesian legal entity, APJII/IDNIC membership, ISP classification on APJII's member page, AS142374, valid public resource records, exchange presence, local support promises, partner relationships and customer references (https://www.apjii.or.id/anggota/idnic?legality=&name=&page=113; https://rdap.apnic.net/autnum/142374; https://www.peeringdb.com/net/28165). It would discount the business for what is not public: audited financials, recurring revenue mix, gross margin by product, customer concentration, last-mile supplier contracts, upstream commitments, route incident history, service-credit exposure, NOC staffing and the true status of displayed customer logos.

The proof demand would be practical. Show the NIB and legal filings; show the ISP licence evidence behind the APJII entry; show current APJII, IIX, EdgeNXT and data-centre invoices; show upstream and last-mile contracts; show address-management policy; show support ticket distributions; show the oldest active customers; show renewal rates; show which customers buy only access and which buy managed-service bundles; show device inventory; show the top ten incidents and how they were resolved. A buyer would not be paying for 512 IPv4 addresses alone. It would be paying for the repeatable ability to turn a messy branch-network problem into a supported monthly contract.

The one fact that would most change the judgement is recurring gross margin by customer cohort. If Intrakom's managed-service customers renew for several years, buy multiple sites, accept priced support and generate low incident cost, the company is a valuable local integration platform. If revenue is mostly low-margin pass-through access with high support burden and fragile supplier dependencies, the public route evidence would overstate the business quality. The second most important fact is customer concentration. A few institutional logos could make the company appear stronger than it is if one renewal carries too much revenue.

Public evidence register

The strongest identity evidence is the combination of Companies House Indonesia, LEI Lookup, APJII/IDNIC and APNIC RDAP. Companies House gives the Indonesian company registration number, registration date and South Jakarta registered address (https://companieshouse.id/solusi-integra-datakom). LEI Lookup corroborates the legal name, active status, entity ID and South Jakarta address (https://www.lei-lookup.com/record/926900193C2A334F2D68/). APJII lists the Intrakom brand, registration number 1034, ISP licence type, domain and Bekasi office address (https://www.apjii.or.id/anggota/idnic?legality=&name=&page=113). APNIC RDAP confirms AS142374 and the IPv4 and IPv6 resource records tied to PT Solusi Integra Datakom (https://rdap.apnic.net/autnum/142374; https://idnic.rdap.apnic.net/ip/103.171.184.0/23; https://idnic.rdap.apnic.net/ip/2400:a060::/32).

The strongest operating-surface evidence is the Intrakom website, PeeringDB and exchange corroboration. The website supports the claims about network infrastructure, managed services, support, monitoring, engineer visits, partners and displayed customer logos (https://www.intrakom.co.id/). The footprint page supports the APJII connectivity and data-centre positioning language (https://www.intrakom.co.id/footprint). PeeringDB supports the AS number, network type, traffic band, open peering posture, two Jakarta facilities and five exchange connections (https://www.peeringdb.com/api/net/28165?depth=2). EdgeNXT and Packet Clearing House corroborate public exchange presence at EdgeNXT and IIX-Jakarta (https://care.edgenxt.com/index.php/customer/detail/107; https://www.pch.net/ixp/details/110).

The market-context evidence is APJII's 2024 internet-penetration release, World Bank fixed-broadband data and Telkom's 9M25 information memo. APJII supports the scale of Indonesian internet use (https://apjii.or.id/berita/d/apjii-jumlah-pengguna-internet-indonesia-tembus-221-juta-orang). The World Bank API supports the low fixed-broadband subscription rate (https://api.worldbank.org/v2/country/IDN/indicator/IT.NET.BBND.P2?format=json&per_page=10). Telkom's memo supports the point that broadband access pricing is under pressure even at the national incumbent scale (https://www.telkom.co.id/minio/show/data/lampiran/1761838522183_original_TLKM-9M25-Info-Memo.pdf).

The unofficial market signals are LinkedIn's company profile and the public project-manager hiring post. LinkedIn supports the company's self-description as a managed-service provider, the South Jakarta headquarters and 11-50 employee size band (https://id.linkedin.com/company/pt-solusi-integra-datakom). The hiring post supports the inference that project execution from purchase order to completion is a current operating need (https://www.linkedin.com/posts/mutya-kristy-sulba-6790b4219_hiring-projectmanager-ict-activity-7463545378714324992-60be). These are not statutory records; they are useful signals about labour, customer delivery and commercial positioning.

The judgement

Solusi Integra Datakom should be read as a small but visible Indonesian connectivity integrator with a real internet-resource footprint, not as a miniature national carrier. The public evidence supports a company that has the legal identity, IDNIC/APJII standing, ASN, address resources, exchange presence and customer-facing support language needed to sell managed connectivity in the Jakarta-area enterprise market. It does not support a claim of broad national infrastructure control, deep audited financial strength or proven large-scale downstream network economics.

That distinction is the investment case and the risk. The attractive version of Intrakom earns from the friction between a customer's need and the messy access market: the provider that can stitch a site together, watch it, visit it and keep the customer from managing five vendors can charge for more than bandwidth. The weak version is exposed to every supplier delay, support overload and price comparison that comes with small-provider access resale. The public record leans toward the former, but the private documents would decide the price.