P3DN Fasilitasi is the facilitation arm of Kemenperin’s P3DN program (Peningkatan Penggunaan Produk Dalam Negeri) — helping Indonesian companies, especially IKM actors, through TKDN certification and domestic-product verification so they can supply government procurement. Like its sibling Business Matching platform, it has been rebuilt four times — tracking the same journey from a PHP 5 monolith to the shared Svelte + Go platform in production today.

P3DN Fasilitasi — the facilitation arm of Kemenperin’s P3DN program (Peningkatan Penggunaan Produk Dalam Negeri) — started on the same PHP 5 stack as the early Business Matching platform. Companies submitted facilitation requests for TKDN certification and domestic-product verification through server-rendered forms, with documents tracked by hand inside a shared MySQL database. The workflow was linear — request, review, facilitate, report — and a monolith could carry it. But document-heavy processes strained the simple upload pipeline, and every ministry reporting cycle meant manual exports assembled by staff. Recap — Digitized the front door of the facilitation program — the paperwork behind it stayed paper-shaped.

The PHP 8 rebuild gave the facilitation workflow real structure. Requests moved through explicit stages — submitted, document review, field verification, facilitated, reported — instead of freeform status text. Document checklists became typed data rather than informal attachments, and staff could finally export the reports the ministry asked for every cycle. Underneath, the same modernization as its sibling platform: Composer dependencies, PDO prepared statements, and tests around the review pipeline. Recap — Facilitation became a pipeline, not a pile — stages and checklists staff could trust.

Era three moved facilitation to the decoupled stack: a React portal where companies could watch their own requests move through the pipeline, upload documents asynchronously instead of in one giant form post, and get notified on status changes — backed by the same Hono TypeScript API family as Business Matching. Staff got a typed review queue with filters by stage, sector, and region. The API-first design meant the facilitation data could feed other ministry dashboards without scraping screens. Recap — Companies stopped calling for status updates — the portal told them first.

The current P3DN Fasilitasi system runs on the consolidated Svelte + Go platform shared with bm-online.id. The SvelteKit frontend handles the public request flow and the staff console in one codebase, while the Go backend serves document uploads, the review pipeline, and ministry reporting from a single binary. Consolidating the two Kemenperin systems onto one stack cut the maintenance surface in half — one deploy pipeline, one set of shared validation schemas, one operations story for both programs. Recap — Two programs, one stack — the platform both systems were converging toward.

P3DN Fasilitasi runs on the consolidated Svelte + Go platform alongside Business Matching — the same facilitation program that started on PHP 5, now part of a shared stack built to carry Kemenperin’s programs into the next era.