Relaynexa
WhatsApp-first customer support automation platform for e-commerce brands.
WhatsApp bots, RAG assistants, backend APIs, Android apps — mostly things that automate whatever is eating up too much time.
"Sipariş #4721 kargoda.
Tahmini teslimat: 2-3 iş günü."
I am a 4th-year Electrical and Electronics Engineering student at Bülent Ecevit University. I started programming in high school with C#, and over time I worked with Python, backend development, Android development with Kotlin, and AI-based systems.
During university, I focused especially on backend architecture, API development, data flow, mobile application logic, and building software around real problems. While developing Android projects with Kotlin, I also improved myself in Python-based AI, automation, RAG, and LLM-powered systems.
Today, I position myself as a developer who can think across backend, Android, and AI instead of being limited to only one area. In a project, I care not only about the interface, but also where the data comes from, how the API works, how the mobile experience connects, and how AI can be integrated safely into the system.
My goal is not to build things that only look impressive. I aim to build understandable, sustainable, and actually usable software products.
Instead of keeping my projects only in a local environment, I have also gained practical experience deploying them with AWS EC2, Linux servers, Nginx, domain/DNS configuration, and production deployment workflows.
Alongside my technical work, I am also building Relaynexa, an AI automation initiative focused on helping e-commerce brands manage customer communication more efficiently through WhatsApp-based support flows.
Relaynexa is an AI automation initiative I'm building to help e-commerce brands handle customer communication without growing their support team.
Most e-commerce brands face the same problem: customer support is repetitive, volume-heavy, and eats into the team's time. Relaynexa is my answer to that — a WhatsApp-first AI platform that handles order tracking, shipping questions, returns, and product inquiries automatically.
Mostly these kinds of things:
I build systems that read incoming messages, pull from a knowledge base, and respond accurately — without needing someone to sit there and do it.
Good option if support is taking up too much manual time.
End-to-end WhatsApp automation for queries, order tracking, lead capture, and notifications — connected directly to your data.
Works on the channel your users are already on.
You upload the docs — contracts, catalogs, manuals — and I build an AI that can actually answer questions from them accurately, with sources.
Useful when you have a lot of documents people keep asking about.
FastAPI with PostgreSQL, auth, background jobs, clean structure. Built to be extended without rewriting everything six months later.
A solid base for whatever comes next.
React frontend, backend API, admin panel — I build it all together. Fast, straightforward, and actually usable.
A working product, not a proof of concept.
Native Android in Kotlin, with Firebase, Maps, and device features where needed. I think about the UX from the start, not as an afterthought.
When the problem really needs to be on mobile.
Pipelines, notifications, reporting, manual workflows — I automate the repetitive stuff so the team can focus on actual work.
Time saved that adds up week after week.
Systems built to solve specific problems — not just to demonstrate skills.
WhatsApp-first customer support automation platform for e-commerce brands.
Writing-based personality analysis API with FastAPI, PostgreSQL and GPT-4o-mini.
AI health assistant built with RAG, BERT, FAISS, FastAPI and OpenAI function calling.
Real-time meeting subtitle and English-to-Turkish translation system using Whisper and GPT.
AI-powered WhatsApp appointment assistant for dental clinics.
RAG-powered CV analyzer and talent matching system for recruiters.
Google Play-published AI English learning app built to improve speaking, listening, vocabulary and real-life language practice.
Discord-like Android communication app built with Kotlin.
Kotlin Android app for taxi driver workflow management.
Income and expense tracking Android app built with MVVM architecture.
Here's roughly how a project goes:
I don't write code until I know what's actually being solved. A lot of bad projects start with skipping this.
Data models, API contracts, integrations — I think this through before building. It saves a lot of painful backtracking later.
FastAPI, PostgreSQL, auth, business logic — tested and structured to be extended without rewriting.
RAG pipelines, chatbots, function calling — only where they actually help, not just because it's cool.
React frontends and admin dashboards made for the actual user, not a generic template.
Real scenarios, edge cases, load testing — then small improvements based on real behavior.
I've seen projects fail not because of bad code, but because the wrong thing got built. I try really hard not to do that.
I need to know what's actually being solved before I write anything. Code that doesn't address the real problem isn't worth shipping.
I've seen systems that looked great in demos but fell apart with real users. I think about edge cases and reliability from the start.
Backend, AI, frontend, mobile — I can design and build all of it. No handoffs, no gaps, no 'that's not my part.'
Clean structure, proper data models, documented APIs. What I build can be maintained, extended, and handed off without starting from scratch.
If you're interested in my projects, want to discuss a collaboration, or simply want to reach out, you can contact me through the links below.
Contact Me