The first clue was a contest to make Windows run on a Mac. In 2006, people who wanted the answer pooled prize money, and programmers went to work. Brandon Kessler, then a music entrepreneur, saw more than a clever workaround. He saw a market in which a problem, an audience and a reward could find each other. In 2009 he launched ChallengePost to put that idea on the web.
The first version was broad. A challenge might ask for an app, a recipe, or a public-sector idea. New York City agencies and consumer brands appeared alongside one another. The premise was appealingly democratic: publish a problem and let capable strangers surprise you. The awkward part was that a marketplace for every kind of challenge had to be good at every kind of challenge.
- Devpost hosts public hackathons and sells a separate private platform for employee and customer events.
- It gives organizers registration, project submissions, judging, promotion, and reporting in one workflow.
- Its distinctive asset is a developer community, plus a lasting record of the work those developers make.
- Qualifying student-only events can use the platform free; corporate pricing is quoted by Devpost.
The useful narrowing
By 2013, Kessler had spotted a pattern: the competitions that seemed to work best were about software and technology. That observation changed the company. In 2015, ChallengePost became Devpost. Even its own rebrand became a Devpost project, described by the team as two months of work to change the business overnight. The entry reads like a warning to anyone who thinks a name change is a logo and a redirect: email deliverability, data, search traffic, users and infrastructure all had to come along.
The narrower company had a clearer transaction. A developer wants a reason to try a tool, practice a skill, meet collaborators or build a portfolio. A company wants developers to do something more convincing than click an ad: use its API, cloud service or model in a working project. Devpost supplies the deadline and the surrounding machinery. The organizer brings the challenge and, often, the prize.
That sentence is also a business proposition. A tutorial can show that a feature exists. A submission can show what someone made with it, where they got stuck, and whether the result deserves another week of effort. The project gallery becomes a curious sort of ledger: part portfolio, part product feedback, part proof that an event happened.
The product is the whole loop
Two doors into the same workshop
The public door is devpost.com. Companies, communities, universities and individuals publish events; participants register, form teams, submit projects and find the next challenge. Devpost says this platform can reach more than six million developers. That reach gives a corporate organizer something a blank event page cannot: an audience already inclined to build. Most listed events, however, are run by independent organizers. Devpost hosts their pages and tools; those organizers set rules, choose judges and deliver prizes unless an event is expressly marked as managed by Devpost.
The private door is Devpost for Teams. An employer can run an internal hackathon to test ideas that would otherwise wait behind the ordinary roadmap. A vendor can invite customers to build with its product without displaying the event to the public. Access controls, templates, submissions, scoring, voting and permanent galleries make this closer to an operating system for recurring programs than a ticketing page. Student-run, student-only hackathons form a third route: qualifying organizers can use Devpost free, online or in person.
For paying customers, the price depends on which door they choose. Public online events carry fees, with Basic, Mid and Full-service options and separate marketing packages; Devpost offers project management, rules writing, participant support and judging help. The private product is an annual per-seat subscription, with additional services available. Devpost does not publish a universal corporate price, so any neat dollar figure would be false precision. Participation itself is free for builders.
The harder question is Monday
A crowded kickoff and a handsome prize make easy photographs. The harder question arrives when everyone returns to work: what survived? Grafana Labs offers one answer. It runs four company-wide hackathons a year and says nearly 40% of projects have become shipped products or roadmap features. Finastra has described seven or eight internal projects going directly onto its roadmap. Those are customer-reported outcomes, and they depend on what each company does after judging. A platform can store an idea; a manager still has to sponsor it.
Figures describe different populations and are not directly comparable.
The customer list is wide: Salesforce has run open competitions and conference events; Neo4j has used private customer hackathons; Grafana Labs and Okta use employee programs. Government agencies, nonprofits and universities also use the platform. The problems vary. A developer relations team wants adoption. An engineering chief wants new prototypes. A customer team wants users to learn by making. The same submission form can serve each, but success should be measured differently: new builders for one, product-ready work for another, deeper use for a third.
Devpost’s 2026 AI report says enterprise AI hackathons rose 83% in the previous year. It also says developers who had joined six or more hackathons shipped AI projects to production at 2.2 times the rate of first-time participants. That is an association in Devpost’s data, not a promise that the seventh event causes a product launch. Experienced builders may simply be more likely to attend again. Still, the pattern points to a practical lesson: a recurring program gives teams time to learn from one attempt and try again.
A contest is useful only if someone owns the next step
An organizer can copy Devpost’s logic without copying its scale. Pick a specific tool or problem. State what counts as a complete submission. Give builders enough time to make something, but a deadline close enough to force choices. Put judging criteria where participants can see them. Preserve the projects after prizes are awarded. Then assign a person to review the promising work when the room is quiet.
The method has limits. A hackathon is a poor substitute for a product team when the work needs years of maintenance, confidential data without safe access, or painstaking regulatory approval. A flashy prototype can conceal brittle code. A large registration count can conceal very few submissions. Devpost’s own organizer guidance puts registrant-to-project conversion in a broad 5% to 33% range; the width is a reminder that the event design matters at least as much as the software around it.
The name change in 2015 clarified what Kessler had actually found. The useful commodity was not an abstract “idea.” It was the moment a person had to make the idea run, show it to somebody else, and decide whether to keep going. Devpost turned that moment into a repeatable service. The prize gets the applause. The project page is what remains.