Studio / Who builds this

Small on purpose.Senior by default.

The mark · 18,000 points

A senior-led engineering studio in Kathmandu. Two founders, a decade of platforms, and a bias for systems that stay boring.

01 / Origin2015 → today

Founded in Kathmandu in 2015 by engineers who kept getting the hard tickets.

WTN grew out of a decade of hands-on product work in Kathmandu. We have built AI tools, storefronts, booking systems and consumer platforms, and we have run them in production afterwards rather than handing over a repository and walking away.

Today the studio is focused on AI products: ChittoWeb turning a sentence into a live website, Chitrakar turning a brief into finished ad creative. The older muscles, Laravel, Vue and Flutter, still work, and they still ship.

We believe in automation, clean architecture and developer-first design, because the people who maintain a system decide whether it lives.

Survey — The pack

Two founders. One pack.

Every engagement is run by the people whose names are on it. No account layer, no hand-off, no drift between what was promised and what ships.

02 / TeamTwo people answer the phone

No account managers. Two founders who answer the phone.

The IO

CEO & Founder

Runs the studio: clients, scope, delivery and the promises we make. Reads every brief that arrives and sits in every discovery call, so what is sold is what gets built.

EngagementsScope & pricingPartnershipsNew business

Winnee

CTO & Founder

Owns architecture and engineering across every product in the ledger. A decade of hands-on work building AI tools, storefronts, booking systems and consumer platforms, and running them in production afterwards.

ArchitectureAI productsWeb platformsInfrastructure

03 / PrinciplesWhat we optimise for

Boring is the goal

A system nobody talks about is a system that works. We design for the quiet months, not the launch tweet.

Own the whole thing

Architecture, code, pipelines, on-call. Splitting those across teams is how bugs learn to hide.

III

Evidence over opinion

Audit logs, metrics, eval suites and ADRs. If it matters, it is measured and written down.

Self-host when it counts

Customer data, order history and creative work do not belong on someone else's API by default.

Local roots, global load

Built in Nepal, for Nepal first. Cash on delivery, local payment rails, Nepali-language interfaces and the realities of shipping to all seven provinces.

04 / StackTools we are fluent in

Fluency, not fashion.

Sweep across the list

We pick the tool the problem deserves. The list is long because the problems have been varied.

AI & MLOpenAI APIGemini APILangChainRAGTransformersSentenceTransformersQdrantPineconeChromapgvectorAgnoADKPrompt engineering Back endGoLaravelFastAPINode.jsPythonPHPDjangoFlaskExpressLumenFirebaseSupabaseConvex Front end & mobileNext.jsReactVue.jsInertia.jsTailwindSASSFlutterKotlinSwift Platform & opsDockerKubernetesOpenShiftApache AirflowCloudflare WorkersAWSGCPAzureDigitalOceanNGINXGitHub ActionsGitLab CIJenkinsPM2systemd ObservabilityPrometheusGrafanaLokiOpenSearchNew RelicAudit logging DataPostgreSQLMySQLMongoDBRedisSQLiteS3HasuraStrapiScrapySelenium Identity & securityOIDCOAuth2Azure Entra IDRBACJWT API & docsRESTGraphQLOpenAPIPostmanStoplight EmbeddedArduinoESP32NodeMCURaspberry PiSensor integration