The TKDN website is the public face of Kemenperin’s domestic-content certification program (Tingkat Komponen Dalam Negeri). It’s where companies apply for certification, where the public verifies issued certificates, and where procurement systems confirm that a product actually carries a valid TKDN percentage. Like the other Kemenperin platforms, it has been rebuilt across four eras — PHP 5, PHP 8, React + Hono, and the consolidated Svelte + Go stack — with each era tightening the trustworthiness of the certificate registry.

The TKDN (Tingkat Komponen Dalam Negeri — domestic content level) website began on the same PHP 5 stack as the other Kemenperin systems. Companies submitted certification requests, uploaded supporting documents, and looked up issued TKDN certificates through server-rendered pages backed by a single MySQL database. Public visitors could verify certificate numbers — a critical trust function for government procurement — but the lookup was a plain table scan behind a form, and every certificate cycle meant staff keying in results by hand. Recap — Put the certificate registry online — lookup worked, but nothing was built to scale trust.

The PHP 8 rebuild gave the TKDN registry real structure. Certification requests moved through explicit verification stages, required documents became typed checklists, and certificates themselves became first-class records — number, product scope, validity window, and the calculation breakdown behind the TKDN percentage. The public lookup became an indexed search instead of a table scan, and staff gained batch tools for issuing certificates at the end of each verification cycle. Recap — Certificates became data — searchable, structured, and auditable for the first time.

Era three moved TKDN to the decoupled stack shared across Kemenperin systems: a React portal where applicants tracked their certification status in real time, and a Hono API that exposed certificate verification as a public endpoint — so procurement systems and buyers could validate a TKDN number programmatically, not just by reading a PDF. Behind the portal, staff worked from a typed review queue with the same staged pipeline, now fed by asynchronous document uploads instead of single form posts. Recap — Verification became an API — trust in TKDN certificates stopped depending on a phone call.

The current TKDN website runs on the consolidated Svelte + Go platform shared with Business Matching and P3DN Fasilitasi. The SvelteKit frontend serves the public certificate lookup with SSR speed, while the Go backend handles application intake, the verification pipeline, and the public verification API from a single binary. Three Kemenperin programs now share one stack and one deployment story — the TKDN registry benefits from every platform improvement the other systems drive, and certificate verification stays fast enough for procurement systems to call in-line. Recap — Three programs, one platform — the certificate registry that procurement can actually depend on.

The TKDN website runs on the consolidated Svelte + Go platform alongside Business Matching and P3DN Fasilitasi — the same certificate program that started as a PHP 5 bulletin, now an instant, API-verifiable registry that procurement systems can call in-line.