Wake League: one park's platform, made into a product

We built a platform for one cable park, then made it a product any park can run: its own install, its own brand, and a league that ranks riders across parks. Four days, and the first park's site did not change.

Wake League is our platform for cable wakeboard parks. It covers bookings, prepaid credit, membership cards, the desk, the office, and a league that ranks riders across parks.

It began as one client's software. We built it for Como Lake Cable, where it has run the park since 18 September 2026, and that project has its own case study. At the end of October we made it a product that any park can run.

Como Lake Cable is still the only park on it. This article covers what it took to make a second park possible.

Product
Wake LeagueMont3's own, for cable wakeboard parks.
Live
Since October 2026At wakeleague.it, with one park in the league today.
Built
27 to 30 October 2026Four days, on a platform already in daily use.
The Wake League home page: the W/L logo, the headline Il gestionale per il tuo cable park, a line saying the platform was built for Como Lake Cable and is now offered to other cable parks, and buttons for the plans, a demo and a leaflet
wakeleague.it, the product's own site. It presents the platform to parks and hosts the league.

What made it hard

  • The first park was live. comolakecable.it takes bookings every day. Turning its code into a product could not change a single page of it.
  • The park was written into the code. Its fonts were named in about 700 places, and its name sat inside sentences in three languages.
  • One install for all, or one per park. A single shared install would have meant a park column on every table and every query: a rewrite of software in daily use.
  • A league across separate parks. Each park keeps its customers in its own database. The ranking still had to put their riders on one table.
  • A ranking shows people. The league had to carry as little as possible about each rider.

What shipped

  • A brand pack per park. Web addresses, the sender of its emails, contacts, the issuer on its receipts, logos, fonts, colours and the names of its levels. The code is the same for every park.
  • A site for parks without one. A park can keep its own website and link to the platform, or use a site drawn from its own catalogue, prices and opening hours.
  • Settings per park. Card payments, the assistant and analytics can each be turned off, and the number of cable lines is set per park.
  • A demo park. A complete install with sample riders and bookings, reset every night, for a park to try before it decides.
  • The league. wakeleague.it ranks the riders of every park that joins, with a page for each trick and the thirty levels.
  • Three plans. Booking and management; branding and online sales; and the features for riders: ranking, tricks, levels and videos.
The demo park's home page: the Wake League logo, the heading Wake League Demo Park inside a drawing of the cable's outline, a line about booking runs online, paying from the account balance and climbing the park's ranking, and buttons to book a run and see the prices
The demo park. The same code as comolakecable.it, with another brand pack and a site drawn from its own catalogue.

How it works

One codebase, one install per park. Each park runs its own copy, with its own database and its brand pack. The park controls its customers' data, and nothing one park does can reach another. While the brand work went in, a script recorded everything comolakecable.it draws, 254 files, before and after each change. A change went in only when the two were identical.

A league gathered from feeds. A park that joins publishes its ranking at one address, readable only with a key it shares with the league.

  • What it carries. Each rider as a code, with a nickname or a first name and an initial, their tricks and their points. No contact details and no date of birth.
  • Photos and clips. They travel as signed links, which stop working when the rider leaves the league.
  • The read. Every 15 minutes, wakeleague.it reads each park's feed. A feed is checked whole before anything changes, and a broken one leaves the park's last ranking in place.
  • Leaving. A park that leaves removes its key, and its riders drop out of the ranking at the next read.
  • The same rules. Points count only for the shared trick list. A park's own bonus achievements stay at the park.

Riders are in the league unless they untick a box on their member form. On each park's board, a switch moves between the park's own ranking and the league.

The thirty levels of the league, each a small illustration with a name and the points it takes, from Sacco di patate at 0 points to Super Sayan Divino at 9500
The ladder every park shares: thirty levels, each with its drawing and the points it takes.

How we built it

  • 18 July to 18 September 2026. The platform, built for Como Lake Cable and live on 18 September.
  • 27 October. Three decisions: one install per park, a site drawn from the park's own data for parks that have none, and each park's brand set up by us. One rule on top: comolakecable.it does not move. The same day, the name, the first brand packs and the demo park online.
  • 28 October. The park's feed, and the ranking on wakeleague.it.
  • 29 October. Cables with more than one line.
  • Updates. One codebase for every park. Each install is updated on its own, and a format number in the feed keeps the parks and wakeleague.it in step.

Result

  • Como Lake Cable runs on the same code any new park will, and its site did not change on the way.
  • A new park needs an install and a brand pack, not a copy of the code.
  • The league is live with one park: 50 riders, and a page for each of 106 tricks, when we wrote this.
  • A park can try every screen in the demo park before it decides.

Stack

  • Platform. Python 3.13, Django 6.1, PostgreSQL 16.
  • Installs. Docker Compose, one per park. The brand pack is chosen when the install is built.
  • League. wakeleague.it, a Django site that reads every park's feed every 15 minutes.
  • Assistant. Claude, by Anthropic.
  • Payments. Stripe Checkout.
  • Tests. More than 2,400 automated tests, and the snapshot of comolakecable.it.

Article 037 · 19 November 2026 · 4 min read.
Reply to paolo@mont3.ch.