Built for unreliable connections
A custom bidirectional sync layer keeps the mobile product useful when the network does not.
Alireza Jalili · Founder / Engineer
A decade of building.Still hands-on.
I have moved from Android ROMs and high-traffic infrastructure to cloud products, trust platforms, and travel software. Today I am building TourOn end to end with a multi-agent system I designed to think, execute, and ship alongside me.
Product decisions stay human. Specialized agents turn them into mobile, backend, and infrastructure work.
01
Current focus
Active flagship · 2026
TourOn is where the whole path converges.
PlanChin began with the awkward math inside group trips. TourOn expands that foundation into a Persian-first platform for discovering tours, coordinating travel, and giving tour leaders a proper operating tool.
Groups and tour leaders, one system
Expense coordination, tour discovery, booking, and operator workflows meet in one product.
AI-native, founder-directed
Frontier models help plan. Specialized agents execute. I own the product calls, architecture, and quality bar.
02
The build log
Different problems. One continuous practice.
The job title changed over the years. The habit did not: find the hard part, learn the system, and stay close enough to the work to make it real.
- 01
First online business
Romfa
Built and sold Persian custom Android ROMs, added Persian support, and ported newer releases to phones manufacturers had left behind. - 02
Part · GreenWeb · Ferdowsi Cloud
Infrastructure
Scaled iSignal from 300K to more than one million users without downtime, designed a CDN, and helped build OpenStack cloud services. - 03
Crowd-sourced trust
Motabare
Built a platform where people shared real purchase experiences with websites, Instagram shops, and Telegram channels. - 04
Product thesis
PlanChin
Turned group expense coordination into a focused product, then used what it taught me as the foundation for TourOn. - 05
The active chapter
TourOn
Rebuilding the travel stack around mobile, offline-first systems, a marketplace, and an AI-native development workflow.
03
How the work moves
The product is not the only system I build.
To stay genuinely hands-on across product, mobile, backend, and infrastructure, I designed a development operating system around clear contracts and explicit ownership.
Reason
Frontier models
Explore trade-offs, challenge assumptions, and turn product intent into architecture.
Execute
Specialized agents
Ship bounded work across mobile, backend, infrastructure, quality, and documentation.
Decide
Founder in the loop
Every important product call, integration decision, and release standard comes back to me.
It is not automation for its own sake. It is a way to protect depth while increasing the surface area I can build.
Open channel
If the problem is worth building, I am always up for a serious conversation.
Product, infrastructure, AI-native delivery, or the strange territory where all three overlap.