Coding School Management Software in Indonesia: What Multi-Branch Operators Have to Reconcile

Your branches are not branches, not in the sense the software you are evaluating means the word. Each one is a separately licensed unit with its own number, its own provincial calendar and its own reporting clock.

Current as of August 2026.

Why does every branch of a coding school need its own licence?

Because the licence attaches to the premises and the local office, not to the brand. Permendikbud 81/2013 tentang Pendirian Satuan Pendidikan Nonformal is the regulation a coding or robotics provider is established under, as a Lembaga Kursus dan Pelatihan.

Pasal 6 sends the application to the Kepala Dinas Pendidikan Kabupaten/Kota, and Pasal 6 ayat (3) gives that office up to 30 hari kerja to approve or refuse. Pasal 5 ayat (2) requires evidence of ownership or right of use over the teaching premises for 3 years, and that document describes one address. A second site cannot inherit it.

Pasal 7 closes the loop. Every licensed unit receives its own Nomor Induk Satuan Pendidikan Nonformal. Six branches across four kabupaten are six numbers issued by four offices on four separate clocks.

Pasal 10 adds a use-it-or-lose-it rule. A unit that has run no programme for 2 consecutive years can be closed by the kabupaten or kota government. A dormant branch is not a paused branch.

That is the argument for treating the branch as a first-class object in the data model rather than a label on a class. Happy Kamper's multi-location management holds each site as its own record under one operator account, which is where a licence reference and a Nomor Induk belong. It does not lodge the application.

One franchise point survives the same logic. A franchise agreement usually commits the branch to a written curriculum standard, since PP 42 Tahun 2007 tentang Waralaba requires a franchise to hold a standard for its services dibuat secara tertulis, so version control over lesson content matters as much as the timetable does.

Two provinces, two school calendars

Provinces set their own school calendars, and Jawa Timur and Jawa Barat published different ones for the same school year. They diverge most at the December break, which means a branch in one province can be teaching while a branch in the other is shut.

A cohort intake is a promise about a start date, a finish date and a fixed group moving together, and that promise is made against a calendar the operator does not own. Scheduling and enrollment that assumes one term definition per account will fight the operator every July and every December.

How should a cohort be defined when the competition defines it differently?

By storing the birth date and deriving everything else, because the competition will not use your grouping.

The WRO 2026 RoboMission General Rules fix the unit plainly, stating that a team consists of 2 or 3 students. The age bands overlap rather than tile, and eligibility runs on the year of birth rather than age on the day, so a child born in 2014 is eligible for two bands in the same season.

So a robotics centre has at least three different groupings live at once. The teaching cohort, which is a fixed intake moving through a curriculum. The class group, which is whoever can attend Thursday at four. And the competition team, which is a small named set inside an age band decided by somebody else.

Software that models a child as belonging to one class cannot hold those three at the same time. What it needs is a child record carrying a date of birth, and membership that is many-to-many. Happy Kamper stores the date of birth on the child profile alongside medical records and emergency contacts, and progress records belong to the child rather than to whichever group they sat in that term. It does not decide that a student has finished a level, and it does not register a team with WRO.

Coding and AI already have a national vocabulary

Coding and artificial intelligence now sit inside the national school curriculum, under three named elements: Algoritma dan Pemrograman, Analisis Data, and Literasi dan Etika Kecerdasan Artifisial. Those three headings are a ready-made spine for a project report a parent can actually read.

What does term billing have to survive in a multi-branch operation?

Two things, and neither of them is the invoice template.

The first is that the term boundary is not the same everywhere. Billing a Jawa Barat branch and a Jawa Timur branch for terms that began in different weeks are two different runs.

The second is that the reporting cycle is the semester, and it is compulsory. The Direktorat Kursus dan Pelatihan requires each unit's Dapodik record to be refreshed at least once per semester, covering informasi lembaga, pendidik/instruktur, pembelajaran, dan peserta didik, and a unit that misses it for five consecutive semesters can be deactivated through the verval system. Enrollment data is not only a billing input, it is a filing obligation, and it is filed per branch.

