jstanbul
How we think, build, and grow together.
Inside jstanbul
Our Engineering Handbook is your all-access pass to see who we are, how we get things done, and why we’re so passionate about what we do.
We’re sharing our guiding principles, the way we collaborate as a team, and the agile methods that keep us pushing forward.Whether you’re just curious about our vibe or considering joining us, you’ll find everything you need here.
Team & Technology
Meet the people behind Jstanbul and explore the tools, frameworks, and creative technologies we use to craft unique digital experiences.Most studios added AI at the end of the process, where it writes code someone has already specified. We put it at the start, where the arguing happens. That is why our repositories are written to be read twice: once by the person joining on Monday, once by the model on every task. The second reader turned out to make the first one's job easier.
The TeamA multidisciplinary group of designers, developers, and storytellers who collaborate across time zones and ideas.
Our StackFrom React, Next.js and Tailwind to Node.js, Express and GSAP — we use tools that empower creativity and performance.
The Fourth SeatClaude works from the same rules we do: a file at the root of every repo saying which module owns the scrolling, and which traps have already cost us a bug. It writes fast. We still decide what ships.
How We Work
Learn about our workflow, agile practices, and the collaborative spirit that drives our projects from idea to launch.Our process blends structure and freedom. Agile principles keep us grounded in discipline, while creativity keeps us flexible. We plan, build, review, and iterate — always with empathy for users and clarity for our clients. Because for us, how we work is just as important as what we deliver.
Agile WorkflowWe iterate fast, test often, and improve continuously.
CollaborationDesign and development work side-by-side, not in silos — every pixel and line of code co-created.
TransparencyWe communicate openly, document decisions, and celebrate progress together.
IterationEvery delivery is a step forward — never final, always evolving.
ReviewNothing ships on trust. Every change goes through one gate — types, lint, both locales, tests, build — and the gate does not ask who wrote it.