08/11
Case Study
New May 1, 2025 GovernmentKemenperinPHP

P3DN Fasilitasi — Kemenperin, Ministry of Industry

The facilitation arm of Kemenperin’s P3DN program — built greenfield in 2025 on SvelteKit + TypeScript + Supabase, the stack the older platforms spent years earning.

Year
2025
Focus
Government
Reading
2 min· 5 sections
Published
Web
Featured Page
P3DN Fasilitasi — Kemenperin, Ministry of Industry
Full Capture
P3DN Fasilitasi — Kemenperin, Ministry of Industry — detailed view

Project Overview

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. Unlike its sibling platforms, it has no migration story: built greenfield in 2025 directly on SvelteKit + TypeScript + Supabase — the beneficiary of every lesson the older systems paid for.

"Facilitation is a pipeline problem: a request enters, documents accumulate, reviews happen in stages. Starting on the modern stack meant the pipeline was designed-in, never excavated."

Engineering Notes Kemenperin P3DN Fasilitasi

The Stack — Built Right the First Time

Every rewrite preserved the program’s core workflow while replacing the foundation underneath it.

01

01. SvelteKit + Supabase — Built Right the First Time · 2025 — Present

P3DN Fasilitasi skipped the archaeology — launched in 2025 directly on SvelteKit + TypeScript + Supabase, the stack the older platforms spent years earning.

2025 Founded

Greenfield build — no migrations, no legacy debt.

05 Pipeline Stages

Explicit review stages from submission to reporting.

SvelteKit Stack

TypeScript end-to-end on the consolidated frontend.

Supabase Backend

Managed auth, Postgres, and document storage.

Era 01 — SvelteKit + Supabase — Built Right the First Time

P3DN Fasilitasi — the facilitation arm of Kemenperin’s P3DN program (Peningkatan Penggunaan Produk Dalam Negeri) — is the youngest of the three systems and the only one with no migration story. Built from scratch in 2025, it went straight onto SvelteKit + TypeScript with Supabase handling auth, the PostgreSQL database, and storage for facilitation documents. The facilitation pipeline — request, document review, verification, facilitated, reported — was designed in from day one instead of being reverse-engineered out of a monolith. Companies submit requests and track them through the stages; staff work a typed review queue; Supabase’s managed layer kept the team focused on the program’s workflow instead of infrastructure. Recap — The platform Business Matching took eight years to reach — P3DN started there.
P3DN Fasilitasi — platform home

P3DN Fasilitasi home

P3DN Fasilitasi — request flow

Facilitation request flow

P3DN Fasilitasi — tracking view

Request tracking

P3DN Fasilitasi — document review

Document review

P3DN Fasilitasi — staff queue

Staff review queue

P3DN Fasilitasi — admin console

Admin console

Design Decisions

What a greenfield government build looks like when the lessons are already paid for.

Start on the Target Stack

Business Matching took four rewrites to reach a modern architecture. P3DN skipped the archaeology — SvelteKit + TypeScript + Supabase from the first commit.

Pipeline as Schema

The five review stages are typed states in the database, not conventions in the code — every transition is enforced and auditable.

Managed Backends Buy Focus

Supabase auth, Postgres, and document storage removed weeks of infrastructure work — the effort went into the facilitation workflow, the part that is actually program-specific.

Self-Service Scales Staff

Status tracking and async document upload removed the "where is my request" phone calls — the single largest time sink for the facilitation desk.

Where It Stands Today

P3DN Fasilitasi runs on SvelteKit + Supabase — launched in 2025 with no legacy to carry, it is the reference implementation of the stack the older Kemenperin programs converged toward.