The business
Studio
Pipeline, clients, contracts, invoices, payments, scheduling, galleries, finance hub.
Sign in to Studio
Better together
Five applications.
Five applications.
One chronicle.
A client's story with your studio isn't five stories — it's one arc that happens to pass through a CRM, a shoot day, a culling room, an edit bay, and a review room. Reminiscent Chronicles is built so the record follows the story, not the software.
One identity
Sign in once. Work anywhere in the family.
Your account is a platform identity, not an app login. It carries your workspace, your role, and your permissions into Studio, CallBoard, Darkroom, Cutroom, and Post-Production alike — one set of credentials, one place to manage your team, one door to lock when someone leaves.
That's more than convenience. Because access is minted centrally and enforced at the database-rules layer in every app, "remove this person" means removed — everywhere, at once, verifiably.
- One account, five apps — no per-product user directories drifting out of sync.
- Roles that travel — owner, admin, member, and bookkeeper mean the same thing family-wide.
- Central offboarding — access revocation propagates to every app on the next token refresh.
- Per-app subscriptions — identity is shared; billing is independent. Pay only for the chapters you use.
The client arc
One record, eight milestones — walk it yourself
Follow a single engagement through the family. Click a stage (or "Next act") and watch the client record travel — the same record at every step, never exported, never re-typed.
01
Studio
Inquiry
A lead form or public booking page creates Avery Lane's record in Studio's pipeline — source, interest, and conversation attached from the first hello.
02
Studio
Booking
Proposal, e-signed contract, and a Stripe deposit — the engagement is real. The same record now carries the agreement and the money path.
03
CallBoard
Production
CallBoard picks the booking up as a production: schedule blocks, the call sheet, e-signed releases, and live day-of verification — no client re-entry.
04
Darkroom
Culling
Thousands of RAW frames come home to Darkroom. Cull to the keepers, edit, and proof — the rated selects flow straight into Avery's delivery gallery, no second catalog of who booked what.
05
Cutroom
The cut
Footage lands in Cutroom inside DaVinci Resolve: silences trimmed, captions written, a rough cut assembled — then the timeline is handed to Post-Production for review on the same record.
06
Post-Production
Review
Cuts and selects land in the review room. Notes are timecoded, versions chain, and approval is recorded per reviewer — against the same client, the same project.
07
Studio
Delivery
The approved work ships through a branded gallery on Avery's record — the same portal that holds her documents and invoices.
08
Studio
Payment
The final invoice reconciles in Studio, the finance hub keeps the score, and the whole arc — hello to paid — reads back like one story. Because it is one record.
"The tools don't have to be one monolith. They have to agree about the client — that's the whole trick, and it's the one thing bolted-together stacks can't do."
One login, five doors
Your account already opens all of them
One Chronicles identity carries your workspace, role, and permissions into every app. Pick a door — the same key works.
The shoot day
CallBoard
Productions, scheduling blocks, call sheets, talent intake, day-of coordination.
Sign in to CallBoard
The photo lane
Darkroom
RAW culling and editing, proofing, and finished selects handed straight to a gallery.
Explore Darkroom
The edit bay
Cutroom
AI-assisted video editing inside DaVinci Resolve — silence removal, captions, rough-cut assembly.
Explore Cutroom
The review room
Post-Production
Review workspaces, versioned cuts, timecoded notes, approvals, screenings.
Sign in to Post-Production
The support model
One support center. Real humans. Audited sessions.
One queue for the whole family
Whether the question is about an invoice in Studio, a call sheet in CallBoard, a cull in Darkroom, a timeline in Cutroom, or a share link in Post-Production, it lands in one support center with your workspace context attached. No "please contact the other product's team."
People, with names
Tickets are answered by the team that operates the platform — the same people running productions on it. You can open a ticket in-app, from the contact page, or by simply replying to a support email.
Audited, scoped access
If support needs to look inside your workspace, the session is brokered per-request, scoped read-only, and recorded in an audit trail you can ask about. Platform staff don't hold standing keys to tenant data.
One record.
The whole story.
Every seam between your tools is a place a client detail dies. Chronicles has no seams — fourteen days free to feel the difference.