01
Engineers first
Every session brings real code, real numbers, a metric, a failure mode, an eval lesson, a design choice, or a hard-earned production insight.
§ 05 / about
Why we built this.
LatentShift is a one-day conference by engineers, for engineers shipping AI in production. Here's why it exists, what we stand for, and the three people putting it together.
§ 01 / why we exist
Why LatentShift exists
the gap
AI events often show the polished ending: the launch demo, the keynote, the roadmap, the big promise. But AI in production is mostly built in the middle: datasets, evals, model behavior, fine-tuning decisions, retrieval quality, pipeline bugs, latency, cost, drift, debugging, and all the trade-offs that happen before something actually works.
LatentShift exists for that middle part. We started it because it was the conference we wanted to attend and could not find: one focused day in Istanbul, where people working on production AI can share what they ran into, what they learned, and what finally worked.
The conference we kept waiting for someone else to build, so we built it.
§ 02 / what makes latentshift different
What makes LatentShift different
engineers first
02
A focused experience
One stage, one day, tightly curated. You won't juggle five parallel tracks or get lost on a trade-show floor.
03
Real production stories
We care about what actually happened: the model that drifted, the eval that misled you, the pipeline that broke, the cost spike, the debugging path, and what finally worked.
§ 03 / what we value
What we value
lowering the barrier
Knowledge shouldn't sit behind a paywall or a seniority gate. We keep LatentShift accessible to students and working engineers alike, and we design every part of it to lower the barrier to learning, not raise it.
That's a promise we'd rather be held to than just state, so here's what it looks like in practice:
// commitments
- Student & community tickets kept deliberately affordable.
- Every talk recorded and published free, for the people who couldn’t be in the room.
- Bilingual on one stage: Türkçe and English.
- Captioning on stage, step-free access, a quiet room.
- A real code of conduct, with a committee behind it. read it →
§ 04 / who's behind this
Who's behind this
three organizers, three reasons
Bilge Gündüz
ML Engineer
“I’m drawn to the hard, often overlooked parts of running AI in production, and I want LatentShift to be a space where we share what works, what breaks, and grow together as a community.”
Ayşe Aktağ
Cyber Security Architect
“I’m motivated to help organize this because I want to create the kind of atmosphere I often missed at other events: a space for genuine discussions, real collaboration, interdisciplinary thinking, and meaningful community value, while keeping it student-friendly and accessible.”
Mehmet İnce
CTO
“LatentShift is going to be a place where people talk honestly about what broke, what failed, what surprised them, and what they learned when AI met the real world.”
§ 05 / what you'll leave with
What you'll leave with
the promise
practical knowledge
Patterns and fixes you can put to work on Monday morning.
new ideas
Approaches you hadn’t considered, from people solving adjacent problems.
new connections
The engineers behind the work, not just their slides.
honest lessons
What didn’t work, told plainly, so you don’t learn it the expensive way.
a community
Proof you’re not the only one fighting these problems. You’re part of something.