A senior engineering firm — New York corporation, engineering team in Kathmandu. Data platforms and pipelines, web and mobile software, AI work like MCP servers, automations and chatbots, and crypto applications. Whole products, or our engineers inside your team.
Most firms our size list twelve services and are genuinely good at two. We cut ours down to the three we’d put our name on.
Moving Azure Data Factory pipelines onto Databricks?
A Snowflake warehouse that holds at volume?
Medallion architecture on Databricks or Microsoft Fabric?
Glue jobs timing out, S3 and RDS sprawl, IAM nobody can explain?
Five hundred lines of SQL Server 2012, and an Azure SQL deadline?
That’s the work. Our engineers are certified across Databricks, Spark, AWS and Microsoft Fabric.
An idea, a prototype, nothing on a screen yet?
Postgres, Mongo, CockroachDB or Dynamo?
How much RAM for 10,000 users, and on what host?
APIs that hold when traffic triples, or one already buckling?
iOS and Android from one codebase? An app stuck at three stars?
Payments in Stripe, PayPal or crypto — subscription or one-off?
That’s the work — web, mobile, APIs, Web3.
Tickets, reports and handoffs eating your week?
An agent that reads your logs and opens the fix PR?
A chatbot on your own data — admins see all, customers see a slice?
Security audits that run on a schedule, not when somebody remembers?
A model self-hosted and tuned to you, so nothing leaves your network?
That’s the work. We don’t build models — we put them to work on whatever’s quietly eating a day a week.
Companies whose data team is three people and underwater
Startups who need one system built, or the whole product shipped
Larger teams who need one specific skill for one specific stretch
Teams who need the decision made before they commit to building
Web3 product owners who need chains, wallets and contracts handled
Agencies who've sold more than they can staff
Ten-plus projects delivered so far. We don’t run a logo wall, and our agreements don’t let us publish the names either. What we can show is the work itself: how a project runs with us, the tools it runs on, and where we come out when the decisions are hard. At proposal stage we put you on the phone with someone we’ve worked for — a client, on a call, answering whatever you want to ask about how the work ran. We ask their permission first, so allow a week.
We give you engineers who join your team, your Slack, your standups. You manage the work. We handle everything else. Hourly or monthly, and you can scale it up or down with reasonable notice.
You bring the problem. We take it from the first conversation to something deployed, tested and documented, with demos at every milestone so you're never waiting to find out how it's going.
Architecture reviews, picking a platform, getting ready for ISO 27001 or SOC 2, or a senior engineer sitting in your planning meetings a few days a month. No implementation required.
Plenty of clients start with the third, move to the second, and end up on the first. That’s fine. That’s normal.
How this works in practiceWe’re in both places. The core technical team is in Kathmandu and that’s where the work gets done. You pick which side you contract with — the New York corporation or the Nepal company — and pay whichever way suits. We’d rather tell you that than have you work it out.
The whole UK working day, year round. For US Eastern we’re online from mid-evening the night before right through your morning, until early afternoon — 12:15pm in winter, 1:15pm in summer. Engineers can start earlier or later within that, so tell us which hours matter to you. Our week runs Sunday to Friday, and we don’t close for Christmas or New Year.
Your afternoon is our night. Anything that needs a live conversation happens before 12:15pm your time, and we’ve built the company’s whole working day around that. Everything gets written down, every handover says what’s done and what’s blocked, and nobody resolves a question by leaning over a desk. It’s made us better at documentation than most co-located teams we’ve worked in. The one real gap is Dashain, when Nepal shuts for about a week each autumn. We give you the dates months ahead.
Headquarters.
Engineering. Where the building happens.
Online now Offline now. Online 8:00am to 11:00pm Kathmandu time, working days.
Most clients pay USD by wire or ACH through New York, or local fiat through Kathmandu. Invoices in USD, EUR, GBP or AUD. If stablecoins are easier, we settle in USDC or USDT too — tell us on the call and it’s set up before your first invoice.
Invoices in
Wire or ACH into the New York corporation, or local fiat into Kathmandu — whichever side you contract with.
Hatnest is our own product — a practice-question site for professional certifications, live at hatnest.io.
We built it because every study site we used while getting certified was buried in ads, and half the questions had obviously been lifted from real exams. That’s against the rules everyone signs, and it’s useless anyway, because memorising a leaked question teaches you an answer instead of a subject.
So we wrote our own. Every question original, written against the published exam objectives. Every one with an explanation. No ads.
It’s also the honest answer to “what do you build when nobody’s writing the requirements?” — which clients ask more often than you’d think.
Visit Hatnest
Twenty minutes, no deck. We’ll tell you straight whether this is work we should be doing, and if it isn’t, we usually know who should.
We come back within one business day.
Analytics
We’d like to use Google Analytics to see which pages people find useful. It sets cookies, and only if you say yes. Your choice can be changed at any time under Cookie settings. Privacy
