Software company · Kathmandu · UTC+5:45
Software that runs
your business.Built to last.
Sanave Tech designs, builds, and supports SaaS platforms, mobile apps, booking engines, admin dashboards, e-commerce stores, realtime APIs, card games, customer portalsfor companies in Nepal and worldwide.
What we do
Six ways we build for you.
See all servicesSaaS product development
From product idea to a launched, subscription-ready platform.
Next.js · FastAPI · PostgreSQLCustom software development
Business systems built around the way your company works.
Next.js · Python · PostgreSQLMobile app development
Android and iOS apps from a single Flutter codebase.
Flutter · Dart · FirebaseWeb application development
Portals, dashboards, and e-commerce in Next.js and React.
Next.js · React · TypeScriptBackend & API engineering
The services and integrations behind your products.
Python · FastAPI · PostgreSQLCloud, DevOps & support
Deployment, CI/CD, and the ongoing care software needs.
AWS · Supabase · DockerBuilt for every screen
Designed on the smallest screen first.
The phone is the tightest constraint, so that is where the design starts and where we test hardest. The layout then opens up as the screen grows, and each size gets its own considered treatment.
- Checked on real devices, including a mid-range Android phone
- Readable type and tap targets that work with one thumb
- Keyboard and screen-reader support built in from the start
- Page speed measured on a real connection, on a mid-range phone
Kathmandu, Nepal
Engineered here. Shipped everywhere.
We work from Kathmandu. We’re built for businesses in Nepal, Australia, the US, and the UK, and set up so distance only ever changes what you pay.
Built at +05:45
Your afternoon is our evening.
Kathmandu runs on the world’s quarter-hour offset. A Sydney morning, a London afternoon, and a New York start of day all overlap our working hours, so questions get answered the same day they are asked.
27.7°N · 85.3°E · 1,400 m · UTC+5:45
Kathmandu is UTC+5:45. Our 9 to 5 overlaps Sydney (UTC+10) mornings, London (UTC+1) afternoons, and the start of the New York (UTC−4) day.
What we can build for you
Pick a system. See what building it involves.
Six shapes cover most of what we’re set up to build. Each one ships as working software on infrastructure you own.
Multi-tenant products with billing built in
Sign-up through to subscription: organizations, roles and permissions, usage limits, payments, and a dashboard the owner can read at a glance.
- Tenant isolation and role-based access
- Subscriptions, invoices, and failed-payment handling
- Usage metering with limits and alerts
- An audit trail on every privileged action
One Flutter codebase, both stores
Apps that feel at home on Android and iOS from a single codebase, with offline behavior, push notifications, and store submission handled for you.
- Android and iOS from one codebase
- Offline-first data that syncs on reconnect
- Push notifications and deep links
- Store listings, review, and release management
Storefronts built for your busiest day
Catalog, cart, checkout, and payments wired to the rails your market already uses, with an admin your team can run without calling us.
- Catalog, variants, stock, and pricing rules
- Checkout with local and card payment rails
- Orders, refunds, and delivery tracking
- Page speed measured on real devices
The back office your team lives in
The screen your staff keep open all day: fast tables over large datasets, filters that combine, bulk actions, exports, and permissions per role.
- Filters that combine with AND or OR
- Bulk actions across selected records
- CSV and PDF exports on demand
- Per-role permissions and activity logs
Availability you can trust
Calendars, resources, and rules that stop double bookings, with payment at booking, reminders, and rescheduling customers do themselves.
- Resource and staff availability rules
- Slot holds that expire, so the same slot isn't sold twice
- Deposits or full payment at booking
- Automatic reminders and self-service changes
The backend everything else plugs into
Documented APIs with versioning, authentication, rate limits, webhooks, and realtime channels, monitored so problems surface before your customers report them.
- Versioned REST or GraphQL, documented
- Token auth, scopes, and rate limits
- Webhooks with retries and signatures
- Realtime channels over websockets
Where we help
The systems a business runs on.
Most of our work falls into a few familiar shapes, whatever the industry. A sample of what we’re set up to build:
2 parts selected · scoped in the same five-phase process
Scope this system →I sketched a system on your site with: auth & accounts, admin console.- Commerce & retail: storefronts, inventory and billing systems, order management
- Hospitality & travel: booking engines, property dashboards, guest apps
- Logistics & field work: dispatch tools, delivery tracking, driver apps
- Education: learning platforms, admissions portals, exam tooling
- Health & clinics: appointment systems, patient records workflows, reporting
- Finance-adjacent operations: invoicing, reconciliation tools, payment integrations
How we deliver
A five-phase process with a demo every week.
Discover
A conversation about what you need and why, then we put the scope in writing. No charge, no obligation.
You getA written proposal: scope, milestones, timeline, and a fixed price — plus what we'd cut first if the budget is tight.
Design
We design the screens and the system architecture together, before heavy build spend starts.
You getA clickable prototype and a technical design you can challenge while changes are still cheap.
Build
Development in weekly increments. Every week ends with a demo you can click through yourself.
You getA working build after each increment, in a repository you own from the first commit.
Launch
Deployment to production on your accounts, store submissions for mobile, and the final quality pass.
You getYour product live, with documentation, credentials, and a recorded walkthrough of the codebase.
Support
A monthly support retainer with agreed response times, or a clean handover if your own team takes it from here.
You getYour choice, changeable later. The code, infrastructure, and accounts are already yours.
What each phase hands you is spelled out on the services page.
Why Sanave
Six things we put in every contract.
You own everything
Repository, infrastructure, and accounts are yours from the first commit. If you ever want to leave, nothing is holding you hostage. We'd rather be kept for the work than for the lock-in.
Demos you can click
Every week you see running software. If a week ends and there's nothing to click, we owe you an explanation.
Documentation as a deliverable
Every project ends with docs, runbooks, and a recorded walkthrough of the codebase. Good enough that another engineer could take over without ever emailing us.
Tested and monitored
CI runs the tests on every change and production has real alerting. When something breaks, we usually know before you do, and we tell you either way.
Updates you can read
A short written update every week, in plain English. Your accountant should be able to follow where the project stands.
Products of our own
We're building our own games and SaaS on the same stack we sell. When we recommend Flutter or PostgreSQL, it's because we work in them every day on our own products.
Technology
A deliberately boring stack.
Proven, widely-adopted technology chosen so your software is easy to run, easy to hire for, and easy to hand over. We go deep on a few tools instead of shallow on forty.
This is the reference architecture most of our projects ship on — the same one behind our own products. Yours starts here and bends where your problem demands it.
- Flutter + DartAndroid and iOS apps from one codebase
- Next.js + React + TypeScriptweb applications and sites
- Python + FastAPIAPIs and backend services
- PostgreSQLthe database, almost always
- Rediscaching, queues, and realtime state
- AWS + Supabasecloud hosting, auth, and storage
Our products
We build our own products on the same stack we sell.
SaaS products are in the works, and our games studio is building mobile titles for South Asian players. Everything runs on the stack we recommend to clients, because we’d rather find its limits in our own products than in yours.
Insights
How we think about building software.
Questions we get asked
The answers, before you have to ask.
The things worth settling before a first call. If yours is not here, ask it and you will get the same plain answer.
See how a project runsWho owns the code and the accounts?
You do, from the first commit. The repository, cloud accounts, app-store listings, and domains are created in your name or transferred to it before launch.
How do you price projects?
Fixed price, agreed after a free discovery phase produces a written scope, and billed by milestone. When something changes mid-project, it gets written down and priced before any work happens on it.
We're not in Nepal. How does working together run day to day?
We agree working hours that overlap your timezone — Australia, the US, and the UK all work with Nepal's UTC+5:45. You get a weekly demo of running software, written updates in plain language, and one named person responsible for your project.
What happens after launch?
Your choice: a monthly support retainer with agreed response times, or a clean handover with documentation, credentials, a runbook, and a recorded walkthrough of the codebase, so your own team can take over.
How big is the company?
Small and founder-led, and we say so plainly. What that buys you: the person who scopes your project is the person responsible for building it, senior attention on every line of the work, and no junior bench for things to be quietly delegated to.
What don't you do?
Technologies we don't use daily, teams of fifty, and promises we can't keep. If your project needs something we're not the right fit for, we'll say so on the first call and point you somewhere better.
Tell us what you’re building.
A few sentences about your project is enough. You’ll hear back within one working day, with questions, a plan, or a straight “we’re not the right fit.”
Looking to join the team instead? See open roles