We build software
for school, factory, and small business admin.
There are 19 products: factory payroll, school report cards and fee bills, aluminium quotations, laundry receipts, clinic medical records, village letters, and more. If none of them fits, we build one for you.
- SekolahinSchools and foundations with records split between the office, teachers, and the bursar.
- AsetinFacilities staff at schools and foundations with assets spread across several units.
- MutuinStudy programmes preparing their accreditation forms.
- PraktikinVocational schools with interns placed across many workplaces.
- SkorinTeachers with a stack of essay answers to mark.
- Smart LibrarySLiMS libraries where borrowing queues build up at the front desk.
- UpahinFactory HR teams who tally attendance, shifts, and overtime before every payday.
- AlumetriAluminium window and door fabricators who have to cost the materials before they can quote a price.
- AbseninField teams who work far from the office time clock.
- AmaninFactories that need evidence of SMK3 safety management from every inspection.
- KonveksinCMT and contract garment makers who pay their tailors per piece.
- PalletinFactory and distributor warehouses that need to know where each pallet is and what it holds.
- LarisinClothing shops where one design comes in many sizes and colours.
- LaundryinPay-by-weight laundries still writing receipts by hand.
- NagihinBusinesses that chase customers for payment one chat at a time.
- RawatinSmall clinics that keep queues, medical records, and payments in separate places.
- ServisinService businesses whose technicians move from one customer to the next.
Tell us which job you want out of Excel or group chats. If none of our products fits, we build a system for you.
A project runs in four steps
- 01
Describe the problem on WhatsApp
For example, overtime tallies from three plants sent through a group chat. If the problem doesn't need software yet, we'll say so.
- 02
Map the flow and the data
We study the forms, tallies, and approvals you use now. The scope is put in writing before anything gets built.
- 03
Run side by side
Old data moves across. For a while the new system and the old way run together until the numbers match.
- 04
Train the users, move to Ophar
The staff who use the system get trained. After that, maintenance of the system moves to Ophar.
We're a small company, so what we show you is the products themselves.
Product images are taken from the apps
The Sekolahin dashboard, the Upahin report, and the Alumetri quotation on this page are the real app screens, not design mock-ups.
Staff only see the data their role allows
Access in Upahin is set per role. Login can use two-step verification, and every data change is kept in an audit log.
Upahin calculates BPJS and PPh 21
Both go straight onto the payslip, so nobody calculates them separately in Excel.
Your message is read by the people who build the system
There is no bot or call centre in between.
How we run a project, on video
Frequently asked questions
Our data lives in Excel. How does it move?
Our team helps with the import. In Sekolahin, student data, schedules, and access roles go in stages, once the school signs off. In Upahin, employee data moves across before the system goes into use, then we check a sample together with HR.
Once the system is built, what does maintenance cost?
Maintenance is handled by Ophar and billed monthly. There are two models: one flat fee, or an itemised breakdown covering servers, fixes, and staff support. The model you choose goes into the agreement.
How long does custom software take, and what does it cost?
There's no fixed rate yet. Once we have mapped how you work, the cost and target timeline go into a scope of work that we both agree before the build starts.
Who owns the code?
The core code stays with Serpihan Tech. Handing over the source code needs a separate agreement.
The first consultation is free.