What's coming roadmap

What pod is building next, written up while it's still being built, so you can plan around it, argue with it, and tell us what's wrong while changing it is still cheap.

Nothing on this page is live yet. Everything here is in the workshop, no dates are promised, and if a page describes something you can't find in your studio, this is where it will be. When a feature ships it moves out of Roadmap and into the rest of the docs.

Most product docs appear the week a feature launches. We publish this section early on purpose. The studios using pod are running real client work on it, and a change to how their team and their customers see that work is not something to spring on them. It's something to show them a draft of. Read it, and if it doesn't match how your studio actually operates, say so: feedback inside the studio, or thebrainpuddle@gmail.com.

Shipped since this page was written: studio seats, projects & the publish gate

The big one has landed. One licence is now a studio with named seats for your crew and separate seats for your customers, client engagements are projects, and a publish gate decides which cuts reach a client, with an append-only record of every approval underneath it. It moved out of this section and into working with clients, seven pages, meant to be read in order.

Studio seats & roles One licence is one studio: seat pools, invite-only signup, and who can see what. Projects & client access A project is one client engagement, and the whole of a client's visibility. The publish gate Submit, queue, publish or reject: how a cut reaches a customer. Rework & the notes loop The no-password link a client taps, their answers, and the round trip back.

Still in the workshop

A customer pointing at a shot by name

Your client can already pause on a moment and leave a note there, and it lands on the right shot on your side. What they can't do is file a typed request against a named shot the way your own crew does, choosing between "re-shoot it", "change the look" and "just noting it". The board is built to take it; the client's half of it isn't built. See rework & the notes loop.

The hands-off modes

This one isn't new, it's a return. Assisted steer (AI critics pre-check every image and clip before it reaches you) and autopilot (pod self-QCs the whole shoot, stopping only at the cost gate) are benched while we make them worthy of real productions. They have their own page already, since they once shipped: the three ways to work. Until they return, every film runs in full control and typing auto at a gate politely declines.

What none of it changes

Worth saying, because it's the question every studio owner asks second:

Your films still live on your computer. The pipeline doesn't move to a server. You produce exactly the way you do now: the studio, the gates, the cost gate, the episodes folder. Sharing an episode is a deliberate push, never a background sync. See privacy & your files.
Nothing is surfaced by accident. A client sees a cut because somebody submitted it and somebody published it. There is no state in the system where work leaks to a customer because a box defaulted to checked.
The production gates stay yours. The gates (script, casting, keyframes, clips, cost) are between you and pod. The publish gate is a different animal: it sits between your studio and your customer, after the film is made.
Pod does not talk to your clients. There is no email anywhere in this and no notifications. When a cut is ready, pod hands you a link your customer can tap without a password, and a person on your side still decides who gets it and when. The relationship stays yours; only the friction leaves.

← A studio, end to end Updating Pod →