
MGA Research
Nov 17, 2026
A practical framework for investors, operators and counsel assessing compute, connectivity, electronic systems, personal data and intellectual property in Indonesia.
MGA Research | Research cut-off: 18 November 2026
An AI infrastructure project can sell rack space, GPU capacity, connectivity, software or a managed business outcome. Those activities may share equipment while creating different legal responsibilities. The starting question is therefore practical: what does each entity actually provide, control and promise?
Consider a company offering a private AI environment to Indonesian enterprises. It might own servers, rent a data-centre suite, buy network capacity, license a model and engage an overseas support provider. Describing the whole arrangement as “AI cloud” does not identify its licences, data obligations or contractual dependencies. This guide explains the principal distinctions; its implementation recommendations are MGA analysis.
Map the service before mapping the rules
Use this simplified project map to connect technical layers with legal questions:
APPLICATIONS AND DECISIONS → intended users, sector rules, accountability
MODELS AND KNOWLEDGE → licences, training rights, intellectual property
DATA AND OPERATIONS → purposes, access, transfers, security, retention
COMPUTE AND CLOUD → hosting activity, PSE assessment, service commitments
NETWORKS AND CABLES → operator roles, telecom approvals, capacity rights
POWER AND FACILITIES → site approvals, supply, cooling, operational readinessFor each layer, identify the contracting entity, operator, customer and subcontractors. Then mark who controls the assets, processes information and bears failure risk. This reveals issues that a list of servers or a corporate organisation chart can miss.
OSS and KBLI: classify the actual activity
PP 28/2025 replaced PP 5/2021 as Indonesia’s risk-based business-licensing framework. Investment Minister/Head of BKPM Regulation 5/2025 supplies current OSS procedures. Depending on activity and risk, an NIB may need to be accompanied by a Standard Certificate or licence, alongside applicable basic and sectoral requirements. An NIB alone is not evidence that every project approval is complete. PP 28/2025; BKPM Regulation 5/2025.
Classification must use the current activity descriptions. Komdigi’s operational manual states that e-Telekomunikasi stopped accepting KBLI 2020 codes on 18 June 2026, requiring corresponding NIB updates through OSS. Komdigi operating guidance.
KBLI 2025 code 63102 covers computing infrastructure and hosting, including IaaS, PaaS and data-centre colocation. Code 62194 has a different, narrower purpose: reusable AI modules, libraries and frameworks for other developers. It is not a generic classification for every end-user AI application. These are illustrative distinctions, not a universal licence package. Match the complete revenue model, ownership structure, location and service scope to the applicable requirements. Official KBLI booklet; OSS description of 62194.
Connectivity: customer, reseller or operator?
Buying connectivity for a compute service and undertaking telecommunications activities require different assessments. Examine who supplies transmission to customers, controls the network, holds capacity rights and assumes service obligations. A contract label, server location or separately itemised connectivity fee cannot resolve those questions alone.
The statutory starting point is Law 36/1999, read with the Job Creation amendments under Law 6/2023. PP 46/2021 and the applicable provisions of Ministerial Regulation 5/2021 remain central sector instruments. Current business standards include Komdigi Regulation 15/2025, which replaced Regulation 3/2021. DPR compilation of amendments; PP 46/2021; current sector standards.
Avoid treating Regulation 5/2021 as an untouched text: Regulation 7/2026 repealed specified cellular subscriber-registration provisions. For a cable-dependent project, separately document operator responsibilities, landing arrangements, restoration, capacity delivery and permitted use. Regulation 5/2021 status record.
Electronic systems: deployment choices have consequences
The ITE framework comprises Law 11/2008 as amended, including Law 1/2024. Assess electronic-system obligations under PP 71/2019 and private-scope PSE registration under Ministerial Regulation 5/2020, amended by Regulation 10/2021. Registration is distinct from business licensing; neither substitutes for the other. ITE amendment; private PSE regulation; 2021 amendment.
PP 71/2019 draws a consequential distinction. Article 20 generally requires public-scope electronic systems and data to be managed, processed and/or stored in Indonesia, subject to its specified exception. Article 21 allows private-scope operations domestically and/or abroad, with supervision and law-enforcement-access requirements; financial-sector rules remain separately applicable. Consequently, neither “everything must stay in Indonesia” nor “private cloud can operate anywhere without conditions” is a reliable project rule. PP 71/2019, Articles 20–21.
Personal data: follow the processing, including support access
Indonesia’s PDP Law, Law 27/2022, already applies. Determine controller and processor roles from the actual activities, identify the processing basis, and assess high-risk processing under Article 34. Article 51 requires processors to follow controller instructions and obtain written approval before involving another processor. PDP Law.
Article 56 establishes a sequence for overseas transfers: equivalent or higher protection in the recipient country; failing that, adequate binding protection; and, where neither condition is met, the data subject’s consent. Map training, inference, retrieval, logs, backups and administrator access separately. Hosting the main database locally does not establish that every processing activity remains domestic. PDP Law, Article 56.
Intellectual property: inputs and outputs need different answers
Law 28/2014 protects qualifying works, including computer programs, while distinguishing protected expression from ideas, methods and data as such. Assess licences and exceptions for the actual copying and use involved in training or retrieval. Public accessibility does not itself establish permission. Contracts should distinguish background technology, project developments, datasets, model access and output rights. Copyright Law.
DJKI’s 27 October 2026 discussion of AI training and text-and-data-mining provisions concerns a Copyright Bill. Proposed exceptions should not be treated as enacted permissions. Similarly, an ownership clause cannot guarantee that every generated output qualifies for statutory protection. DJKI’s explanation of the proposed reform.
Turn the analysis into a workable project
Before committing to delivery, assemble five connected records:
Service map: what is sold, by whom, to which users, using whose infrastructure.
Approval matrix: activity classifications, licences, registrations, site requirements and responsible entities.
Data-flow record: processing purposes, countries, access, retention and subcontractors.
Rights schedule: permitted software, model and dataset uses, with ownership and reuse boundaries.
Operating contract: acceptance tests, capacity, security, incidents, audit evidence, continuity, liability and exit.
These records help expose a practical mismatch: a supplier may promise a complete managed service while its approvals, upstream contracts or technical controls cover only part of it.
AI-specific guidance adds another layer. Ministerial Circular 9/2023 addresses AI ethics; it is not a comprehensive AI statute. The official policy materials examined describe the national AI roadmap as under development. Treat proposals separately while applying existing law to the service already being built. Circular 9/2023; Komdigi policy statement, 6 October 2026.
Legal information notice: This dated guide provides general information and MGA analysis, not advice on a particular project. Applicable requirements depend on the service, parties, users, data and location. Obtain a project-specific assessment before implementation.