LaceUp

Roadmap

What we're building, in order.

Three columns and no dates. Now is being built, Next is committed, Later is real and unscheduled. Items move as organisers and players tell us what matters, and every request sent from inside the app lands on the same board.

Last updated September 8, 2026

Now

3

In progress

  • Card payments switch on

    Checkout for league registration and memberships is built and waiting on live keys. Until it is on, organisers collect payment their own way and LaceUp records the registration.

  • Bring your league onto LaceUp

    Everything a new organisation needs is in place: its own address, its own colours, its own staff, its own payouts. Onboarding the next league is what remains, and it is being done by hand.

  • Claim your own web address from the admin

    Point a hostname at LaceUp and confirm it yourself on the settings screen. The screen is built and switches on once the hosting credentials are in place.

Next

2

Committed, not started

  • Email that comes from your own domain

    Every message goes out from one platform address today, with your organisation as the sender name. A verified sending domain per organisation puts your own address on it.

  • Your name on the sign-in screen straight away

    The sign-in, signup and password pages work out which organisation they belong to in the browser, so your name arrives a beat after the page does.

Later

2

On the list, unscheduled

  • Player stats that carry across seasons

    Records and streaks on a player page, built from the games already in the schedule. Set aside when leagues and seasons were designed, and still on the list.

  • Sports other than dodgeball

    Everything LaceUp says about courts, matches and rosters is read from one place, so a second sport is a configuration change. Nothing is scheduled.

Have something in mind?

Sign in and use Request a Feature. It goes straight onto the board that feeds this page.

Request a feature
Already shipped106 updates across 13 batches, newest first.Changelog →