Fundit.
Schema-driven application and decision platform for regional film funds. Two portals, full audit trail, Apache 2.0. In production at Film i Väst for over a year.
Live · Demo open
A regional film fund handles roughly the same set of processes as a small public agency — applications, assessments, decisions, contracts, tranched payments with conditions, final reports — but with specialised role types (producer, director, script consultant, distribution adviser) and an accounting regulation that has to live fifteen years back in time.
Industry practice is still Word templates emailed back and forth, Excel for the decision matrix and payment tranches, Public 360 or similar for the document archive. No link between them. Industry-specific systems exist — but almost all of them send data to the vendor's cloud, which doesn't fit a regional authority subject to public-access law.
Fundit is an open platform that handles the entire application life cycle — from the producer's first application to final report and archiving — with all data on the fund's own infrastructure. Two separate portals coordinating through the same backend.
What it does
- Client portal for producers — eight project types, document upload, organisation profile, milestone and tranche tracking, statistics dashboards.
- Administration portal — incoming-application queue, assessment workflow, decisions, contracts, tranched payments, the full project life cycle (status 1–22).
- Schema-driven workflow — business logic lives in schema definitions, not code. New project types are a configuration change, not a deploy.
- 17 roles — caseworkers, script consultants, distribution consultants, legal. Limits and thresholds (spend limits, geography requirements, veto rights).
- Self-hosted AI — ollama-daol behind Cloudflare Access. AI features work without sending scripts or budgets to third parties.
- Public360 integration for the document archive. Full audit trail. Soft-delete only. Seven-year archiving per accounting law.
- Two separate portals — not one system with two views. Two Blazor apps consume the same API, each with its own security model and UI.
- TOTP MFA on every account — credentials, QR code and recovery codes are in the howto guide.
What sets it apart
Apache 2.0. No cloud dependencies for business logic. Self-hosted LLM via ollama-daol behind Cloudflare Access — AI features work without sending scripts or budgets to third parties. Production-validated: in use at Film i Väst for over a year. Not a demo project — a system in daily use by a regional fund with real budgets and deadlines.
The data never leaves the customer's infrastructure. Auditable in earnest.