01
Full-stack platforms
Customer-facing surface and operator-facing admin, built against one database. The product and the back-office are not separate projects.
- Next.js 16 · App Router
- Supabase · Postgres + Auth + Storage
- Vercel
Loading
Kagu
Custom websites and digital tools, built to fit your business.
What we build
Five things, done well.
Not a full-service menu. We say no to most of what we're asked, so the work we ship is the work we're known for.
02
Admin that staff use
Role-based content systems that non-technical operators actually open. Less CMS, more form.
- Supabase RLS
- Custom editor per surface
- Audit + soft-delete by default
03
Multilingual by default
Turkish + English first-class, not bolted on. Public copy and admin labels translated; routing per locale.
- Per-route locale
- Editorial translation, not auto-MT
- Right-to-left ready
04
Real-time, where it matters
Operator notifications via the channels the team already lives in: WhatsApp threads, Telegram channels, on-site dashboards.
- WhatsApp Business API
- Telegram bots
- Webhook + cron orchestration
05
Ship to production, fast
Vercel-first, free-tier compatible where possible. Production at the kickoff, not at the launch.
- Vercel · preview deploys
- Free-tier compatible
- Domain + CI on day one
Stack lineage · always
Selected work
Four operators, in production.
01 · Hospitality · Tourism · 2025
Sabrina Turizm
02 · Restaurants · Hospitality · 2025
UpperDeck
03 · SaaS · Operator tools · 2026
GenBuzz
04 · Services · Immigration · 2025
Vize Makinesi
Approach
Four steps. Same every time.
01
Listen
Before any code, we sit with the operators. We watch a shift. We read the messages they actually send each other. The brief on paper is rarely the brief in practice.
Map
We design the smallest system that solves the actual workflow. One database. Two surfaces. No microservices for a fifteen-person team.
Ship
Production in weeks, not quarters. The first deploy is real, on a real domain, the day kickoff ends. Every later week is a real release.
Hand off
An admin staff actually use. Documentation the team reads once. The handover is the moment we stop being needed, and the moment Kagu is most useful.
Studio
Kagu is small on purpose. The people who write the code are the people in the meetings. We work in hospitality, tourism, and operator-facing software, verticals where production is the deliverable, not the kickoff deck.
We build what operates, not what demos
If it doesn't survive a Friday-night shift, it's not done. Polish is for what the staff actually see every day.
Production is the deliverable
Not a kickoff deck. Not a Figma file. The thing live, on a real domain, with real users: that's the unit of progress.
Vertical depth compounds
We stay in hospitality, tourism, and operator tools. The fifth restaurant menu is faster, and better, than the first.
Small team is the feature
One throat to choke. No account managers. The people writing the code are the people in the meetings.