Built not to break.
Your on-sale is the worst possible moment for a ticketing site to go down. Jump runs on Erlang and Elixir, technology first built for telephone switches that weren't allowed to fail. Here's what that means for your box office.
-
Checkout
-
Email sends Running Crashed Restarted · 4 ms
-
Check-in
-
Payouts
99.99% uptime since July 2026
That's since we moved Jump onto our own server cluster. We don't ask you to take our word for it: every incident, however small, is on our public status page.
One server can fail. Your sales won't.
-
More than one of everything
Every part of Jump runs on multiple independent servers. If one goes down, the rest keep selling.
-
No maintenance windows
We update one server at a time, and each has to pass a health check before it takes buyers again. You'll never see a "back soon" page.
-
Traffic goes only where it's healthy
A load balancer checks every server around the clock and sends buyers only to the ones that answer.
-
Nothing gets dropped
Emails, payouts and reports run as queued jobs that retry automatically, so a hiccup doesn't swallow your email blast.
Your money and your buyers' data, handled with care.
-
Card numbers never touch Jump
Buyers type card details into fields hosted by Stripe and PayPal. We never see or store a card number.
-
Every action checked against the record it touches
Jump doesn't stop at "is this person an admin?" Each change is checked against the specific event, order or customer, so one account can never reach into another's.
-
Your team, your rules
Give staff exactly the access they need. Door staff can check people in without seeing your payouts.
-
A record of who changed what
Refunds, check-ins, attendee changes and permission grants go into an append-only audit log with the before and after.
-
No front door to knock on
Our servers have no open public ports. Traffic reaches them only through encrypted Cloudflare tunnels.
-
Passwordless sign-in
Sign in with a one-time link sent to your email, so there's no password to steal or reuse. If you set a password anyway, it's stored hashed with bcrypt.
Why we built Jump on Elixir and Erlang.
Most ticketing sites are built on the same few stacks. We chose one with nearly 40 years of keeping things running.
-
Born in phone exchanges
Ericsson created Erlang in the 1980s to run telephone switches, where downtime wasn't an option. The same runtime later carried WhatsApp's messages and now runs Discord's chat.
-
Crashes stay small
Jump runs as thousands of tiny, isolated processes. When one fails, its supervisor restarts it in milliseconds. A bad request fails on its own; it doesn't take checkout down with it.
-
Less to run, less to break
Background jobs, live updates and our server cluster all run inside one runtime, next to Postgres. There are no extra queue servers, caches or microservices to keep alive. Fewer moving parts means fewer 3am surprises.
-
Live by default
The Jump admin is built with Phoenix LiveView. Pages stay connected to the server, so changes appear without a reload.
Erlang and Elixir also run systems at
- Ericsson
- Discord
- PepsiCo
- Heroku
- Klarna
How we build it.
- automated tests
- 17,000+
- written architecture decisions
- 50+
- compiler warnings allowed
- 0
- change through CI
- Every
- Every change runs the full test suite before it can deploy.
- The compiler enforces boundaries between parts of the system, so payments code can't quietly reach into marketing code.
- Big decisions are written down with their reasoning, so it outlasts the conversation they came from.
- Some shortcuts are tracked by "ratchet" tests that only let the count go down. Once a shortcut is fixed, it can't come back.
- Elixir 1.20
- Erlang/OTP 28
- Phoenix 1.8
- LiveView 1.2
- PostgreSQL + TimescaleDB
- Oban
Here for the Erlang?
Then you'd probably like it here. Jump is a large Elixir app with event sourcing on Commanded, a distributed cluster, LiveView throughout, and a connector that lets organizers run their box office from Claude and ChatGPT.
We're looking for Product Engineers: people who want to talk to the venue, design the feature and ship it end to end, not just close tickets.
Your next on-sale, in safe hands.
Every feature included. Service fees only.