01
Network
A directory of student devs you can actually reach. No cold-email moat, no recruiter middlemen.
Developer Network · Campus chapters
Build locally.
Connect globally.
DevNet is a network of student-led developer chapters. Each chapter runs independently on its own campus. Together, we share a brand, a standard, and a distribution engine that turns local builds into public proof of work.
See the network02 · The Network
Where DevNet runs today
Thirteen network presence hubs — builders coordinating locally before or alongside a formal campus chapter. Hover a pin for city and region; switch to Chapters for campus chapter pins.
Network presence
03 · What is DevNet
A network, a brand layer, and a distribution engine for local devs.
DevNet is three things at once: a connective tissue between builders across campuses, a shared identity that lets every chapter punch above its weight, and a pipeline that turns local projects into public proof of work.
02
Brand layer
One identity, many chapters. Local autonomy stays local; the DevNet name carries beyond your campus.
03
Distribution
Featured projects ship through DevNet's X and LinkedIn — accepted work is shown to the wider network.
04
Standard
Autonomy with a shared standard. Chapters run their own way, the standard keeps quality recognisable.
05
Opportunity
Founder roles, campus lead roles, and access to projects you wouldn't see from outside the network.
04 · Members
Low-commitment membership. High-leverage network.
Membership is intentionally lightweight. You join the network, you stay in it on your own terms. No quotas, no activity minimums, no fees — ever.
- No fees, no quotas, no activity minimums.
- Get featured on DevNet's X and LinkedIn when your project ships.
- Connect with members across every chapter and presence hub.
- Opt into webinars, hackathons, and chapter events. Nothing is required.
- Any stack, any level, AI-built projects welcome.
05 · Chapters
Independent affiliates. One DevNet.
Chapters are independent campus affiliates of DevNet — formal chapters you can start on a school. The map lists network presence hubs (builders coordinating locally); chapters are a separate layer when a campus goes live.
Run events your way
Build nights, demo days, study jams, hackathons. Chapters pick the format that fits their campus.
Tap the wider network
Reach builders in other chapters, presence hubs, and DevNet's central channels — without re-explaining what DevNet is.
Get distribution
Standout chapter projects ride DevNet's distribution pipeline to the wider audience.
Keep autonomy
No corporate playbook. Chapters own their voice, their events, and their members.
06 · The Standard
Autonomy with a shared standard.
The network only works if quality stays recognisable across every chapter. The standard is small, practical, and never a leash.
-
01
Build something that actually runs.
Featured projects need a working prototype, beta, or live product. Slides and screenshots aren't a product.
-
02
Open to any stack and any level.
First-time builders, senior engineers, AI-assisted projects — all welcome. We care about what you shipped, not what you used to ship it.
-
03
Respect the network.
Don't spam, don't gatekeep, don't trade on the DevNet name to sell things. Local autonomy doesn't mean ignoring the people in other chapters.
-
04
Keep it free for members.
No chapter charges members to join DevNet. Sponsorships and event partnerships are fine; pay-to-play membership is not.
-
05
Use the DevNet name honestly.
Anchor your chapter to a city or school. Don't claim presence you don't have. Map pins are network presence until a campus chapter is live — then it earns a chapter pin.
07 · Chapter naming
City-first. Always.
When you launch a campus chapter, name it after the city first, then anchor to the school. Presence hubs on the map (Toronto, London, NYC, and the rest) stay as network presence until a chapter goes live.
- DevNet Toronto
- DevNet Boston
- DevNet Vancouver
08 · Opportunity
Real roles. Real responsibility.
Chapters are looking for founders and campus leads. These aren't résumé fillers — they're actual ownership over a piece of the network.
Open role
Founder · Chapter
Be the first chapter on your campus. Set the tone, recruit the first members, run the first event. You own the chapter and its identity, with DevNet behind you.
- Full chapter autonomy
- Direct line to DevNet leadership
- Distribution access from day one
Open role
Campus Lead
Join an existing chapter as a campus lead. Run events, plug into the network, get featured. Lower lift than founding, higher lift than just being a member.
- Sit on chapter leadership
- Help shape local events and standards
- Network across all DevNet chapters
09 · Projects
Ship projects. Get seen.
The fastest way to convert a build into public proof of work. Every featured project shows on DevNet's X and LinkedIn and gets routed back to the chapters and presence hubs.
01
Submit
Send your working prototype, beta, or live product through the feature form.
02
Review
Every submission is reviewed manually. We're looking for working software, not engagement metrics.
03
Feature
Accepted projects are featured across DevNet's channels and connected back into the chapter network.
10 · Get involved
Build locally.
Connect globally.
Three ways to plug into the network. Pick the one that fits.