Private Screener Portal Development for US Film Distributors

Relevant delivery: Inspire Film's streaming platform in Spain

The published Inspire Film case covers a React and TypeScript application on Supabase and PostgreSQL. Bunny Stream provides adaptive film and course playback with captions. LiveKit supports live screenings and events, alongside memberships, Stripe checkout and administration. Guided experiences continue after a film, with recommendations based on a short questionnaire. This demonstrates a connected streaming product. Distributor invitations, territory-specific access, expiring screener links and rights negotiations are separate scope decisions; they are not presented as features delivered in that case.

• Read the Inspire Film streaming case

Separate the public title catalogue from the private screener

Decide which title description, artwork, trailer and contact information can be public. Keep the full screener's destination and access records in the private viewing workflow. A buyer should understand which title they are requesting without an invitation accidentally making the film publicly available. Review the catalogue, an approved invitation and the destination reached by an unauthenticated visitor as different acceptance examples. If the portal also needs public promotional pages, agree their editorial owner and stable destinations independently from the private playback route.

• Scope public pages and the private application boundary

Treat an invitation and active viewing access as different records

An invitation identifies a proposed viewer; a viewing grant determines what that account can currently open. Agree the title or edition, the permitted period, the staff owner and the withdrawal rule for that grant. Review a forwarded invitation, a saved playback URL after expiry and a buyer who is permitted to view one title but not another. Define how an already-open session behaves when access changes, including which behavior the media provider can support. The interface and the access checks need to follow the same approved policy.

• SaaS account roles and access workflows

Keep the approved edition clear when media changes

Name the person who approves a replacement file, captions or artwork. Decide whether an existing buyer should keep the earlier edition, receive the new one or wait for a renewed grant. Give staff an explicit reference for the asset shared with a buyer and the version discussed in an enquiry. Start with one title that changes during review rather than assuming every replacement can reuse the earlier link. This is an operating decision for the new distributor portal, not a historical claim about Inspire Film's asset replacement process.

Carry viewing context into a rights enquiry

Agree which information the sales team needs: title, viewed edition where relevant, buyer contact, stated territory and the proposed use or window. Route that enquiry to the named owner or an agreed existing system. Keep a commercial enquiry separate from granting viewing access or accepting a licensing agreement. A CRM integration, online rights checkout or automated contract flow needs its own assessment. Review an enquiry from a buyer whose viewing period has ended, so the sales handoff remains understandable without silently extending access.

• Full stack product and integration scope

Choose playback and protection requirements before scaling the catalogue

Bring the approved video and caption assets, the devices buyers use and any content-protection requirements to the first review. Agree playback recovery, caption selection and the information staff can use to investigate an unavailable screener. Watermarking, download controls or DRM require a specific provider and implementation assessment; membership access by itself does not establish those protections. Compare a small invitation-and-viewing release with a larger portal before adding every title or sales-system integration. Use acceptance evidence from the agreed workflow rather than a promise about leakage prevention or deal conversion.

Accept one title from buyer invitation through rights enquiry

For a new engagement, bring one approved film edition, two sample buyer roles, the viewing-window policy and the person receiving rights enquiries. Proposed acceptance examples: an approved buyer reaches the intended edition; an expired or withdrawn grant follows the agreed access rule even from a saved URL; a replaced asset has an explicit edition policy; and a rights enquiry retains the title and stated territory without creating a new viewing grant. Review captions and interrupted playback on the named devices. These are proposed distributor-portal checks, not claims about Inspire Film's historical buyer invitations, rights transactions or protection guarantees.

Work with a US company and an Ankara-led engineering team

Curiosive LLC is a US company, with engineering led from Ankara, Türkiye. Monthly AI-accelerated development starts from $2,000, with scope, capacity and release responsibilities confirmed in writing. Bring one approved title, the buyer and staff roles, the access policy and the existing sales handoff. Agree US working-hour overlap and a bounded first release. Streaming services, licensed media responsibilities and any continuing operations are specified separately so the engineering scope is reviewable.

• US company and delivery arrangements
• Commercial engagement terms