Rote Playoffs registration is open, and the deadline is closer than most hackathon deadlines: sign-ups run until 1 September 2026, with the kickoff livestream the same day at 4pm UK time. The Rote Playoffs is a free, fully online AI hackathon run by Modiqo, the San Francisco startup behind the Rote agent-workflow platform, together with the WeMakeDevs developer community. First place wins a MacBook Pro, and over 1,200 builders had already registered before the opening ceremony.
The premise is unusual for a hackathon. Entrants do not build an app or a demo. They ship a “Play”: a repetitive working task, solved once with an AI agent, captured by Rote, and published so that other people can run it. The event page puts it plainly: a Play is “a workflow you’ve done repeatedly and resented each time, solved once and kept properly.”
This article covers what the Rote Playoffs is, the key dates and how to register before the window closes, what a Play actually is, the prizes and how judging works, the company behind the event and its $3 million pre-seed round, and how to prepare in the few days available. Every figure traces to a link in the References section.
Table of contents
- What Is the Rote Playoffs?
- Rote Playoffs Key Dates and How to Register
- What You Actually Build: Plays Explained
- Prizes and Judging at the Rote Playoffs
- The Company Behind It: Modiqo and Its $3 Million Bet
- Where the Rote Playoffs Fits in the Agent Reliability Debate
- How to Prepare for the Rote Playoffs in the Time Left
- Rote Playoffs: Frequently Asked Questions
- References and Further Reading
What Is the Rote Playoffs?
The Rote Playoffs is a one-week, online-only competition hosted on Luma under the WeMakeDevs banner, presented by Kunal Kushwaha, the founder of the WeMakeDevs community, and Chetan Conikee, the founder and CEO of Modiqo. DevTools Academy is also a collaborator on the event.
One arena, one job
The organisers describe the Rote Playoffs as “a live event of builders with one arena and one job: ship a Play that other people actually want to run.” That framing matters, because the winning condition is not novelty or stagecraft. A submission succeeds if it runs reliably, reads clearly to a stranger, and gets adopted by other participants after it is published.
A hackathon shaped like a product launch
The competition doubles as the most visible public test yet of Rote, the platform Modiqo launched out of stealth in May 2026. Rote captures what AI agents actually did during a successful run and converts those traces into deterministic, replayable workflows. A hackathon whose only deliverable is a published Play is, in effect, a coordinated stress test of that capture-and-replay loop by hundreds of outside builders at once.
Who can enter
Registration is open to anyone, and the Rote Playoffs has no team-size requirement or entry fee. Because a Play is captured from a task you already do, the event is as open to a marketing operations specialist automating a reporting chore as it is to a developer wiring up repository maintenance. The agent harnesses Rote works with include Claude Code, Cursor, Codex App, Kimi, Hermes Agent and Pi Coding Agent, so most participants can keep the tools they already use.
The organisers’ pitch is deliberately broad, and the structure rewards that breadth. Because the judging leans on adoption, the Rote Playoffs benefits from a mixed field: the more varied the entrants’ day jobs, the more corners of ordinary knowledge work end up represented in the community library by the end of the week.
Rote Playoffs Key Dates and How to Register
The schedule is compressed, which is worth spelling out precisely because the registration window closes the day the event begins.
The registration step
Registration happens on the event’s Luma page, and the organisers ask entrants to do more than click a button before kickoff. The warm-up checklist asks every participant to finish the platform’s onboarding steps 01 through 06, run one practice Play end to end, and post “warmed up” in the community Discord. By late August the attendee counter had passed 1,246 registrations.
The competition week
The kickoff livestream on 1 September at 4pm UK time opens the arena. Building runs through the week, and submissions close on Sunday 7 September at 8pm London time. There is no separate submission form: publishing a Play to the platform’s Community setting is the submission.
| Milestone | Date and time | What happens |
|---|---|---|
| Registration and warm-up | Now until 1 September 2026 | Register on Luma, finish onboarding steps 01–06, run one practice Play, post “warmed up” in Discord |
| Kickoff livestream | 1 September, 4pm UK | Rules, walkthrough and the opening of the build window |
| Build week | 1–7 September | Capture, refine and document your Play |
| Submissions close | Sunday 7 September, 8pm London time | Publishing a Play to the Community setting is the submission — no form |
| Format | Fully online | Free entry, no team-size requirement, WeMakeDevs Discord for support |
Why the warm-up is mandatory in spirit
A week is a short build window, and the practice-Play requirement exists so that nobody spends the first two competition days learning the capture flow. Entrants who arrive at the kickoff having already run one Play end to end start the Rote Playoffs with the mechanics behind them and the whole week free for the actual idea.
What You Actually Build: Plays Explained
Understanding the deliverable is the difference between a submission that places and one that gets scrolled past, so it is worth being precise about what Rote captures.
From agent run to Play
When an AI agent works through a task, it reasons step by step: reading files, calling APIs, retrying failures, verifying output. Rote watches a successful run and crystallises the full trace, including the failures along the way, into a versioned artefact. That Play can then be recalled and re-run against fresh inputs without the agent re-reasoning the whole problem from scratch, and the platform’s core claim is that this replay is deterministic rather than probabilistic.
The numbers behind the pitch
Modiqo’s own measurement on its hello-world example is stark: a first discovery run took roughly 14,900 reasoning steps, while a repeat run of the captured Play needed about 300, a 98% reduction in reasoning work. Investor materials around the company’s funding round cite 30–40% lower generative AI spend for high-volume workloads as the commercial version of the same claim.
Shareable and inspectable by design
A published Play is addressed by a URI and carries visible metadata: the author, the version, the permissions it needs, the tools it touches, and an integrity digest. Anyone considering running it can inspect all of that before execution, which is precisely the property the hackathon’s judging leans on. The tool integrations available at launch include Python, Shell, GitHub, Gmail, DNS lookups and Lighthouse audits, with local credentials staying local.
What makes a good hackathon Play
The organisers’ guidance is to pick a workflow you have done repeatedly and resented each time. The strongest candidates are chores with a stable procedure and fresh inputs every time: triaging a repository’s new issues, auditing a site’s performance and filing the results, turning a weekly export into a formatted report, or checking a batch of domains’ records. Novelty is worth less than the moment another participant sees your Play and thinks: I do that every week too.
Prizes and Judging at the Rote Playoffs
The prize table is Apple hardware from top to bottom, and the judging is deliberately adoption-shaped.
The prize pool
| Place | Prize |
|---|---|
| First place | MacBook Pro |
| Second place | iPad |
| Third place | iPhone 17 |
| Best social posts (tag Modiqo on LinkedIn or X) | Apple Watches |
For a free-entry online event, that is a strong table, and the hardware goes to individuals rather than teams. The social-post prize is a telling inclusion too: it rewards the participants who document their build in public, which serves the platform’s visibility as much as the community’s learning.
How winners are picked
Three questions decide the ranking, and none of them is “how clever is the idea”:
| Judging question | What it rewards |
|---|---|
| Does the Play actually run? | Reliability over demo polish — a Play that fails on replay is out |
| Can someone unfamiliar with it understand and trust it? | Clear naming, documentation and honest permission scopes |
| Do others adopt it after publication? | Usefulness — the community vote is cast by running your work |
Why adoption is the hardest criterion
The first two questions are within an entrant’s control; the third is a market test inside the Rote Playoffs itself. A Play only scores on adoption if other builders, mid-competition, decide it is worth their time to run. That pushes entrants towards common, boring, genuinely shared problems rather than personal edge cases, which is exactly the library of workflows a young platform wants seeded by its first public cohort.
The Company Behind It: Modiqo and Its $3 Million Bet
A hackathon is a marketing motion as well as a community event, and the company running this one has a specific thesis to prove.
Founder and funding
Modiqo was founded by Chetan Conikee, previously the founder and CTO of the code-security firm ShiftLeft, which later became Qwiet AI. His background is in cybersecurity and large-scale software analysis, and it shows in Rote’s design: the emphasis on integrity digests, inspectable permissions and locally held credentials reads like a security engineer’s answer to agent sprawl. In May 2026 the company announced a $3 million pre-seed round co-led by Heavybit and Seligman Ventures, with participation from Irregular Expressions and angel investors.
The problem statement investors bought
Heavybit general partner Joseph Ruscio summarised the thesis when the round was announced: “today’s AI agents are impressive in the demo and unreliable in production.” Agents work from one-off chat logs rather than provable, iterable artefacts, so every execution of a task starts from scratch no matter how many times the agent has already solved it. Rote’s wager is that the fix is not a bigger model but a memory of the run that worked — the company’s tagline is “Don’t design the workflow. Capture the run that worked.”
How the platform is priced
Rote sells per organisation per month, with a free Community tier that is all a Rote Playoffs entrant needs.
Why a hackathon, and why now
For a pre-seed company, the Rote Playoffs solves three problems at once. It generates a public library of community Plays, it produces real-world reliability data from hundreds of uncontrolled environments, and it borrows the reach of WeMakeDevs, whose founder Kunal Kushwaha has one of the larger developer audiences in the DevOps and cloud-native world. The cost of the prize pool is modest against what an equivalent amount of enterprise pilot feedback would take months to gather.
Where the Rote Playoffs Fits in the Agent Reliability Debate
The event lands in the middle of an industry argument about whether autonomous agents are ready for production work, and the format takes a clear side.
Determinism as the missing layer
The reliability critique of agents is well rehearsed: the same prompt can produce different behaviour on different days, token costs balloon as agents re-reason solved problems, and context windows fill with the debris of earlier steps. Rote’s approach — freeze the successful path, replay it deterministically, and spend inference only when something genuinely new appears — is one of several competing answers, alongside heavier orchestration frameworks and the sub-agent patterns we covered in our piece on agentic AI and autonomous AI employees. None of those approaches has won the argument yet, which is what makes a public, scored experiment genuinely useful.
The token economics angle
There is a cost argument underneath the reliability one. Every re-reasoned run of an already-solved task is paid for in tokens, and Modiqo’s pitch to enterprises is that replaying a captured Play reserves inference spending for genuinely new work. The company’s benchmarked scenarios claim up to a 40% reduction in inference token usage for high-volume workloads. For entrants, the same mechanics mean the free Community tier stretches further than it otherwise would: a practice Play replayed ten times costs a fraction of ten fresh agent runs. Whether those percentages survive contact with hundreds of community-built workflows is one of the quieter things the Rote Playoffs will reveal.
A test you can watch
What makes the Rote Playoffs interesting to neutral observers is that its results will be public. Every submitted Play carries adoption numbers, and a week of hundreds of builders capturing real workflows will say more about where deterministic replay works, and where it breaks, than any launch post. If the community library fills with Plays that strangers actually run, the thesis gains evidence; if submissions cluster into demos nobody re-executes, that is evidence too.
The wider tooling picture
For teams evaluating this space, the sensible frame is that captured workflows complement rather than replace general-purpose agents: the agent explores, the Play preserves. Our running index of notable platforms in our AI models and tools hub tracks how quickly this category is filling out, and the Rote Playoffs will be a useful signal of whether capture-and-replay graduates from pitch to practice.
How to Prepare for the Rote Playoffs in the Time Left
With registration closing on 1 September, preparation time is measured in hours, but the checklist is short.
Before the kickoff
Register on the Luma page, join the WeMakeDevs Discord, and work through onboarding steps 01 to 06 on the platform. Then run one practice Play end to end, however trivial, and post “warmed up” in the Discord channel as the organisers ask. The practice run is the single highest-value hour of preparation, because it front-loads every tooling surprise into the warm-up rather than the scored week.
Choosing your workflow
Make a shortlist of three recurring chores from your actual work before the kickoff livestream. Apply the judging questions to each: will it run unattended, would a stranger trust its permission scopes, and does anyone else have this problem? The third question should pick your winner. A workflow that ten other entrants recognise from their own week is worth more than an impressive one nobody shares.
During the build week
Ship early rather than late. Because publication is submission, a Play published on Wednesday has four days to accumulate the adoption that a Sunday-evening submission never can. Use the remaining days to improve documentation, tighten permissions and respond to feedback from people running it — visible iteration is itself a trust signal to the judges and the community. Treat the Discord as part of the arena as well: the organisers answer questions there, and the participants most likely to run your Play are the ones already talking about theirs.
After the event
Win or lose, a published Play remains a public, versioned artefact with your name on it, which makes the Rote Playoffs one of the cheaper ways to put a verifiable piece of automation work in front of a large developer community. The best social-post prize also means a well-documented build thread on LinkedIn or X has hardware attached to it.
Rote Playoffs: Frequently Asked Questions
When does Rote Playoffs registration close?
Registration runs until 1 September 2026 on the event’s Luma page, the same day as the kickoff livestream at 4pm UK time. The organisers ask entrants to finish onboarding and run one practice Play before then.
Is the Rote Playoffs free to enter?
Yes. Entry is free, the event is fully online, and Rote’s Community tier, which is all you need to capture and publish a Play, costs nothing.
What do winners of the Rote Playoffs receive?
First place wins a MacBook Pro, second an iPad, and third an iPhone 17. Apple Watches go to the best social media posts about the event tagged to Modiqo on LinkedIn or X.
How are submissions judged?
Three questions: does the Play actually run, can someone unfamiliar with it understand and trust it, and do others adopt it after publication. Publishing a Play to the Community setting is the submission — there is no separate form.
What is Modiqo?
Modiqo is a San Francisco startup founded by former ShiftLeft founder Chetan Conikee. It raised a $3 million pre-seed round in May 2026, co-led by Heavybit and Seligman Ventures, to build Rote, a platform that captures successful AI agent runs and replays them as deterministic workflows.
Do I need a particular AI coding tool to take part?
No. Plays run on several agent harnesses, including Claude Code, Cursor, Codex App, Kimi, Hermes Agent and Pi Coding Agent, so most entrants can compete with the tools they already use.
What can a Play actually do?
The integrations available at launch cover Python, Shell, GitHub, Gmail, DNS lookups and Lighthouse audits, with local credentials staying on your machine. That is enough surface for most reporting, repository maintenance, auditing and outreach chores — exactly the kinds of tasks the Rote Playoffs is designed to collect.
References and Further Reading
Luma: Rote Playoffs Hackathon registration page
Modiqo: Rote product site and pricing
SiliconANGLE: Modiqo raises $3M in pre-seed funding to help AI agents learn by Rote
PR Newswire: Modiqo raises pre-seed round to bring deterministic AI workflows to enterprises
TechEdge AI: Modiqo secures $3M to launch Rote AI infrastructure platform
Chetan Conikee: Announcing my new company, Modiqo
More AI coverage: explore Progressive Robot's AI Models, Tools & Releases hub — hands-on reviews, setup guides and benchmarks in one place.