A charge has to be raisable in rupiah against a child record, at one branch, without disturbing the recurring term fee. Happy Kamper's billing and invoicing is IDR-native and sits on the same child record as enrollment and attendance, per branch. It does not file anything to Dapodik, and no vendor should be described as though it does.

Three products a multi-branch operator can actually compare

Compare on three things, what a branch costs, what a branch is allowed to be, and whether the money can land in rupiah. All three products below were read on the vendors' own sites in September 2026.

Teachworks prices the branch directly. Premium is listed at USD 187.99 per month and is the only tier carrying branch accounts, the first 5 included and each further branch at USD 35 per month, with fees charged in US dollars. It suits an operator whose sites genuinely differ, because there the branch is a billing object rather than a filter on a report.

Jackrabbit Class lists USD 49 per month as a starting price and USD 245 for Enterprise, the lower tiers priced on student count at month end. It suits a centre growing in students rather than in sites. Its integrated card processing is offered in the United States, Canada, Australia, New Zealand and the United Kingdom, so an Indonesian operator would be collecting fees outside the system that holds the roster, which is a practical disqualifier rather than a criticism.

AOne is the local entry, and the Indonesian vendor's own site says it controls every branch and franchise in one integrated system, listing kurikulum alongside students, teachers and payments. It publishes no price, so that comparison has to come from a quote. It suits a franchise network that wants a supplier in Bahasa Indonesia.

Happy Kamper sits in that last bracket. Billing is in rupiah, each site is held as its own record, and the parent app runs in Bahasa Indonesia and English.

On one dimension Jackrabbit Class is stronger, and it is the dimension that decides it for a school pushing back-to-back cohorts through one lab with a fixed number of workstations or robot kits. Its own site says its appointments reduce scheduling errors and ensure rooms are not double-booked. Happy Kamper does not detect room conflicts, so a centre whose binding constraint is the room rather than the roster should weigh that heavily.

Which operators do not need this software yet?

A single site running one cohort at a time with one instructor. If that is you, you do not need this yet. A spreadsheet for the roster, a WhatsApp group for parents and a transfer per term genuinely work at that size.

The risk of staying is not a missing feature, it is succession. The roster, the fee history and the parent contacts sit in one person's file and one person's phone, so the business cannot be handed over, audited or sold without that person.

It stops working at the second site, or earlier, at the point where two cohorts run at once in the same room. That is when a clash has to be visible to somebody who was not in the conversation that created it.

Where should a buyer push hardest during a demo?

On the branch, the cohort and the money, in that order.

The branch as an object. Can a branch exist as its own entity with its own licence reference and its own Nomor Induk, or is it a label on a class? Ask to see two branches with different term dates in the same account.

Many groups, one child. Can a student belong to a teaching cohort, a weekly class group and a competition team at the same time, without duplicate records?

Birth date, not age. Does the child record store a date of birth, so a WRO age band can be evaluated per season rather than fixed once?

The report a parent will actually read. Can a project outcome be recorded against the child and sent to the parent, in Bahasa Indonesia, without a staff member retyping it?

Charges outside the fee. Can a one-off item be raised in rupiah against a child, at one branch, without disturbing the recurring term fee?

Where it stops. Anything a vendor implies about Dapodik, a licence or a certificate deserves a live demonstration rather than a screenshot.

The line software does not cross

Happy Kamper covers the operating layer of a multi-branch coding or robotics school. It does not lodge a licence application with a Dinas Pendidikan, it does not update Dapodik, it does not register a competition team, and it does not issue a competency certificate. The regulatory work stays with the branch that holds the licence, because that is where the law put it.

This is general information rather than advice. Licensing requirements are set locally and they change, so confirm the current position with the kabupaten or kota office that issues your own Nomor Induk.