We build the systemsother systems depend on.
A Kathmandu product studio. We build AI tools, web platforms, storefronts and the operations systems behind them, for businesses and audiences here in Nepal and beyond.
Ten years of shipping platforms that carry real load.
Most studios show you a mood board. We show you a ledger: twelve products across nine sectors, from an AI builder that turns a sentence into a live website to the operations system running a resort in far-western Nepal.
We are small on purpose. Senior engineers own architecture, code and operations end to end. No hand-offs, no layers, no decks that outlive the product.
From terrain to structure.
Every platform in the ledger started as a messy landscape: regulations, legacy data, people under pressure. We turn it into something with edges, indexes and audit trails.
Five we would build again tomorrow.
ChittoWeb
AI / SaaS · 2025 —Describe your business in a sentence and it designs, builds and publishes a working website in about thirty seconds.
Chitrakar
AI / SaaS · 2026 —An AI creative director that turns a short brief into finished ads and social assets for Nepali businesses.
Sudurpashchim Resort
Hospitality · 2025Booking flow and public site for a luxury resort in far-western Nepal, with live availability across three room tiers.
NepCase
Commerce · 2025Phone case retail across all seven provinces: catalogue, cart, cash on delivery and order tracking.
MeroGantabya
Travel · in developmentTravel discovery across all 77 districts, with separate journeys for Nepali citizens and international travellers.
- A
AI products people actually use
→We build AI into products that ship, not demos. ChittoWeb turns a plain sentence into a published website. Chitrakar generates ad creative from a brief. Both run in production for Nepali businesses.
- B
Web platforms & SaaS
→Full-stack products with accounts, billing, dashboards and an admin nobody dreads. Go, Next.js, Laravel and Vue, chosen for what the product needs rather than what is fashionable.
- C
Storefronts & marketplaces
→Catalogues, carts, checkout and order tracking built for how Nepal actually buys: cash on delivery, nationwide shipping, and marketplaces that pay creators directly.
- D
Systems that run the business
→Back-office platforms for teams doing physical work. Reservations, housekeeping, inventory, staffing and billing, unified so one small team can run an entire property.
- E
Sites that bring in work
→Fast, well-built sites for firms whose customers arrive through search and referral. Portfolios, product catalogues, booking flows and enquiry routing that actually converts.
- F
Platforms with an audience
→Products built for scale and habit: readers, tournament platforms, creator tools and travel discovery. Web and mobile, built to hold traffic and keep people coming back.
Everything connected. Nothing exposed.
Identity, permissions and observability are designed in on day one, so the system can grow without growing its attack surface.
We start at 3 a.m., not at the launch.
Anyone can demo a system on a good day. We design for the bad ones first, then work backwards to the architecture that survives them.
- 01When
the queue backs up at 3 a.m. and nobody is awake
We already builtMetrics, structured logs and alert routing from the first deploy, with runbooks that name the person to call.
- 02When
a vendor changes their API without telling you
We already builtAdapters at every boundary and contract tests that fail loudly in CI rather than silently in production.
- 03When
a regulator asks for two years of evidence
We already builtImmutable audit trails and automated evidence collection, so the answer is an export rather than a project.
- 04When
the engineer who understood it leaves
We already builtDecision records, documented APIs and a codebase a new senior can read on day one. That is what developer-first means.
- 05When
traffic multiplies without warning
We already builtLoad-tested paths, queue-backed writes and horizontal scaling proven before launch, not improvised after it.