Client delivery
Client Gallery & Portal Software for Photographers
Deliver a branded client gallery for proofing, downloads, and approvals on the same platform as your portfolio and site.
Client Portal
Invite clients into a branded room on your domain. They select and submit; your studio queue, downloads, courses, and print shortlists stay in the same portal story.
Portal
Delivery your clients actually follow.
Replace link chains and inboxes with structured rooms, clear access rules, and visibility your ops team can invoice against, including a sensible handoff after someone registers for a workshop or session.
Branded portals
Clients land in a room that matches your studio before they ever see finals. Trust starts the moment they open the link.
Events & post-registration
Workshop and session signups can feed the same portal access story as galleries and downloads. Paid flows tie purchases to registrations so attendees know where to go after checkout.
Proofing & selects
Favorites and review flows aligned with how people already behave on consumer gallery tools. Turn opinions into decisions without endless email threads.
Policy-backed finals
Access codes, expirations, and download vs. preview rules you can stand behind in a contract. Protect your work while still feeling generous to good clients.
Engagement visibility
Signals for viewed, favorited, or downloaded work, less guesswork before you invoice. Close the loop without chasing confirmations.
Print handoff
When wall art matters, fulfillment paths stay attached to the same delivery story. Production stays legible from client yes to lab ship.
Before a connected platform
- WeTransfer links and endless email threads for feedback
- No tracking on whether finals were seen or downloaded
- Manual zip exports and “which version is final?” confusion
After you standardize here
- Structured proofing in a branded room clients recognize
- Access control, expirations, and download rules you can defend in a contract
- Versioned, policy-backed delivery with visibility for your ops team
Built for client rooms
Cloudflare R2
Private storage
Client masters off the public CDN with signed downloads
Stripe Connect
Checkout & entitlements
Purchases and workshops unlock the same branded portal
Private masters stay in Cloudflare R2 with signed access; Stripe Connect ties purchases and workshops to portal entitlements; Resend delivers access codes and invites.
Swipe sideways for more
Delivery systems clients can follow
Workflows take a job from invite to finals. Clusters hold portal, proofing, and fulfillment depth.
Invite with control
Issue access codes, set expirations, and scope what can be downloaded vs. previewed.
Proof in context
Favorites and review flows align with how clients already behave on consumer gallery tools, without losing your brand.
Deliver finals
Grant finals and downloads in the same room. Private portfolios stay off the public CDN and use signed access after invite, with policy controls you can stand behind.
Close the loop
Visibility into viewed or downloaded assets reduces back-and-forth and speeds invoicing.
A client room that feels like your studio.
- Branded presentation
- Tuned to creative studios and how clients actually review work.
- Secure access
- Patterns suited to high-value deliverables.
- Private portfolio bind
- Gallery widgets keep files off the public CDN with signed access after invite.
- Event entitlements
- Registration can land clients in your portal room after checkout.
- Internal vs client
- Clear separation between studio tools and client-visible surfaces.
Marketing emails
The gallery did its job, then it went quiet. Email keeps the relationship going.
Studio
Now
Booking the next session.
See the dates.
The pictures are delivered
Now you have a reason to stay in touch, and a place to send them. The message that opened the gallery is a different send.
Only people who opted in
Not everyone you delivered to, just those who asked to keep hearing from you.
What you can see afterward
The campaign shows how many went out and how many bounced. The subscriber list shows who asked to stop.
Continuity across the business
The difference isn't one feature. It's what happens when publishing, commerce, media, and delivery stop behaving like separate products or plugins.
Delivery is a chain of links and inboxes
it becomes workflows clients can actually follow
Feedback lives in email chaos
proofing lives in structured, branded context
You guess whether finals were seen
engagement becomes something you can see and invoice against
Delivery is a chain of links and inboxes
it becomes workflows clients can actually follow
Feedback lives in email chaos
proofing lives in structured, branded context
You guess whether finals were seen
engagement becomes something you can see and invoice against
Ready when you are
Compare plans, then bring this surface online with the rest of your creative operating system.






