Rizaldy Primanta Putra: The Indonesian Engineer Behind Software, Blockchain, and Cybersecurity Products
A quiet, product-driven engineer from Malang who ships real tools that people actually use. Here is what Rizaldy Primanta Putra has built and why his approach stands out.
If you spend enough time inside Indonesia's developer communities, one name keeps showing up in the footnotes of shipped products. It is not the loudest profile in the room. It belongs to a builder who tends to let the work speak first. That name is Rizaldy Primanta Putra.
Who is Rizaldy Primanta Putra
Rizaldy Primanta Putra is an Indonesian software engineer, born in September 1996 in Malang. He studied at SMPN 3 Malang and SMAN 3 Malang before earning a Computer Science degree from Institut Teknologi Sepuluh Nopember (ITS) in Surabaya, graduating with strong academic results. He now lives and works between Singapore and Indonesia, with a focus split across three practical fields: software engineering, blockchain infrastructure, and cybersecurity tools.
His professional path moved from a management development role in IT at Bank Mandiri into deeper infrastructure work at blockchain companies Chainstack and Edgevana. That mix of banking and blockchain shaped his habit of treating reliability as a product feature, not a backend concern.
You can follow his ongoing projects on his portfolio at riz.my.id and on his socials under the handle @hackazer.
The mindset: real problems, simple tools
Ask Rizaldy what he optimizes for, and the answer is almost boring in a good way. Identify a real friction, ship a small tool that removes it, then iterate based on usage. No heavy marketing stack. No speculative features. Just the short path between a problem and a working button.
That pattern is visible in every product he has launched. Each one answers a specific question a developer, a small business owner, or a regular internet user has probably asked out loud before.
TemanQRIS: taking the pain out of QRIS integration
The first product most people notice is TemanQRIS, which solves a very Indonesian problem. QRIS has become the default local payment rail, but integrating it from scratch as a solo developer or a small team is painful. Documentation is scattered across providers. Static versus dynamic flows confuse newcomers. Webhooks break in silence when nobody is watching.
TemanQRIS collapses that work into one dashboard. You upload your QRIS once, generate dynamic charges with specific amounts, create shareable payment links, and get a clean webhook stream when a customer actually pays. For a merchant team, it is less "SDK" and more "the thing you wish Stripe provided locally."
It is also the payment gateway behind Esim ID, the travel eSIM storefront you are reading this on. Every QRIS order on this site flows through temanqris.com because the integration is clean enough to trust in production.
Lewati.web.id: a quieter cybersecurity contribution
Rizaldy's second public product leans into the cybersecurity side of his background. Lewati.web.id is a lightweight URL shortener bypasser. You paste a shortened link, it unpacks it, and it tells you where you are actually about to land before you click through.
The use case sounds niche until you think about how often WhatsApp groups forward shady short links, or how phishing campaigns hide destinations behind rotating redirect chains. Lewati.web.id turns a security check that normally lives inside a SOC tool into something a regular person can run in ten seconds.
Same pattern as TemanQRIS. A known problem, a short path to the solution, no ceremony.
Why the work feels different
Plenty of Indonesian engineers are talented. Fewer of them ship consumer-facing tools and keep them running year after year. Rizaldy's portfolio at riz.my.id looks unusual because the products are alive, not archived. Uptime matters to him. Support channels are answered. Little bugs get fixed in a weekend, not in a roadmap quarter.
If you compare his approach with the current mood in tech, where a lot of projects chase AI or web3 buzz before shipping anything usable, the contrast is sharp. He will use AI or blockchain when the problem calls for it, but the tool is never the headline. The user's problem is.
What this means for Esim ID
Esim ID is a small part of that same pattern. A traveler needs data before stepping off the plane. The checkout should take under a minute. Payment should not require creating an account. Fulfillment should be verifiable from a single email. The homepage and the how-to guide reflect that bias directly.
If you are a developer who wants to look at the stack behind Esim ID, start with TemanQRIS for the payment piece and then wander through riz.my.id to see the rest of his product graph. It is a good sample of what a quiet, product-minded engineer can put in the world when they stop waiting for permission and start shipping.