About
Built on the assumption that it is your business.
SnapEterna is a plugin, not a service. It runs on your site, stores your clients in your database and takes money through your own gateway — and every decision below follows from that one.
How it is built
Three decisions you can hold us to.
These are not values on a wall. Each one is a thing the software actually does, and each one cost something to do that way.
Your records outlive your subscription
If the licence lapses, the plugin goes read-only rather than dark. You can still open, read and export every client, booking and gallery. New enquiries still arrive.
It would have been easier to switch everything off. A studio whose card expired on a Friday should not lose Saturday’s shoot list.
The database refuses the double-booking
Not the application. Everything that consumes time writes one row to one ledger with a uniqueness rule on the seat, so two checkouts in the same second cannot both succeed.
Checking first and saving second is simpler to write and has a gap in the middle — one a card payment is slow enough to fit through.
It tells you what your server cannot do
Watermarking needs one image library; private folders need rules a particular web server honours. Rather than assume, the plugin checks and says so on screen.
Including the awkward one: on nginx, the deny rules do nothing until you add a rule yourself. It says that, in those words.
Who we are
Why a WordPress developer built this
SnapEterna is built in India by a WordPress developer who spent years making sites for other people. Photographers were the clients who kept coming back with the same list: a booking form that knew when they were free, a gallery their clients could choose from, and a way to take a deposit that did not end in a spreadsheet.
Every time, the answer was a handful of plugins that each did a quarter of the job and none of which knew about the others. The booking form did not know about the deposit. The gallery did not know whose shoot it belonged to. Something always had to be retyped, and what got retyped was always the part that mattered.
So this is that job done once, as one plugin on your own site rather than an account on somebody else’s. It is built the way you build software you will have to support yourself: your records stay yours and keep working if the licence lapses, the database refuses the double-booking rather than apologising for it afterwards, and nothing is held back for a tier above the one you bought.
Being straight about it
What Snapeterna is not.
A list of things it deliberately does not do is more useful than another list of things it does — and it saves you finding out in week three.
It does not
Do your accounts. It reports what you have booked, collected and are owed. It does not work out tax, and nothing in it is reconciled — that is still your accountant’s job.
And it will not
- Take a cut of your bookings. The money goes from your client to your gateway. We are not in the middle of it and the architecture makes that impossible, not merely promised.
- Hold your clients’ details. They are rows in your database. We never see them, which also means we cannot recover them for you — back your site up.
- Charge more as you grow. No per-seat, per-booking or per-gigabyte pricing. The flat price is the whole offer.
- Email your clients behind your back. Every automation starts switched off, sends at most once, and keeps a log of what went — including what it chose not to send.
Still deciding
Ask us the awkward question.
If there is a thing your studio does that none of this covers, that is the useful thing to tell us.