A short list,on purpose.
There is no logo wall on this page, because we would have to invent it. What follows is everything Studioshare actually talks to, plus a longer list of the things it does not — so you can find out now rather than halfway through wiring it into a workflow.
Windows desktop app and Android. macOS and iOS in development.
The camera pushes. We do not reach into it.
The capture app opens a transfer session bound to one event and shows you an address, a port and a generated username and password. You type those into the network-transfer menu the camera already has, fire a test shot, and frames start landing. The connection is the camera sending files to the machine — there is no vendor SDK in Studioshare, no USB tethering protocol, and nothing installed on the camera.
Which means the honest compatibility statement is not a list of four brands. It is: any camera that can transfer files over a network to an address you give it. If yours can, it works. If it cannot, no amount of logos on this page would have changed that.
A previous version of this page named Canon, Nikon, Sony and Fujifilm as integrations. They are not. Those names appear in Studioshare in exactly one place — a table of RAW file extensions — and recognising a file extension is not a partnership. Camera make and model detection is also not wired up yet, so do not plan on filtering a shoot by body.
Tethered camera capture
Connect the camera to the Studioshare desktop app and frames sync as you shoot. No card swaps, no import step at the end of the night.
QR + selfie guest access
Guests scan a QR code at the event, take one selfie, and get the photos they appear in. No app install, no account, no waiting for a link.
Tethered capture is the one part of Studioshare that needs a desktop install, and that desktop is Windows today.
Google Cloud, in specific pieces
“Hosted on Google Cloud” is not an integration, it is an address. Here is what is actually used, so the sentence means something.
| Firebase Auth | Sign-in for photographers and guests. Phone OTP, Google and Apple. There is no email-and-password option, by design. |
|---|---|
| Cloud Firestore | Studios, events, media records — and the face vectors. The match itself is a Firestore nearest-neighbour query, not a separate vector database. |
| Realtime Database | Holds which frames belong together, so a burst of nine shots resolves to one card in a gallery. |
| Firebase Storage | Where the photographs and studio brand assets live, served over Google’s storage hosts. |
| Remote Config | Lets us change starting credit allowances and validity windows without shipping a release. |
| Cloud Run | The web app runs on Firebase App Hosting, and the face service is a second, private Cloud Run service alongside it. |
Our own, not a third party’s
- A private Cloud Run service, deployed with no unauthenticated access.
- Runs the AuraFace ONNX pipeline and returns a 512-dimension, L2-normalised embedding.
- Called only from our backend, with a short-lived identity token minted per request.
- Never called from a browser, and never reachable from one.
No face API vendor
Studioshare does not send guest faces to AWS Rekognition, Google Vision, Azure Face or any commercial recognition API. The model runs in a service we operate. That is a smaller supply chain, not a bigger one — and it is the reason we can tell you precisely where a face vector goes.
Two vendors, one job each
Razorpay
Checkout runs in the billing screen and the payment is an order in rupees. When Razorpay confirms it, a signed webhook lands on our side, the signature is verified, and the credits are added to your studio.
Worth being precise about: these are one-time orders, not a recurring card mandate. Nothing auto-renews, and there is no subscription to cancel — you buy credits with a validity window and buy again when you want more.
Sanity
Our blog is written in Sanity and published straight into this site. Publishing a post triggers a revalidation of the affected pages rather than a rebuild of the whole site.
It touches the marketing site only. No studio, event, guest or photo data goes anywhere near it, and there is nothing for you to configure.
Two stores, one browser
The apps are distributed through the stores your machines already trust. Your clients and your guests install nothing at all.
Microsoft Store
The Windows desktop app, which is the machine that runs tethered capture at the event.
Google Play
The Android app, published by DFEVERX LLP. Live today for photographers and guests alike.
The browser
Guest galleries and client selection run in whatever browser is already open on the phone. Nothing to download, nothing to sign up for.
Windows desktop app and Android. macOS and iOS in development.
What Studioshare does not connect to
The previous version of this page advertised several of these, including three API endpoints that do not exist. If one of them is why you are here, this is the section that saves you a fortnight.
- Not supported: No public developer API, no API keys, no OAuth for third-party apps, no outbound webhooks.
- Not supported: No Zapier, Make, n8n or any automation-platform connector.
- Not supported: No Lightroom or Capture One plugin, and no watch-folder import.
- Not supported: No Dropbox, Google Drive, OneDrive or S3 sync.
- Not supported: No embeddable gallery, no iframe widget, no custom domain and no white-label build.
- Not supported: No CRM, email-marketing or WhatsApp Business API connection.
- Not supported: No Stripe, PayPal or any payment provider other than Razorpay.
- Not supported: No analytics or advertising pixel, and no third-party error-monitoring service.
- Not supported: No calendar, invoicing or accounting integration.
We are not going to list these as “coming soon” either. Nobody is building them right now, and a roadmap you invent to close a deal is a promise you have already broken.
Tell us what you actually need it to talk to.
If there is a piece of your workflow this list does not cover, say so. We would rather know what is missing than guess at a connector nobody asked for.