An engineering company in Kathmandu
Quorlyn Technology builds web, mobile and AI-enabled systems. We are a small team, founded in 2026, with engineers involved from scoping through implementation.
- Registered
- Quorlyn Technology Private Limited
- Based in
- Kathmandu, Nepal
- Founded
- 2026
- Focus
- Product, AI, platform, data
A small team, directly involved
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 a new company. We document project decisions, release working software for review, and discuss constraints as they become clear. No client case studies are published yet.
The team is deliberately small. The people scoping your project are the people writing the code. You can discuss the scope and technical decisions directly with them.
How we make engineering decisions
These principles guide our recommendations, implementation and handover.
Choose tools around the system
We model the data and system boundaries first. Tool selection follows the problem, the team maintaining it and the budget available to run it.
Make the code readable
We favour explicit code and predictable behaviour, especially in the parts that must not break. Documentation records decisions while the reasoning is still fresh.
Prepare the release
We deploy to a working environment during development. A deployment pipeline, monitoring and a tested rollback are part of preparing the first production release.
Include accessibility in acceptance
Keyboard access, readable contrast, semantic markup and reduced-motion support belong in the agreed acceptance criteria and implementation checks.
Measure before optimising
We collect measurements before changing performance, AI features, infrastructure spend or database indexes. The measurements guide what to change and whether it helped.
Raise constraints early
We discuss scope, scaling concerns and costs when they become clear, so the team can decide how to proceed before committing more work.
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.