For wedding & event photographers

Deliver the wedding.
Then deliver it to everyone who was there.

A private gallery your client picks from, and one printed card that gets every guest at the venue their own photos.

Free plan, no card. Every feature on every plan — only storage differs.

Aisha & Rohan — Reception

Private link · selection open

4 of 40 picked

“The third one — can we crop it tighter?”

What your client opens

A link, on their phone, that looks like your work

No logo of ours across the top, no account to make, no app to install. Your name, your watermark, and the frames.

The proofing loop

One link, from the card reader to the signed-off album

Your client opens a link, picks their frames, and leaves a note. No account, no app.

A gallery per function

Haldi, Mehendi, Sangeet, Reception — one gallery each, all under one event.

Upload the card

Previews are built on upload. Your original is stored untouched.

Send a private link

No account for your client. The link is all they need, and it opens on a phone.

They pick, against a quota

Favourites, picks and a comment per photo. You watch the count live.

You release the downloads

Full-resolution files stay locked until you release them.

Venue wifi is not your problem

The gallery installs as an app on your client's phone. Picks made with no signal are queued and replayed when it returns.

Between the card reader and the link

A wedding does not arrive as four folders. It arrives as one dump, stamped with the minute you copied it — so upload time cannot tell the Haldi from the Reception, and the capture times can.

Ask for five more and the number goes up on the gallery they are already looking at. Ask for fewer than they have already chosen and it is refused, with the count named — a list your client has filled is not something we will quietly shorten.

Sat 15 Aug · 11:04 am – 2:58 pm

386 frames · filed into Haldi

Sat 15 Aug · 8:02 pm – 11:47 pm

214 frames · filed into Reception

Sun 16 Aug · 7:12 am – 9:30 am

96 frames · filed into Couple shoot

No capture date

6 frames · still one tap away, never hidden

The runs your camera already recorded, offered as they came off the card
  • Runs of shooting, not dates

    Consecutive frames are one run until the camera goes quiet for two hours, so the grid offers the Haldi and the Reception separately even though both were shot on the same day and uploaded in the same batch. Frames with no capture time keep a row of their own and are never dropped.

  • Sections your client reads in order

    Show a run, tick all, file it into Haldi — one gesture. Your client's link then opens in the order the day happened. Anything you have not filed yet still shows, under a heading that reads as part of the shoot rather than as your filing system.

  • Their picks, on the wall you work on

    Filter the grid to what they selected, favourited or commented on — each one on its own, so you can see picks and notes at once. Then file that set, or change the pick limit and let them choose more.

Lightroom Classic publish plugin

Edit in Lightroom → re-publish → same photograph, new version

When your client asks to crop tighter, fix an exposure, or retouch a blemish, you don't need to export JPEGs and re-upload through a browser. Edit directly in Lightroom Classic and hit Re-publish.

The new rendition updates in place — no download, no re-upload by hand, and no duplicate row.

Every client pick, heart favourite, and note stays attached to the exact frame. Guest face-match links stay intact.

The revision loop that doesn't break your gallery

1Client requests edits with a note on the frame
2Make the adjustment in Lightroom Classic
3Click Re-publish — version updates in place
Picks, favorites, and notes preserved without duplicate rows

AI guest photo delivery

300 people were at the wedding. They all want their photos.

A guest scans the card on their table and takes one selfie. Our AI finds them across the whole shoot and sends a private link to only the photos they appear in — then messages them again as more arrive.

The selfie itself is never stored. It is matched and thrown away in the same request, and everything about that guest is erased when the gallery expires.

Photos from tonight

Scan, one selfie, and we'll send you the photos you're in

Print once. Works at every wedding you shoot.

One card, reused — pointed at whichever function is running
  1. 1Scan the card

    No app, no account, no password. The card on the table is the whole thing.

  2. 2One selfie

    Embedded and thrown away in the same request. The photo itself is never stored.

  3. 3Their own link

    Only the photos they appear in — and a message when more arrive.

  4. 4Next year's wedding, from this year's guest

    One question after they download: is anyone in the family getting married? An answer with intent becomes a lead in your own queue. Three hundred people were at the wedding — the ones planning their own tell you so.

We never market to your guests, and never sell the introduction back to you. The lead is yours.

One card for your whole studio — printed once

Not a fresh standee per wedding. Print it once and point it at whatever you are shooting. Occasions carry a date and a time, so a guest scanning at the Haldi lands on the Haldi, and one scanning that evening lands on the Reception.

  • Only what you are shooting right now is reachable. Never your back catalogue.
  • Pin a card to one client or one occasion, or leave it open to whatever is running.
  • Print one per standee or table card. Each is pointed and revoked on its own.
  • Card goes missing? Revoke it and print another. Guests who already registered keep their photos.
  • Functions that overlap? Set the card to always ask, and the guest picks.

Haldi

11:00 am

Reception

7:00 pm

Guests land here

Post-wedding shoot

Tomorrow

A guest at more than one function can say so and be found across all of them — still one selfie, one link. Pick a single function and only its photos are searched.

What we do with the photos

The uncomfortable questions, answered in the code

Face matching at a wedding is only acceptable if the promises around it are real. These are enforced in code, not on a policy page.

The original is never modified

Byte-for-byte what came off the card, EXIF intact. Nothing we do writes to it.

Previews carry no metadata

EXIF, GPS and every other tag are stripped from previews. Photos still come out upright.

Watermarks survive a right-click

Burned into the pixels, not laid on top. Saving the image saves the watermark.

A guest's selfie is not kept

It becomes a signature and is thrown away in the same moment — the photo never reaches storage.

Downloads open only when you say so

Before you release, your client sees watermarked proofs only. Released by mistake? Lock it again and the full-resolution link stops working — including one they had already saved.

Guest delivery stays off until the couple turns it on. Matching is tuned for precision over recall: a missed guest sees “nothing yet”, which is recoverable. Sending someone a stranger's photos is not.

T&C

Pricing

Pay for storage. Nothing else is metered.

Every feature is on every plan, including Free. Only storage changes.

Studio 500 GB500 GB

₹899 / month

Studio 1 TB1 TB

₹1,499 / month

Studio 2 TB2 TB

₹2,999 / month

Custom3–50 TB

from ₹4,399 / month

Free3 GB

₹0

Pro100 GB

₹499 / month

Bigger than 2 TB?

Above the largest fixed plan, storage is priced by the terabyte on a graduated scale — the rate falls as the archive grows. Annual prepay is charged for ten months, not twelve.

Your next wedding can deliver itself

Create a gallery, upload a card, and send the link. Add the printed code when you are ready for the guests.