Your hackathonReady for big ideas

MainPath gives every team a shared project foundation. Build with familiar AI agents, test changes and share the demo with a link.

From the first promptto the demo

Get straight into the project

Every team starts with a prepared structure and rules for its AI agent. A repository and build workflow are included.

Keep building in the browser

A prepared development environment helps teams who do not want to configure their laptops. Everyone works on the shared project.

Know what works before demo time

Automated tests and builds check changes on every push. Teams can spot problems before their presentation.

Give your demo its own link

The web application runs at an address with HTTPS. Mentors and judges can open the current version directly in their browsers.

One eventMany teams in view

MainPath helps you organise collaboration before, during and after the hackathon.

Give people the right access

Teams work in separate projects. Organisers and mentors get the permissions they need to support them.

Keep familiar AI agents

Claude Code, Codex or Cursor remain the teams’ tools. MainPath provides the shared project foundation.

Keep building after the event

The code stays with the team. After the weekend, the hackathon project can grow into its next version.

How your hackathon startsAnd what comes next

A shared test run before the event checks that access, templates and the demo environment work together.

  1. Prepare before the event

    Create the organisation, prepare team projects and assign mentor permissions. Try the setup together before the event.

  2. Bring teams into their projects

    Each team picks a template or has existing code checked for support. Then it connects its preferred AI agent.

  3. Build and try things out

    Teams work locally or in a workspace. Changes go through tests and builds; the web demo is deployed to dev.

  4. Show the results together

    Mentors and judges open the demo links. The code stays in the project so teams can keep working after the event.

Your next hackathonA shared starting point

Tell us the date and number of teams. We can look at projects, access and the environment for your demos together.

Questions about your hackathon

How do we prepare the start?

Create an organisation, plan one project per team and assign appropriate permissions. We recommend a test run before the event to check access and the demo environment.

Does every team need its own server?

No. Several team projects can run on one server while remaining separate projects. We can discuss the right hosting option with your organisers.

What can mentors see?

You decide through roles and access permissions. Mentors can support the projects shared with them and open web demos through their links.

Can teams build mobile apps too?

Yes. MainPath supports technologies including Flutter, Expo and native apps. The appropriate store credentials must be configured for TestFlight and internal Play tests.

App and store features

What does an event cost?

The options depend on your scope, including projects, users, workspace hours and pipeline minutes. Tell us the date and number of teams so we can discuss a suitable offer.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab