A two-personteam, with nomiddle layer.
Khaing Myel Khant is a lead product engineer and Myat Min Thu is a fullstack developer. We work together from Yangon and Jakarta, and we put our names on everything we ship.
- Based
- Yangon · Jakarta
- People
- Two, no bench
- Products live
- Three
- Built with others
- Two
- Focus
- Product, platform, AI
01
How we got here
Yantaz is the name we use for the work we do together. It comes from the Pali word for machines, which is what software is when it is working.
We have shipped three products under it: qqPOS, PoPoTalk, and qqdraw. Each started as a problem we could see up close, was built in public, and is still running. That is the whole portfolio — no pitch decks, no concept work.
Keeping those products alive taught us more than building them did: what breaks at two in the morning, which screens people actually use, and what a support inbox sounds like. We bring that to everything we take on.
AI is the third thing we are known for. PoPoTalk scores live conversation in production, and agentic coding is how two people keep three products running while still taking on new work. The agents write the diffs; the specs, tests, and review decide what ships.
All three, in full, on the work page
Etymology
- Pali
- yanta
- Burmese
- ယန္တရား
- Meaning
- machines
The trailing z is a nod to Gen Z.
Smallon purpose.
Two people, no bench, no handoff. The two you meet are the two who design, build, and run the software — and the ones who answer when something breaks.
02
Rules we actually enforce
Not poster copy. These show up in code review, scope documents, and retros.
01
Say the hard thing early
We would rather disagree in week one than discover a misalignment in month six. Clear scope, clear trade-offs, no theatre.
02
Boring where it counts
Proven infrastructure and conventional defaults. Innovation belongs in your product, not in your deploy pipeline.
03
Ship, then measure
Production in the first week beats a perfect demo in the last. If a decision can be measured, we measure it.
04
Leave it runnable
Documentation, tests, and credentials are part of the deliverable. You should not need either of us to keep the thing alive.
And what we decline
- Renting out a bench. There is no team behind us to grow into your project.
- Ghost-written work. If we cannot say we built it, it does not go on this site.
- A surface we cannot keep alive. Small in production beats wide in slides.
03
The two of us
One engineer, one fullstack developer. Both of us read every message that arrives through this site.
01
Khaing Myel Khant
Lead Product Engineer
Entrepreneur as much as engineer. Leads product engineering at a startup in Yangon, and has taken products the whole way himself — first sketch, interface, data model, deploy, then the numbers and the support afterwards. Point of sale, realtime collaboration and AI conversation practice: different shapes, the same path, no handoff. Owns the whole product, because the hard decisions sit in the seam between the layers.
- Entrepreneurship
- Product building
- End-to-end ownership
02
Myat Min Thu
Fullstack Developer
Studies Information Systems at President University in Indonesia on a SEAL scholarship, with a data science focus. Builds mobile apps in Flutter — Dart, Riverpod and Firebase — and the API and data layer behind them. From Myanmar, now based in Jakarta; the work he wants is AI, machine learning, NLP and generative AI, where a model has to hold up inside a shipped product.
- Mobile engineering
- Data science
- Applied AI
04
Two bases,one working day
We work from Yangon and Jakarta, half an hour apart on the clock, and take calls in your time zone where the hours allow. Anything that would otherwise wait for an overlap gets written down instead.
Half an hour of clock separates the two bases, so the whole team keeps the same working day.
Two of the sites we helped other teams build are on the work page.
Worked with
- Singapore
- Thailand
- Japan
- South Korea
- Vietnam
- China
- Taiwan
- Hong Kong
- Malaysia
People we have worked with — not places we keep an office.
05
How this siteis made
The same standard we hold the products to: typed content, no page builder, nothing running that nobody maintains. Every line below can be checked in the repository.
- Framework
- Next.js 16 with the App Router and cache components on. Static by default, so there is no database to keep alive.
- Language
- TypeScript in strict mode. Content is typed data rather than a CMS, so a typo fails the build instead of shipping.
- Styling
- Tailwind CSS 4 over one @theme token set: canvas, surface, surface-2, night, accent.
- Motion
- Motion for React, one easing curve for the whole site, and every reveal skipped under prefers-reduced-motion.
- Type
- Archivo for text, IBM Plex Mono for numerals, Noto Sans Myanmar for Burmese — self-hosted through next/font.
- Map
- Natural Earth 1:50m boundaries, projected and simplified by a script in the repository. Generated, never hand-drawn.
- Screenshots
- Captured from the live sites at 1440×900 and twice the pixel density, then shipped as captured.
- Build
- Bun for scripts and the build. No analytics and no tracking script anywhere in the bundle.
06What we believe
Three products that runbeat ten that demo.
Every product linked from this site is live and has users. That is the bar we hold new work to as well — a small surface in production, kept working, rather than a wide one in slides.
Say hello,or follow the work.
What you are working on, a question about a product, or a note on something we wrote. One of us reads it and replies within one business day.
Working together
- StatusOpen to collaboration
- Reply timeOne business day
- Time zoneUTC+06:30 – UTC+07:00
- Based inYangon · Jakarta
Both of us read every message. There is no queue and no assistant in between.