Deployment schedule

Hackathons

A curated deployment schedule, not a listing service. Agent/AI-relevant events in the KW–GTA–Toronto orbit plus notable remote. The opinion is the value. Squads form in the #hackathons Discord channel. Refreshed monthly.

Hack the North crew forming September 18-20, 2026 · University of Waterloo Canada's biggest hackathon. Sponsor-rich and agent-friendly; go to ship a real build, not to farm swag.
SOON crew forming October 23-25, 2026 · Toronto, location TBA Fifty builders, one weekend, one house. SOON is application-only and small on purpose: 48 hours living under one roof with the companies sponsoring the build, so the bar is a shipped product, not a pitch deck. Apply early. Luma link to follow.
DeltaHacks 13 solo-friendly January 9-10, 2027 · McMaster University, Hamilton 24 hours in Hamilton on a build-for-change brief. Short enough that agent scaffolding you already trust beats anything started from scratch.
UofTHacks 14 crew forming January 2027, exact dates TBA · University of Toronto Canada's first student-run hackathon, 36 hours and 500-plus hackers. Dates are not posted yet, so watch the site if you want the January slot.

Deployments

Battle of the Schools September 12-13, 2026 · Toronto devkick ran a workshop and joined the panel at the UTMIST × WAT.ai Battle of the Schools.

How to use this schedule

A hackathon is a deployment window: a short period where a team has to turn an idea into a working build. This page is for developers who want that constraint, especially builders working with AI agents and agentic tools in the KW-GTA-Toronto orbit. It also includes notable remote options when they are relevant to the same kind of work.

The list is curated, not scraped into existence. Each entry has a date, location, link, and one line of devkick's take. That take is the reason to read the page. It can point out an agent-friendly format, strong judges, a sponsor-heavy environment, or a reason to skip an event unless you have a specific goal. A name and a URL alone are not useful guidance.

Squad status makes the social layer visible. Crew forming means a team conversation is open. Crew confirmed means a squad has already formed for that event. Solo-friendly means the event can make sense without arriving with a complete team. The status is a coordination signal, not a promise of placement, prizes, or a particular result.

Start with the date and the event's own rules, then decide what you want to ship. The #hackathons Discord channel is where squad conversations happen. devkick does not host these external hackathons, sell tickets for them, or represent their organizers. After a deployment, the intended follow-up is a short recap slot at the next Kick night and a result recorded here when there is a real result to report.

This page stays intentionally small. It is refreshed once a month, keeps the opinion visible, and avoids becoming a second events aggregator. The value is a focused deployment schedule for builders in and around the corridor, with enough context to make a decision and no claim that the page covers every event.

Questions, answered

What is the devkick hackathons page?

It is a curated deployment schedule for agent and AI-relevant hackathons in the KW-GTA-Toronto orbit, plus notable remote events. It is not a general listing service.

How does devkick choose hackathons?

Each entry carries devkick's take on the event. The opinion is the value, whether that means an agent-friendly format, strong judges, or a reason to skip it.

What does squad status mean?

Each entry can be marked crew forming, crew confirmed, or solo-friendly. Squads form in the #hackathons Discord channel.

How often is the schedule refreshed?

The schedule is refreshed monthly. It is a bounded curation pass, not a live feed of every hackathon.