Live inventory
Find your vibe
Ten categories, each one a real page a search engine can land on — not a filter on this one. The count beside each is how many are on sale in it right now, which is why some of them are dim.
For organizers
Build it, price it, put it on sale, find the room, run the door, and read the ledger in the morning. Everything below this line is how that actually works — and it is below this line because the person deciding where to go on Saturday does not need it.
Eight steps, one record. Every one of them writes a row, which is why a number on a GREENWAY dashboard can always be traced back to a transaction.
The platform
Not eight products with an integration between them. One record moves through all of it, which is why a figure on a dashboard can be traced back to the transaction that produced it — and why turning on a new lane, like taking the money at the door, changes one setting rather than one department.
Card, wallet, the box office and future rails behind one interface. The processor is a detail, not the architecture.
Inventory, holds, allotments and signed tickets that cannot be minted without a confirmed payment.
Build it, price it, put it on sale, run the door — the same record end to end.
Six fields and a price with nothing hidden in it. Mobile first, because the queue is outside.
A signed QR, a short code for dead phones, an email that works with no signal, and a page that opens on one bar of it.
Every event gets a command centre and, on the night, a live mode built for a dark room.
Who buys, what converts, who returns — each answer traced to the rows it came from.
Slots, packages, fulfilment and a sponsor report that refuses to invent reach.
Emerald is money moving. Bronze is the platform working something out. The eight drawings are generated by site/marks.mjs from one isometric projection, so they are lit by the same light.
The revenue engine
Every order separates the face value, the processing cost, the platform fee, the tax and the organizer's net. The organizer sees it. The buyer sees it. The ledger balances to zero or the write is refused.
The breakdown beside this text is not a mock-up: it is fees.quote() run on a $100.00 ticket with the default schedule, rendered as it comes back. Change the schedule and this page changes with it.
Read the fee model| Ticket sale | $100.00 |
| Greenway platform fee | $3.99 |
| Customer pays | $103.99 |
| Card processing (estimated) | -$3.32 |
| Organizer net | $96.68 |
Every way to sell it
The same inventory, the same price, the same ledger, reached five different ways. A ticket sold at the door and a ticket sold by an agent at three in the morning arrive in the same place and are counted once.
Poster, door time, age policy and a checkout that shows the whole price before it asks for a name.
GREENWAY
/e/your-event
The handle the organizer chose, short enough to print on a flyer or say into a microphone.
/your-night
One tag. The same checkout, inside your page, on your domain — the traffic never leaves.
<script src="/embed.js">
Cash or card taken on the night, recorded by the person who took it, settled against the same event.
box office
A buying agent works to a bounded mandate and a human approval step. Nothing is spent outside the mandate.
/agent/mcp
The door
A ticket is a signed message about a specific event. Edit it and the scanner rejects it; present it twice and the second reader is told exactly when the first one was let in.
The QR code above was generated by this page. The encoder is ours — no third-party script sits between a venue and its own door.
The integrity rule
Most platforms demo beautifully because the numbers are invented. GREENWAY cannot render a figure that has no source — the component throws. Before you have sold anything, this is honestly what you see.
Each of those reads its own reason. The moment a real order lands, the same tiles fill in — and hovering one tells you which rows produced it. The live strip at the top of this page obeys the same rule: a cell it cannot count is a cell it does not draw.
Merchants, events, tickets, customers and ledger entries are all tenant-scoped, and the store filters on the tenant as well as the API. GREENWAY was never a single-event application that had organizations added later.
Stripe is today's implementation of one interface. Checkout, refunds and reporting speak to the interface, so a second processor, ACH or a future rail is a new file — not a rewrite. No card data ever touches GREENWAY.
Before you commit
Two of these answers are not flattering. They are on the homepage anyway, because finding them out after the event is worse for both of us than reading them now.
Find something, bring your people, and get in. Or put your own night on the greenway.