We made the studio we wanted to write in.
CineNote is built by people who shipped scripts to set and watched the seams between four disconnected tools cost real days. The studio exists to remove those seams.
Four tools, four versions of the truth.
A screenwriter opens one app for the script. The director opens another for the moodboard. The gaffer opens a third for the rig. The coordinator opens a fourth to track who has what.
Four tools, four exports, four versions of the truth — and the film lives in the seams between them. Every hand-off is a chance to lose a revision, a reference, or a day.
We couldn't find one room that held all of it. So we built it.
Idea to shooting script — together.
What we hold to.
The format on screen matches the format in production. Slug line, scene number, shooting script, lock — the real vocabulary, nothing softened for a different industry.
A beat becomes a scene; the scene keeps its references; the shot ties to a fixture. One source of truth, from the first idea to the locked page.
Six roles and 23 permissions, enforced at the gateway, the service, and the row. The studio is as careful with access as the production is.
No AI gimmicks on the page, no motion for decoration. Animation communicates hierarchy and nothing else.
What's under the hood.
- 4
- Connected studios
- 6
- Production roles
- 23
- Granular permissions
- SHA-256
- Content-addressed scripts
Three studios. One workspace.
A paginated editor that exports print-grade PDF, Final Draft FDX, Fountain, and DOCX.
An infinite canvas with twenty-three film-native widget types, linked to the script.
Fixture-aware lighting plans with circuits, power loads, and a share link the gaffer can read.
The home that holds them — roles, invites, audit, and a full activity trail.
Engineered like the deliverable matters.
CineNote runs as a set of focused services behind a single gateway — scriptwriting, workboard, lighting, and workspace, each a bounded context speaking gRPC, with REST only at the edge.
Scripts are content-addressed and deduped by SHA-256, so every revision is recoverable and nothing is stored twice. Sessions are HTTP-only cookies; permissions resolve at three layers, not just in the UI.
It runs on Google Cloud (asia-south1), with PostgreSQL for state and object storage for assets — built to be defended in a deal memo.
Open the studio.
The first script is the only commitment.
Questions, press, or partnership? hello@cinenote.global