BUNGKUS — A Vertical Operating System for Independent Film Production

BUNGKUS is an open-source Vertical Operating System (VOS) and Creative Resource Planning (CRP) platform for independent film production in Indonesia. Where StudioBinder targets established production houses on a per-seat subscription, BUNGKUS serves the crews who currently run everything on Word, Excel, and a WhatsApp group: upstart production houses, campus film communities, and student filmmakers.

Revise a script once, and every derived document follows — breakdown, budget, call sheet, location permits. On-set take logging keeps working even when the signal drops.

---

Project Info

Parameter	Detail
Project Type	Vertical Operating System (VOS) & Creative Resource Planning (CRP)
Model	Open Source
Role	Full-Stack Engineer & System Architect
Status	Work in progress, no public release yet
Tech Stack	Goravel (Go), PostgreSQL, Redis, Vue 3, TypeScript, Tailwind CSS, S3 (MinIO/Cloudflare R2), Docker

---

The Problems It Solves

• Scattered documents that go stale fast. Script breakdowns, budgets, call sheets, and permits are normally retyped by hand in Word and Excel. The moment the script is revised, there is no quick way to tell which documents followed the change and which are still on the old version.
• Crew rates leaking to the wrong roles. At indie scale, crew fees are the most sensitive number in the production. General project management tools tend to show the whole budget to everyone on the team, with no separation of access rights.
• Shooting locations rarely have good signal. The crew still has to log take numbers, sound notes, and continuity precisely, with no reliable internet connection on set.

---

Architecture & Engineering Highlights

• Script parser as the single source of truth. Screenplays (.fountain / .fdx) are parsed on the backend into breakdown elements — sets, characters, props, wardrobe — automatically. Script revisions are locked down with stable scene numbering, so an inserted scene can be added as 12A without shifting every scene number after it.
• Strict multi-tenant isolation at the database layer. Tenant boundaries are enforced in PostgreSQL, not just in application code. Rate-card privacy gating (people.view_rates) redacts crew fees and budget figures at the API level and inside exported documents, so sensitive numbers never reach roles that should not see them.
• Immutable document engine. Official documents — Call Sheets, Master Breakdowns, Location Permits, Release Forms — are issued as immutable PDF/XLSX snapshots generated by a native Go engine using excelize. Any document already circulating among the crew can be traced back to the exact data version it was issued from.
• Optimistic concurrency control. Producers, directors, and first assistant directors routinely edit the stripboard or budget at the same time. Writes are guarded with If-Match headers and a row_version column, so two people cannot silently overwrite each other’s work.
• Two UI modes, one database. The Vue 3 + TypeScript frontend splits into a Desk Mode (desktop, for table analysis and the inspector) and a Field Mode (high-contrast mobile PWA for logging takes on set). Field Mode uses an idempotency key (client_uuid) so notes resent when the connection returns do not create duplicates.
• Contract-driven development. Backend–frontend integration is driven by a single openapi.yaml schema, and the core flows are covered by an automated integration suite built on testcontainers-go — around 89 tests and still growing.

---

Tech Stack

• Backend: Goravel (Go framework), PostgreSQL (UUID v7/v4, JSONB, generated columns), Redis, S3-compatible storage (MinIO / Cloudflare R2), Docker.
• Frontend: Vue 3 (Composition API), Vite, Tailwind CSS, shadcn-vue (Reka UI), TanStack Vue Query v5, Pinia, PDF.js.
• Testing & CI: OpenAPI spec validator, testcontainers-go, and automated agent workflows for repeatable test runs.

---

Status & Roadmap

BUNGKUS is under active development with no public release yet. Working today: the script parser, the breakdown engine, immutable documents, rate-card gating, and Field Mode. What remains before release is contributor documentation, a self-hosted deployment guide, and a more complete Desk Mode.

The project sits at the intersection of two pillars that usually run separately: hands-on film production experience shapes the interface, and backend engineering discipline decides how safe the production data actually is.