About
A company built around how software actually ages
Quorlyn Technology is an engineering company in Kathmandu. We are new, deliberately small, and more interested in systems that stay workable than in shipping something impressive once.
- Registered
- Quorlyn Technology Private Limited
- Based in
- Kathmandu, Nepal
- Founded
- 2026
- Focus
- Product, AI, platform, data
Small, technical, and direct about it
Quorlyn Technology Private Limited is a software engineering company registered in Nepal and based in Kathmandu. We build web and mobile products, AI-enabled features, the cloud infrastructure underneath them, and the data systems that make any of it measurable.
We are early. There is no decade of case studies here and we are not going to manufacture one. What we can be judged on is the way the work is run: what gets written down, how quickly something real reaches an environment you can open, and whether the difficult parts of a project get raised in week one or week twelve.
The team is deliberately small. The people scoping your project are the people writing the code, which removes the layer where estimates usually go wrong and context usually gets lost.
Six positions we build from
These are opinions, not neutral best practice. They shape what we recommend and occasionally what we decline.
The problem outranks the stack
Technology choice is downstream of the domain. We model the data and the boundaries first, then pick tools that fit the problem, the team that will inherit it, and the budget it has to run on. A stack chosen for its novelty becomes someone else's maintenance burden.
Software is read more than it is written
Code is a communication medium with a long lifespan. We favour explicit over clever, boring over novel in the places that must not break, and documentation written while the reasoning is still fresh.
Shipping is a discipline, not an event
Work goes to a real environment early and often. A pipeline, monitoring and a tested rollback exist before the first release, which is what makes launch day uneventful.
Accessibility is correctness
An interface that excludes part of its audience is not finished. Keyboard access, contrast, semantics and reduced-motion support are part of the definition of done, not a remediation phase.
Measure before optimising
Performance work without a measurement is decoration. We instrument first, fix what the data points at, and leave the rest alone — the same applies to AI features, infrastructure spend and database indexes.
Say the difficult thing early
Scope that will not fit, an approach that will not scale, a request that will cost more than it returns — all of it is cheaper to raise in week one. We would rather have an awkward conversation than deliver a comfortable failure.
The people, once there are people to name
Not yet published
We are not listing a team page with stock photographs and invented job titles. When the founding team is ready to be named publicly, their names, roles and actual work will appear here.
In the meantime, the fastest way to judge us is to send a real problem and see what comes back.
Work with us
Bring us something difficult
An architecture you are unsure about, a build that has stalled, or a product that only exists as a document. All three are good first conversations.