SMSocial JinniOpen Our Live Concerts
Events · built in

Our Live Concerts
A ticket, one device, one event — and no way to rip it.

Our Live Concerts is a live-streamed music concert with a paid ticket, running on your own server. You schedule the show and its ticket types, sell tickets, and each ticket carries a single-use code that admits one device, only during the event's date and time. The ticket's serial number and its code are private — the serial is visible only to you as the owner — and the stream is delivered through your own media server, which refuses anyone without a valid ticket. It is the shape of a big ticketing site, kept in your own database, with the anti-piracy rules built in rather than bolted on.

A ticket is a credential, not a link. Admission is a server-side exchange: the holder types their code, your server checks that they hold the ticket, that the doors are open and that this is the device the ticket is bound to, and only then does it let the stream through. The code never has to reach a browser and there is no shareable stream URL, so a screenshot or a copied link is worthless. One device, once: the first entry binds the ticket to a device, and a second device voids the ticket and suspends that account from the event, no refund — while a dropped connection on the same device is allowed back in, so a lost Wi-Fi never burns a ticket. The media server asks your app on every single read, which is where stream-ripper software is recognised and refused. What this app deliberately does not claim is that screen-recording is impossible: no web software short of DRM can stop someone filming their own screen, so the promise is exact — every fetch-based download is blocked and attributed, ripping is made futile, and recording is deterred by a per-viewer watermark and the terms you accept at purchase.

Open Our Live ConcertsSee how it works

Step by step

How to run your first ticketed concert

Every step is the real one in your own install. A concert, its tickets and every admission are rows in your own database.

  1. STEP 01

    Open Our Live Concerts

    From your workspace, open Our Live Concerts. It shows the concerts on your install and the form to schedule one.

  2. STEP 02

    Schedule a concert

    Give the concert a title, a venue, and its doors, start and end times. Add one or more ticket types with a price and a quantity.

  3. STEP 03

    Go on sale

    Publish the concert and its tickets go on sale. Inventory is held atomically, so two buyers racing for the last seat cannot both get it.

  4. STEP 04

    Sell tickets

    Each purchase issues one ticket per seat, each with its own code shown once to the buyer, and its own serial number kept for you.

  5. STEP 05

    Go live and admit

    Start the broadcast to get the room path and the publish key for your encoder. On the night, ticket-holders enter with their code; the media server admits only one device per ticket, only while the doors are open.

What it does

A ticket, a device, and a window — enforced

  • A single-use code per ticket

    Each ticket has its own code. Only one code per ticket may ever enter the live stream, and the code is stored only as a hash, so even a copy of your database cannot be used to forge an entry.

  • The serial number is yours alone

    Every ticket also has a serial number for your records. It is encrypted and visible only in the admin console — never to the buyer, never in a page, and never derived from the code.

  • One device, once

    The first entry binds the ticket to that device. A second device voids the ticket and suspends the account from the event. The same device reconnecting — after a dropped signal — is let straight back in.

  • Valid only for the event's date and time

    A code is refused before the doors open and after the show ends. Outside the window there is nothing to watch and no way in.

  • No downloads

    The stream is delivered through your own media server, which asks your app before every read — so a leaked URL admits nobody, and stream-ripper software like yt-dlp, ffmpeg and Streamlink is recognised and blocked.

  • Terms the buyer actually accepts

    Before buying, a customer accepts the single-use, single-device, single-event terms. The exact version they agreed to, with the time and address, is recorded — so a term is enforceable rather than merely displayed.

Questions

Questions people ask

Straight answers, and where something is not built yet it says so.

What is Our Live Concerts?
Our Live Concerts is a live-streamed music concert with a paid ticket that runs on your own server. You schedule the show and its ticket types, sell tickets that each carry a single-use code, and admit one device per ticket during the event — all stored in your own database and streamed through your own media server.
How does a ticket code work?
Each ticket has its own code. The buyer types it to enter, and the server checks that they hold the ticket, that the doors are open and that this is the ticket's bound device before letting the stream through. The code is stored only as a hash, never in the clear, and it never has to reach a browser — so a screenshot or a shared link is worthless.
Can I see a ticket's serial number?
Yes — you, as the owner, can see the serial number for any ticket, and nothing else. The buyer never sees it, and it is encrypted at rest with your installation key, so a copy of the database without the key reveals nothing. The serial is deliberately unrelated to the code, because a secret derived from a guessable number would be guessable.
What happens if a ticket is used on a second device?
The first entry binds the ticket to that device. A later entry from a different device voids the ticket and suspends that account from the event, with no refund. Reconnecting on the same device — for example after a dropped connection — is allowed, so a lost signal never burns a ticket.
How long is a ticket valid?
Only for the exact date and time of the event. A code is refused before the doors open and after the show ends, so there is nothing to watch and no way in outside the window.
Can a viewer download the stream?
No. The stream is delivered through your own media server, which asks your app before every read, so a leaked stream URL admits nobody and stream-ripper software such as yt-dlp, ffmpeg and Streamlink is recognised and refused. What no web software can stop is someone recording their own screen with a camera or capture card — that is why every view is watermarked and the terms the buyer accepts cover it. The honest promise is that every fetch-based download is blocked and attributed, and ripping is made futile.
Does it take payments?
Not yet. This release issues and admits tickets and records the terms a buyer accepts; a live payment provider is the next slice, and it is built to a seam so your own gateway can be plugged in without changing the ticketing.

Our Live Concerts is ready on your install

It is part of Social Jinni and it runs on your own server — nothing to register, nothing to approve.

Open Our Live ConcertsSee all apps