Kryp Ticket
🚀A Peer-to-Peer Help Desk Built for ETNA Students
Starting a new tech school can be overwhelming — new people, unfamiliar concepts, and a strong emphasis on self-guided learning. At ETNA, where peer learning is at the heart of everything (think École 42), my friends and I saw an opportunity: how could we reduce friction for students seeking help, and at the same time, strengthen our student network?
That’s how KRYP Ticket was born — a lightweight, Discord-connected ticket system for students to ask for help and connect with more experienced peers.
🧠 The Idea
We were four students — Khai, Roland, Y, and P — just starting our prépa year at ETNA. We noticed that many classmates felt isolated when tackling new programming concepts or projects. While asking for help in Discord was encouraged, the signal-to-noise ratio was high.
So we built a platform that formalized the help request process while keeping things casual and Discord-native:
- Login with Discord
- Create a ticket: Add a title, category, and markdown-supported description
- Ticket is sent to a Discord channel via webhook
- Assistance continues in private messages
- Ticket gets closed once resolved
It was meant to be simple, familiar, and accessible to everyone — especially those still finding their footing.
🛠️ Tech Stack & Implementation
KRYP Ticket was my first ever public project, and I learned a ton during development:
- Frontend: Built with Next.js using the Pages Router (the App Router didn’t exist yet!)
- Backend: Supabase for user data and storage
- Auth: Discord OAuth
- API layer: tRPC for typesafe communication between frontend and backend
- Webhook: To notify assistants on Discord when a new ticket is created
- Admin features: Role-based access to a dashboard
It was a full-stack playground, and looking back, I’m proud of how clean and accessible the experience was.
🧪 The Experience
Despite being a side project launched at the start of the school year, KRYP Ticket had real engagement:
- 📅 7 tickets opened the day we announced it to our promo
- 🕓 Continued usage for 2–3 weeks
- 👥 Positive feedback — not just about the help, but about making new friends
That last point surprised us — KRYP Ticket wasn’t just a help desk; it helped people form study groups, chat in private, and get comfortable talking to more experienced students.
💡 What I Learned
- How to build with Next.js from scratch
- How to manage authentication via Discord
- How to use tRPC for typesafe data fetching and mutations
- Designing user flows that fit naturally into existing student habits
- The value of ship-first, iterate-later — especially for internal tools
🧱 What I Would Improve Today
If I were to rebuild KRYP Ticket now, I’d probably:
- Use the App Router and React Server Components
- Add real-time updates via Supabase’s live queries or WebSockets
- Let assistants claim tickets and manage their status
- Add a more persistent history of interactions
But for a first project, made in just a few weeks, it served its purpose perfectly — and we had a blast building it.