Six challenges. One hackathon. Developers, students and innovators building practical intelligent solutions for a safer and more resilient digital future.
AEGLYSAI INTELLIGENCE NETWORK
Select a domain to explore its connections.
CONCEPTUAL EXAMPLES · NO LIVE TELEMETRY Select with Enter / Space · Arrow keys pan the view
PROJECT SUBMISSIONS OPEN · AEGYTHON 2026
Your project deserves to be seen.
Registration has closed. Qualified teams can now submit their working AI/ML projects for finalist consideration.
Registration & Qualification: Oct 1 – Nov 6, 2026 — Closed
Project Submission & Finalist Selection: Nov 15 – Nov 22, 2026 — Active
Grand Finale: Nov 28, 2026 — Upcoming
01ONE HACKATHON
02SIX CHALLENGES
03TEAMS OF 1–4
04FREE PARTICIPATION
05ANY TECH STACK
06TWO-ROUND JUDGING
THE NEXT GENERATION OF BUILDERS
Intelligence is powerful. Make it useful. Make it safe.
From suspicious logins to everyday human problems, this is an invitation to turn curiosity into working software. Choose a practical problem, explain your decisions and show the evidence.
An international-facing invitation. Geographic and age eligibility remain TBA; no countries, partners or participants are confirmed here.
SIX CHALLENGES / ONE HACKATHON
Six ways to build what comes next.
Registration & Qualification: Oct 1 – Nov 6, 2026 Project Submission & Finalist Qualification: Nov 15 – Nov 22, 2026 Grand Finale: Nov 28, 2026
AEGYTHON 2026. Explore security problems across authorization, identity, risk, observability and incident response. Challenge themes describe work to investigate, not validated platform capabilities. Model D research implementation is complete, experimental and non-enforcing; it is not required for qualification.
Challenge 01Beginner-friendly
Smart Login Guardian
Recognize suspicious synthetic login attempts and explain the risk signals.
Explore cloud security and AI/ML concepts through practical engineering questions.
BUILD
Create a working prototype with a clear problem, useful output and reproducible evidence.
COMPETE
Receive technical evaluation through two distinct rounds of judging.
CONNECT
Collaborate with individually qualified and selected teammates.
SHOWCASE
Build a portfolio-ready prototype. Public event showcases require consent and organizer approval.
GROW
Become part of the AeglysAI developer community through issues, documentation and reviewed contributions.
For people who build and investigate
University students, graduate students, early-career engineers and experienced practitioners can explore the same engineering questions at different depth.
Platform Engineers
Cloud Engineers
Security Engineers
Distributed Systems Engineers
SREs
Software Engineers
AI/ML Engineers
Researchers
Graduate Students
Intelligent security
Build executable behavior, explain its decisions and validate it using authorized synthetic or licensed inputs.
Reproducible engineering
Document setup, tests, attribution and limitations so reviewers can run your project.
MORE THAN A COMPETITION
A community engineering rhythm.
Proposed activities across the build window. Sessions, mentor capacity and discussion arrangements are unconfirmed; dates and accessible alternatives will be announced when available. Shortlisted finalists demonstrate live over Google Meet in Round 2.
PLANNED
Kickoff
PLANNED
Technical Workshop
PLANNED
Architecture Clinic
PLANNED
Mentor Office Hours
PLANNED
Midpoint Checkpoint
PLANNED
GitHub Discussions
PLANNED
Demo Day
PLANNED
Final Showcase
GitHub remains the primary engineering community platform. After the event, continue through issues, documentation and reviewed contributions. Mentorship and showcases depend on availability and permission; no outcomes are guaranteed.
DIFFERENT DEPTH / THE SAME ENGINEERING QUESTION
Find your starting point.
FOUNDATION TRACK
Students · Early-career engineers · First-time contributors
Build a focused prototype, explain its architecture and demonstrate predictable behavior with clear tests.
ADVANCED TRACK
Experienced engineers · Graduate researchers · Advanced students
Evaluate deeper engineering tradeoffs, compare approaches and document uncertainty with reproducible experiments.
Both tracks value correctness, security reasoning and clear evidence. Final prerequisites, track-specific evaluation and award allocation are pending.
THE QUALIFICATION PATHWAY
Earn your place. Start with evidence.
Mandatory individual qualification for every participant, including every team member. The A/B/C baseline is sufficient; Model D knowledge is not required. Qualification does not guarantee selection.
Registration and qualification intake are closed. These steps remain available as reference for qualified participants.
01
REGISTER
Register individually through the official Google Form.
02
FORK AEGLYSAI
Fork the official repository into your own GitHub account.
03
CLONE & RUN
Clone your own fork; demonstrate the baseline builds/runs.
04
UNDERSTAND & DOCUMENT
Document architecture, setup, an observation, an improvement and validation.
05
SUBMIT EVIDENCE
Send your GitHub username, fork, branch, qualification document and sanitized build-log URLs.
06
ORGANIZER REVIEW
Organizer review against published criteria; qualification does not guarantee selection.
07
BUILD & COMPETE
Develop a scoped challenge with reproducible evidence.
Registration & Qualification: Oct 1 – Nov 6, 2026 Project Submission & Finalist Qualification: Nov 15 – Nov 22, 2026 Grand Finale: Nov 28, 2026
Google Forms handles intake; private Google Sheets and Drive support organizer review. Teams of one to four include the team leader; every member must be individually qualified and selected. Registration confirmation, qualification review and project-submission receipt are separate steps. No private application data is published here.
Only selected participants form a team. One leader submits its unique roster for private organizer verification; no duplicate active membership. Changes need organizer approval.
Registration and qualification intake are closed. Unstop and Luma remain event-discovery resources; external listings do not reopen intake or indicate organizer selection. Qualified teams should use the official project submission form.
External listings may show different dates, locations, eligibility or prize details. This official AeglysAI page remains authoritative; Registration & Qualification: Oct 1 – Nov 6, 2026. Project Submission & Finalist Qualification: Nov 15 – Nov 22, 2026. Grand Finale: Nov 28, 2026. Submission deadline: November 22, 2026 — end of day. The exact cutoff timezone has not yet been confirmed by organizers. Age and geographic eligibility remain subject to official terms.
Before selection, applicants demonstrate they can fork, clone and run AeglysAI, understand its basic architecture, provide one meaningful technical observation, suggest one realistic improvement and explain how to validate it. Qualification is not a LeetCode-style elimination exercise. Qualification is mandatory for every team member and does not guarantee selection. The A/B/C baseline is sufficient; Model D knowledge is not required.
01
Fork the repository
Work in your own fork. Participants do not receive write access to the official repository.
02
Clone locally
Clone your fork into a local working directory; keep secrets and private data out of Git.
03
Build and run
Use the current AeglysAI README for prerequisites and supported setup. Retain commands and observed evidence.
04
Understand the architecture
Describe key components, policy boundaries and the request/decision flow in your own words.
05
Make one technical observation
Describe something you observed, how you tested it and any limitations.
06
Suggest one improvement
Explain a realistic scoped change, its value and how you would validate it. A contribution does not require an accepted upstream PR.
Your fork. Your evidence.
Fork AeglysAI on GitHub, clone your own fork and follow the official repository setup instructions. Participants do not receive write access to the official repository or official main.
Create qualification/<github-username> in your fork, for example qualification/example-user. Record evidence in community/qualification/<github-username>.md: environment, OS, runtime, actual build/test results, architecture understanding, technical observation, improvement idea, engineering value and validation approach. Never use emails, phone numbers, student IDs or other PII in branch names.
Qualification intake is closed. The following evidence requirements remain available for reference. Push to your fork. Submit your GitHub username, fork URL, qualification branch URL and qualification file URL and sanitized build-log URLs through the official Google Form. Organizer review uses published selection criteria; completing qualification does not guarantee selection.
Selected participants build in their own forks under hackathon/<team-id>. The organizer issues team IDs and verifies individual qualification and selection in private Google Sheets. No duplicate active team membership; changes require organizer approval. Final submission does not guarantee an AeglysAI merge. An optional upstream PR retains normal maintainer review.
Use Google Forms for registration, qualification and final submission, private Google Sheets for applicants/teams/judging, private Google Drive for supporting evidence and Google Meet for finalist presentations. No accounts, database or private-data API. Never publish private participant, credential or patent-related data.
Submit QualificationQualification Intake Closed
THE COMPETITION JOURNEY
From application to the final demo.
Three phases. Qualification establishes readiness; competition judging evaluates the finished project.
Phase 1
Registration & Technical Qualification
–
Participants register, complete mandatory technical qualification requirements and submit qualification evidence for organizer review.
Online
Phase 2
Project Submission & Finalist Qualification
–
Qualified participants submit their project or prototype along with the required evidence and demonstration material. Judges evaluate eligible submissions and select finalists.
Virtual judging and finalist selection
Phase 3
Grand Finale
Selected finalists demonstrate their solutions and present their work to the judging panel.
Hybrid — Online & On-site
Final submissions require a working project. Prepare the full checklist before submitting. Submission deadline: November 22, 2026 — end of day. The exact cutoff timezone has not yet been confirmed by organizers.
Grand Finale: November 28, 2026 — Hybrid (Online & On-site). On-site venue details will be announced separately.
FIRST-PLACE SPOTLIGHT · USD
$300
PROPOSED AWARD — SUBJECT TO CONFIRMATION
Build for the breakthrough.
Planned award; funding is unconfirmed. Final prize structure to be announced. The first-place spotlight is a proposed presentation, not an approved allocation.
Prize eligibility and payment are subject to official event rules. Award allocation requires organizer approval.
Event schedule: Registration & Qualification: Oct 1 – Nov 6, 2026. Project Submission & Finalist Qualification: Nov 15 – Nov 22, 2026. Grand Finale: Nov 28, 2026. Exact session times will be announced separately.
Prize details subject to official event rules. Prizes and rules are subject to official event terms until finalized. No prize has been awarded.
RECOGNITION WITH EVIDENCE
Build. Demonstrate. Earn Recognition.
Showcase your technical skills through a working AI/ML project and receive recognition according to the official hackathon eligibility and award criteria.
Registration alone does not earn a certificate. Every category requires its own eligibility review and separate organizer approval. No issued certificates or approved results are represented here.
AEGLYSAICOMMUNITY ENGINEERING
SAMPLE CERTIFICATE
AEGYTHON 2026
Certificate of Recognition
AEGYTHON 2026
THIS SAMPLE IS PRESENTED TO
Sample Recipient
[Certificate Category]
In recognition of technical participation and contributions to a working AI/ML project. Actual recognition requires verified eligibility and organizer approval.
Individual A/B/C qualification evidence accepted by the organizer. Qualification alone does not establish competition selection or hackathon participation.
Separate organizer approval required.
Hackathon Participant
Individually qualified and selected, with approved team membership and a valid working final project meeting the published requirements.
Separate organizer approval required.
Finalist
Official Round 1 finalist selection and completion of the required finalist participation steps.
Separate organizer approval required.
Winner
Official final ranking approved after Round 2 judging, conflict review and any applicable tie resolution.
Separate organizer approval required.
Judge Appreciation
Confirmed judge who completed assigned reviews and conflict-of-interest requirements; organizer verifies service.
Separate organizer approval required.
Speaker Appreciation
Confirmed speaker who delivered the approved session; invitation or acceptance alone is insufficient.
Separate organizer approval required.
Guest Appreciation
Confirmed guest whose actual participation meets organizer-approved guest criteria; invitation alone is insufficient.
Separate organizer approval required.
Mentor Appreciation
Confirmed mentor who provided the agreed mentoring support; organizer verifies service.
Separate organizer approval required.
Issuance, consent, supporting evidence and correction records stay in private Google Sheets and Drive. Certificate verification and issuance details will be communicated through official AEGYTHON channels.
Individual entry and teams
Individuals may compete; teams may contain two to four participants, maximum four.
Every member, including the leader, must individually complete qualification and be selected.
Designate one team leader and obtain a unique team ID from the organizer.
No duplicate active team membership; membership changes require organizer approval.
Organizers verify rosters in private Google Sheets; roster mappings are never public.
Every project must be a working MVP, executable prototype or functional proof of concept. A slide deck or documented walkthrough alone is insufficient. Any programming language or framework; standalone implementations are acceptable after mandatory AeglysAI qualification.
Team ID
Selected challenge
Public GitHub source URL and frozen review commit/tag
Project README
Reproduction/setup instructions
Working demonstration video URL — maximum two minutes
Explanation of AI/ML or intelligent technique
Test or validation evidence
Data/model attribution and licensing
Known limitations
Narrated screen recordings or silent captioned demonstrations are accepted. Webcam footage is not mandatory. A deployed demo URL is optional. Submit only sanitized evidence; no private participant, credential or patent-related data.
Virtual project review and finalist selection: November 15 – November 22, 2026. Exact session times will be announced separately.
Submission deadline: November 22, 2026 — end of day. The exact cutoff timezone has not yet been confirmed by organizers.
ROUND 01 / 100 POINTS
Round 1 — technical screening
Review source code, working prototype, required video and reproducibility. Round 1 determines finalist selection.
Working functionality — 30 points
AI/ML or intelligent feature — 25 points
Relevance and creativity — 20 points
Reproducibility — 15 points
Video clarity — 10 points
ROUND 02 / 100 POINTS
Round 2 — finalist demonstration
Shortlisted finalists give a five-minute live demonstration over Google Meet followed by five minutes of technical Q&A. Round 2 determines final ranking; do not combine round scores.
Live demonstration — 35 points
Technical understanding — 25 points
Solution quality and safety — 20 points
Technical Q&A — 15 points
Presentation — 5 points
Proposed capacity: five to ten finalist teams, subject to submission quality and organizer capacity. This is not a guaranteed finalist count. Each rubric totals 100 points; equally weighted, non-conflicted judges score independently and their scores are averaged within each round.
Round 1 ties: functionality, intelligent feature, then reproducibility. Round 2 ties: live demonstration, technical understanding, then solution quality and safety. Remaining ties receive equal additional demonstration/Q&A and independent panel review; unresolved ties receive a shared rank with any capacity decision explained under published rules.
Reviewers disclose conflicts privately and recuse; organizers assign unconflicted replacements. Technical clarification uses equivalent time and scope, is logged privately and cannot permit undisclosed post-deadline feature development. Scores, roster mappings and private comments remain in private Google Sheets/Drive. Judge appointments and results are not confirmed.
ENGINEERING PERSPECTIVES
Speakers
Speaker appointments will be announced only after confirmation and approval to display their profiles.
Additional speaker sessions will be announced only after confirmation and permission to publish.
Invited guests may respond through the official guest response form. An invitation or response does not establish attendance. Only confirmed, publication-approved profiles are displayed.
When are registration, qualification and the grand finale?
Registration & Qualification: Oct 1 – Nov 6, 2026. Project Submission & Finalist Qualification: Nov 15 – Nov 22, 2026. Grand Finale: Nov 28, 2026. Registration and qualification intake are closed. Qualified teams can submit their project now. Submission deadline: November 22, 2026 — end of day. The exact cutoff timezone has not yet been confirmed by organizers.
When are projects judged?
Virtual project review and finalist selection: November 15 – November 22, 2026. Exact session times will be announced separately.
Where is the grand finale?
Grand Finale: November 28, 2026 — Hybrid (Online & On-site). On-site venue details will be announced separately.
How will certificate verification and issuance details be shared?
Certificate verification and issuance details will be communicated through official AEGYTHON channels.
Is participation free?
Participation is FREE. Final eligibility and event terms will be published by organizers; they remain pending despite registration-link availability.
Who can participate?
Students, engineers and researchers are welcome to explore the program. Age and geographic eligibility are TBD.
Can students participate?
Students are part of the intended audience. The Foundation track is designed for students and first-time contributors; final eligibility is TBD.
Can I join individually or as a team?
Individuals and teams of two to four may enter. Every member must individually qualify and be selected; designate one leader and obtain a unique team ID. No duplicate active membership; changes need organizer approval.
Do I need prior AeglysAI experience?
AI for Everyday Life is beginner-to-intermediate; the Foundation track supports newcomers. Read the current repository setup guide; the A/B/C baseline is sufficient; Model D knowledge is not required. Qualification is mandatory and does not guarantee selection.
What technologies can I use?
Choose from six Portal challenges, including AI for Everyday Life. Any programming language or framework. Standalone final implementations are acceptable after mandatory AeglysAI qualification. Work in an authorized, isolated environment.
Is the project open source?
AeglysAI is an open-source initiative. Final projects require a public GitHub source URL, attribution and licensing.
How are winners selected?
Round 1 technical screening selects finalists; Round 2 live demonstrations and Q&A determine final ranking. Scores are not combined.
What is the prize?
An existing planned USD $300 prize, with funding unconfirmed. Prize eligibility and payment are subject to official event rules.
Can international participants participate?
TBD. Geographic eligibility and prize conditions must be finalized by organizers; registration-link availability does not confirm geographic eligibility.
How do I become a judge or speaker?
Use the relevant official interest form. An application is not a confirmed appointment; public profiles need confirmation and permission.
Code of Conduct
Treat others respectfully, welcome different backgrounds and experience levels, give constructive feedback, and credit collaborators and prior work. Harassment, discrimination and intimidation are unacceptable.
Test only systems and data you are authorized to use. Keep credentials and personal information out of submissions. Report vulnerabilities privately to the affected maintainer rather than exposing sensitive details publicly.
Reporting contact and enforcement procedure remain pending despite registration-link availability; official event terms require organizer completion. Do not post conduct reports or sensitive vulnerability details in public submissions.
Free participation Registration & Qualification: Oct 1 – Nov 6, 2026 Project Submission & Finalist Qualification: Nov 15 – Nov 22, 2026 Grand Finale: Nov 28, 2026 Eligibility and official terms pending