Stubkin: ticketing under the organiser's own name, built and not yet trading

Stubkin is our own product, not a client project, and it is not trading yet. TicketWave HQ Ltd, the company behind VerySEOly, has built it since March 2026: event ticketing that runs on the organiser’s own domain and their own Stripe account, in five languages. It was called TicketWave until October 2026. It has no organisers and no orders: sign-up is closed until launch, and stubkin.com shows a coming-soon page.

The brief: the box office, under the organiser’s own name

When an organiser sells through a ticket marketplace, the marketplace’s brand sits between them and the people who come, and the attendee list sits with the marketplace. Stubkin’s answer is in its own line on stubkin.com: it “runs on your own name and domain, so your customers stay yours”.

So the brief was a platform where an organiser sells tickets on their own pages, takes the money into their own Stripe account, and scans people in at the door, even where the signal drops.

What was built

• Event pages and checkout on the organiser’s own domain, with ticket tiers, add-ons, time slots, deposits, custom questions, pay-what-you-want and a waitlist.
• An embeddable widget and a WordPress plugin, so an organiser who already has a site sells from it.
• A door scanner that runs in the browser, keeps scanning when the venue’s connection drops, and catches up when it returns.
• Refunds and transfers under the organiser’s control, promo codes, promoter links, guest lists, and a box office for sales on the night.
• Payments in pounds or euros, chosen by each organiser, on the organiser’s own Stripe account.

The decisions, and why

The organiser’s account, not ours. Every sale is charged on the organiser’s own Stripe account, at their own Stripe rates. The organiser is paid directly and keeps the relationship with their buyers.

One product at launch. Bookings and ordering were built too. With nobody using them, each would be more to keep safe and more copy to keep true, so only events launch, and the rest is parked with its code kept.

A name and a domain of its own. The old name was shared with another software business, and the product lived on a subdomain of the company’s own site. It became Stubkin, on stubkin.com, and every address on the old one now redirects there.

Pounds or euros. A UK company that cannot sell a ticket in pounds cannot launch in the UK, so each organiser picks the currency they sell in.

Say where it stands. The site says “coming soon”, sign-up is closed until launch, and nothing is claimed about organisers or sales.

Why it is here, and what it does not claim

It shows engineering most websites never need: payments on someone else’s account, many domains on one platform, five languages and a door app that works offline. When a client sells tickets, our checklist for choosing a ticketing system is how we judge the options. Stubkin shows no result, because there is none yet, and VerySEOly does not sell it: we connect the system the client chooses.