Skip to content

HomeUse casesHackathons and internal challenges

The challenge lasts a weekend. What came out of it doesn’t have to end.

A hackathon usually lives in a form, a spreadsheet and a group created on Friday and abandoned on Monday. Here sign-ups come in by track, the teams are visible to everyone, the jury reviews in the same place the submissions arrived, and what was built stays published with author and date — so the next edition starts where this one stopped.

How it’s built

  1. 1

    A calls space for sign-ups, with a track per challenge and the jury reviewing inside the platform.

  2. 2

    An events space with the kickoff, the checkpoints and the final presentation.

  3. 3

    A gallery with what each team delivered, which is what draws sign-ups to the next edition.

  4. 4

    Ranking to recognize who really took part, not just who got on stage.

The result becomes an archive instead of a shared folder.

The spaces you can use

In order from what almost everyone uses to what few people remember is possible. You don’t need all of them to start.

Nothing here is exclusive to this setup: all eight space types come with every plan. What changes is which ones you turn on.

We are inviting the first communities.

Memberfy is in closed beta, so access is by request. Tell us what you want to build: we reply, set it up with you and stay close afterward.

Request access