Tripper Driving Simulator
Browser game · 2026
Haul cargo in a tipper truck through mountain routes. A driving game by Quorlyn Technology, published on Playgama.
Software your team
can maintain.
We design, build and run web, mobile and AI-enabled systems from Kathmandu, Nepal. We plan the architecture, release working software in stages, and document the code and infrastructure for your team.
Product engineering
Web · Mobile
AI engineering
LLM · Retrieval
Platform & cloud
Infra · CI/CD
Data engineering
Pipelines · Warehouse
From architecture to the next release
A product needs work after its first release: new features, changing data, deployment updates and fixes. Your team needs to understand how it was built.
We document technical decisions, version database changes, and test the parts a change could break. You keep the code, infrastructure and accounts.
How we work
- Scope
- Fixed in writing before the build starts, with the trade-offs named.
- Visibility
- Working software released in stages, with progress you can review.
- Ownership
- You keep the code, the infrastructure and the accounts. No lock-in.
What we can build with you
Six services, from a first product release to changes in an existing system. Each starts with a problem to solve.
- 01
Product Engineering
Web and mobile applications, including architecture, development, release and ongoing changes.
- 02
AI Engineering
Language models, document retrieval and automation, with evaluation and fallbacks built into the system.
- 03
Platform & Cloud
Deployment pipelines, monitoring and infrastructure management, with a review of running costs.
- 04
Data Engineering
Data pipelines, warehouse models, quality checks and reporting interfaces.
- 05
Interface Design & Engineering
Design systems and responsive interfaces, with accessibility checks and reusable components.
- 06
Technical Consulting
Architecture and code reviews, technology selection, and written migration or remediation plans.
Work directly with the engineers
The people who scope the project write the code. Here is how we approach that work.
Engineers scope the project
The people writing the code take part in scope, estimates and architecture. You can discuss a technical decision directly with them.
Changes are documented
Typed interfaces, versioned database migrations and tests help the next engineer understand a change. We record the reasoning behind technical decisions.
Interfaces work across devices
Shared components keep screens consistent. Responsive layouts and accessibility checks are included in the work and its acceptance criteria.
Recommendations include trade-offs
We explain the cost and constraints of the options, including a smaller build, a different tool or keeping the existing system.
Tools we work with
The stack depends on your system, budget and team. These are the tools we currently work with.
- Frontend
- Typed, component-driven, server-rendered by default. The browser gets as little JavaScript as the feature actually needs.
- TypeScript, React, Next.js, Tailwind CSS, Vite, React Native
- Backend
- Explicit system boundaries and typed interfaces keep application rules separate from framework code.
- Node.js, TypeScript, Python, FastAPI, REST, GraphQL
- AI & ML
- Model integration includes evaluation examples, quality checks and a fallback when a request fails.
- Claude API, Vector search, RAG pipelines, LangGraph, PyTorch, ONNX
- Data
- One definition per metric, versioned alongside the code that computes it. Pipelines are re-runnable by design.
- PostgreSQL, dbt, Airflow, DuckDB, Pandas, SQL
- Cloud & DevOps
- Infrastructure as code from the first environment, so the path to production is reviewable like any other change.
- Docker, GitHub Actions, Terraform, AWS, Cloudflare, Vercel
- Databases & Storage
- We start with relational storage and evaluate other options when the workload needs them. Schema changes are versioned migrations.
- PostgreSQL, Redis, SQLite, S3, Prisma, Drizzle
How a project runs
Scope, design, build, test, release and maintain. We agree the depth of each stage around the project.
- 01
Scope
We discuss the users, existing systems, constraints and budget, then agree the problem to solve and how to judge the result.
Deliverable: Scope, constraints, success criteria
- 02
Design
We design the interface and architecture together, recording decisions in the data model, schemas and reusable components.
Deliverable: Design system, data model, architecture
- 03
Build
We implement and deploy working features in stages. You can review the software as it develops and use those reviews to guide the next changes.
Deliverable: Working software, in an environment
- 04
Test
We test application logic and interfaces, check accessibility and performance against the agreed requirements, and address the findings before release.
Deliverable: Test coverage, audit results, fixes
- 05
Release
We prepare deployment, monitoring and a tested rollback before releasing to production. The runbook records how to operate the system.
Deliverable: Production release, monitoring, runbook
- 06
Maintain
After release, we review usage, cost and performance to plan further changes, or hand over the documented system to your team.
Deliverable: Iteration cycle or documented handover
Published work
Explore a project we have built and released.
Tell us about your project
Describe what you need to build or change, what is getting in the way, and any budget or deadline you have in mind.