Challenge Overview
The PyWeb Creators hackathon challenges developers to build web applications using Python EVERYWHERE—whether that's Python-only frameworks or Python running directly in browsers.
On August 1st, we celebrate World Wide Web Day—commemorating Tim Berners-Lee's invention that democratized information sharing. This year, we're proving that Python can power the ENTIRE web stack!
The Mission
Choose your path and show the world that Python belongs everywhere on the web!
Traditional web development requires juggling HTML, CSS, JavaScript, and backend languages. But what if Python could do it all?
This hackathon celebrates two revolutionary approaches: frameworks that generate everything solely from Python code, and technologies that run Python directly in browsers.
Two Paths, One Goal:
Python-Powered Web
Expertly combine both approaches! Use FastHTML for the backend and PyScript for complex client-side tasks. Or try Streamlit with Pyodide components. Get creative!
Hybrid Approach
Build complete web apps where you write primarily Python code. The framework handles HTML/CSS/JS generation for you.
Python-Only Frameworks (Server-Side)
Path A:
Run Python directly in the browser using PyScript, Brython, or similar technologies. Perfect for zero-server applications!
Python-in-Browser
(Client-Side)
(Client-Side)
Path B:
Note: This is not an exhaustive list! If you know other Python web libraries or tools, you're welcome to use them. We encourage exploration and innovation!
- PyScript — Run Python in browser
- Brython — Python client-side implementation
- Pyodide — CPython compiled to WebAssembly
- Skulpt — Python implementation in JavaScript
- Transcrypt — Python to JavaScript compiler
Python-in-Browser Technologies
Path B:
- FastHTML — Modern framework with HTMX
- Reflex — Full-stack framework compiling to React
- Streamlit — Data apps with automatic reactive UI
- Gradio — ML/data science-focused interfaces
- NiceGUI — Native-feeling web apps
- Flet — Flutter-based Python framework
Python-Only Web Frameworks
Path A:
Suggested Technologies
Hybrid Guidelines
Document which parts use which approach
Aim for Python in both frontend and backend
Aim for Python in both frontend and backend
Path B → Guidelines
Python must run IN THE BROWSER
No server-side dependencies for core functionality
Minimal JS for library initialization is acceptable
Should work offline when possible
No server-side dependencies for core functionality
Minimal JS for library initialization is acceptable
Should work offline when possible
Use Python-focused web frameworks
Server-side Python is encouraged
Let the framework handle web complexities
Server-side Python is encouraged
Let the framework handle web complexities
Path A → Guidelines
- 80%+ Python Logic: The majority of your application logic should be in Python
- Minimal Manual Web Languages: Avoid writing raw HTML/CSS/JS where possible (framework-generated is fine)
- Open Source: Use OSI-approved licenses
- 72-Hour Creation: Build during the hackathon window
Core Requirements
Technical Guidelines
Beautiful is better than ugly — Explicit is better than implicit — Simple is better than complex — Complex is better than complicated — Flat is better than nested — Sparse is better than dense — Readability counts — Special cases aren't special enough to break the rules — Although practicality beats purity — Errors should never pass silently — Unless explicitly silenced — In the face of ambiguity, refuse the temptation to guess — There should be one obvious way to do it — Although that way may not be obvious at first unless you're Dutch — Now is better than never — Although never is often better than right now — If the implementation is hard to explain, it's a bad idea — If the implementation is easy to explain, it may be a good idea — Namespaces are one honking great idea, let's do more of those
Remember: These are just suggestions. Build whatever excites you!
5
Creative CodingBuild generative art, music applications, or interactive visualizations. Show Python’s creative side!
4
Data Science StudiosCombine server frameworks with client-side Python for powerful data analysis tools that respect privacy.
3
Educational PlatformsInteractive lessons, code playgrounds, or quiz systems. Perfect for summer learning projects!
2
Real-Time DashboardsUse FastHTML’s reactivity or Streamlit’s auto-updates to build live dashboards. Financial trackers, monitoring systems, or analytics platforms.
1
Offline-First ApplicationsBuild PWAs that work completely offline using PyScript or Brython. Create note-taking apps, calculators, or games that never need a server.
These are just examples to inspire you—we accept all types of web applications!
Sample Challenge Tracks
Example Implementations
Path B: PyScript Calculator
Path A: FastHTML Todo App
Documentation:
Clear README with setup instructions and project description
Demo/Presentation:
Live demo URL preferred, video presentation required
Your project repository (GitHub, GitLab, etc.)
Source Code:
Submission Requirements
What to Submit
Sample Repository Structure
This is just a suggestion—organize your code however makes sense for your project!
/app
main.py # Main
application index.html # Entry point (if using Path B)
/static # Static assets
requirements.txt # Python dependencies
README.md # Project documentation
main.py # Main
application index.html # Entry point (if using Path B)
/static # Static assets
requirements.txt # Python dependencies
README.md # Project documentation
- Official documentation links
- Common patterns and best practices guide
- Step-by-step project walkthroughs
Other Resources
- FastHTML: https://www.fastht.ml/docs
- PyScript Examples: https://pyscript.com/@examples
- Discord Support: 24/7 help
Documentation
Important Resources
Renowned experts shape the industry and inspire innovation with unique perspectives — adding depth and credibility to the evaluation process
Judges You Should Know
Technical Artist with 10+ years in game dev and CG. Worked on AAA titles, built tools and pipelines (Python, MEL, C++), and founded a platform for game developers.
Israel
Ivan Roskin
Cloud/DevOps lead delivering 99.99% pipeline uptime and AI-driven CI/CD and observability stacks that shrink release cycles from hours to minutes.
United States
Vladyslav Haina
Senior Product Manager at Uptiq.ai with 8+ years of experience in embedded finance, data enrichment, automation, and business intelligence for the banking and financial services industry.
United States
Pavlo Martinovych
Lead Software Engineer specializing in high-performance, data-driven web platforms with strong technical leadership.
United States
Denys Riabchenko
2025 judge for the Globee Awards (Achievement & Disruptors) and Washington University of Science and Technology Hackathon, evaluating high-impact innovations across industry and academia.
United States
Karthikeyan Selvarajan
Praneeth Kamalaksha Patil
United States
Senior Staff Engineer at Equinix, focused on developer tools and AI integration with a decade of product leadership.
Beautiful is better than ugly — Explicit is better than implicit — Simple is better than complex — Complex is better than complicated — Flat is better than nested — Sparse is better than dense — Readability counts — Special cases aren't special enough to break the rules — Although practicality beats purity — Errors should never pass silently — Unless explicitly silenced — In the face of ambiguity, refuse the temptation to guess — There should be one obvious way to do it — Although that way may not be obvious at first unless you're Dutch — Now is better than never — Although never is often better than right now — If the implementation is hard to explain, it's a bad idea — If the implementation is easy to explain, it may be a good idea — Namespaces are one honking great idea, let's do more of those
72-Hour Timeline
August 1
August 1
Day 1
19:00 UTC
World Wide Web Day!
Start at 19:00 UTC, choose your approach, begin building
Start at 19:00 UTC, choose your approach, begin building
August 2
August 2
Day 2
Core development, add features, test functionality
August 3
August 3
Day 3
19:00 UTC
Polish, optimize, prepare presentation, submit by 19:00 UTC deadline
10%
Documentation
Clear setup instructions and code explanation
15%
User Experience
How polished/usable is the app with UI/UX principles
20%
Technical Excellence
Code quality, architecture, performance
25%
Creativity & Originality
Fresh ideas and unique implementations
30%
Python Mastery
How effectively you used Python for web development
Judging Criteria
Meet the Jury
A diverse panel of industry professionals ready to evaluate your ideas with fairness and insight. Each judge brings valuable experience to ensure every project gets the attention it deserves.
Winners will be announced 2 weeks after the hackathon wraps up.
Note:
$ 500
Community Choice
Chosen by public vote on LinkedIn one week after the hackathon. A chance for any team to shine with community support.
$ 200
Celebrates a project with great potential and solid execution, selected by the jury.
Third Place
$ 300
Second Place
Given to a high-performing team that demonstrated strong creativity and technical skills across the challenge.
$ 1000
First Place
Awarded to the most outstanding project as judged by our expert panel. Innovation, execution, and impact will lead the way.
Win rewards, recognition, and real opportunities to grow your idea.
Prizes
This hackathon proves Python can own the ENTIRE web stack—from server to browser. Whether you believe in framework simplicity (Path A) or browser autonomy (Path B), you’re showing that Python developers shouldn’t need to learn multiple languages to build for the web.
Why This Matters
Organized solely for social good [and fun] and designed by Hackathon Raptors. A non-profit community — UK [C.I.C] — 15 557 917.
#RaptorsHack
#PythonEverywhere
#WorldWideWebDay
#PyWebCreators
Register and join the Python web revolution!