About Selene
A gallery tool built by someone
who actually delivers them.
Selene exists because wedding clients deserve a delivery experience that matches the work. Most gallery platforms feel like banking dashboards in a tuxedo. We wanted something that felt the way a printed proof book feels — quiet, considered, made for the photos.
The story
Selene started as a private project. After years of delivering weddings through the big-name client-gallery tools, the same frustrations kept surfacing — buried branding, clunky favorites, slow lightboxes, payment friction, support tickets the client shouldn't have to file.
The brief was simple: build what we wished existed. A gallery viewer fast enough to flick through on a phone in a wedding car. A studio dashboard that respects the photographer's brand instead of competing with it. A client experience that ends with picks, prints, and a smile — not a help-desk email.
We're still early. New surfaces ship every day; the live progress log on the repo records every wake. If something you need is missing, it's probably in tomorrow's build.
What we care about
Four principles, every wake.
Editorial restraint
Every surface starts quiet. Type sizes earn their weight; colour earns its presence. The photos do the talking, the chrome stays out of the way.
The photographer owns the relationship
Your brand. Your domain. Your client emails. Selene is the rails — the studio in front of the client is yours. No Selene-branded watermarks, no upsell to the buyer, no surprises on the invoice.
Honest defaults, real privacy
Biometric features ship behind per-gallery opt-outs. Client emails never leave your studio. We track what we need to keep Selene running and nothing else. Account deletion is one click and means it.
Ship every day
Selene improves on a tight build cadence. The repo carries a live progress log so you can see what landed this morning. If a feature competitors charge for is missing here, it probably ships this week.
Try it on your work