Devpost

Devpost hosts hackathons in two distinct modes that are worth separating before evaluating, because they serve entirely different organisational goals.

Public hackathons on Devpost are aimed at growing a developer ecosystem and promoting a platform. A company running one is doing developer marketing: attracting people who have never used its API to build something with it over a weekend, in the hope that some continue afterwards. Success is measured in developers acquired and awareness generated, and the participants are strangers.

Devpost for Teams runs internal hackathons for innovation, collaboration and retention within an organisation. Here the participants are employees, the goal is ideas and cross-team relationships, and retention appears as a stated outcome because engineers who get to build something of their own choosing occasionally are measurably less likely to leave.

Those need different features. A public hackathon needs discovery, open registration, judging at scale and public project galleries. An internal one needs private access, integration with corporate identity and confidentiality of what gets built, since internal projects frequently touch real systems and unreleased plans.

Published use cases include AI hackathons, customer hackathons and employee hackathons, with AI hackathons currently prominent as companies encourage teams to explore what the technology can do for them.

Customer hackathons are the less obvious category and a commercially interesting one: inviting existing customers to build on your platform produces both product feedback and deeper integration by the customers who participate.

Pricing is not published, which is normal where public and internal hosting carry different commercial models.