Roorkee, India — est. 2024

We build software.Then we run it.

Opryon Labs is a small engineering team. We've shipped three products of our own — a gym platform, a billing system, and a nutrition app — and we still maintain every one of them. They're live right now. Go use them.

3
products of our own, in production
2yr+
longest one has been live and maintained
2
client builds under NDA, EU + North America
1
team. No account managers, no handoffs.

Our own products

Most studios have never had to keep something alive after launch. We have three.

These aren't case studies we wrote about ourselves. They're running products with real users, and we're the ones who get called when they break.

GymPilot

SaaS — live

Gym management for Indian fitness businesses. Members, attendance, payment collection, and renewal reminders in one dashboard.

  • Next.js
  • TypeScript
  • PostgreSQL
  • WhatsApp Business API

AstraBill

SaaS — live

Billing and expense management for small and mid-size Indian businesses. Invoicing, GST compliance, and expense reporting in one place.

  • React
  • Node.js
  • TypeScript
  • Razorpay

FuelPulse

Web + Android — live

Nutrition and habit tracking that understands Indian food. Type what you ate in plain language and it estimates the rest. Free.

  • Next.js
  • Android
  • LLM inference
  • Vercel

Ekaya Fresh Food Hub

Web — live

Ordering and operations for a pure-veg home kitchen in Meerut. Menu, checkout, order tracking, and a phone-first admin the owner runs herself.

  • Next.js
  • TypeScript
  • PostgreSQL
  • Drizzle

Client work

Some of what we build, we can't show you.

Two of our builds sit behind NDAs. Here's what we can say about the problems, since the problem is the interesting part anyway.

Fleet compliance & driver logging

NDA

Confidential client · Commercial trucking

Hours-of-service logging for a commercial fleet. Drivers record duty status and mandatory rest, the operator gets a compliant record instead of a paper logbook.

  • Web app
  • Rules engine
  • PostgreSQL

Details on request

Vendor onboarding automation

NDA

Confidential client · Industrial manufacturing, Germany

A manufacturer had to complete supplier onboarding forms for every company it wanted to sell to. The process was: receive PDF, print it, fill it by hand, scan it, email it back. We removed the printer.

  • PDF form automation
  • Document pipeline
  • Node.js

Details on request

Before you email us

We're not right for everyone. Here's how to tell.

Probably a good fit

  • You want the thing you build to still be running in three years — not a demo for a pitch deck.
  • You want to be told when an idea has a problem, before we build it, not after you paid for it.
  • You're building for Indian users and need UPI, WhatsApp, or GST to genuinely work — not to be a checkbox in a spec.
  • You'd rather have four weeks of the right thing than two weeks of the wrong thing.
  • You want the people writing the code to be the people you talk to.

Probably not

  • You need it live next week.
  • You're collecting quotes and picking the cheapest one.
  • You've already decided exactly what to build and want someone to type it out.
  • You want AI in it because it ought to have AI in it.
  • You need a team of twenty. We're deliberately small and we stay that way.

If you're in the right-hand column, no hard feelings — we'd rather you know now than four weeks in.

How we work

Four stages. The last one is the one nobody else mentions.

01

We figure out what you actually need

Before anything gets built we work out what problem this solves and who it solves it for. This is where we tell you if part of it is a bad idea. Most projects get smaller at this stage, not bigger.

02

We scope it honestly

A plan that fits your budget, with what it includes and what it does not. If we think the budget will not cover what you want, we say so now rather than halfway through.

03

We build it

Working software you can open, in stages, not a reveal at the end. You talk to the engineers directly. Clean architecture and code someone else could pick up later.

04

We keep it alive

We've run our own products in production for years. We know launch day is the beginning of the work, not the end of it. Monitoring, fixes, and updates after you go live.

What we believe

01

We tell clients when something is a bad idea.

02

We use the right tool for the job, not the most impressive-sounding one.

03

We write code other people can read.

04

We take on a small number of projects at a time.

We build for how India actually works — UPI, WhatsApp, Hindi, GST, and pricing that isn't a US number converted into rupees. If you're building elsewhere, that same attention applies to wherever your users are.

Tell us what you’re building.

If we're not the right team for it, we'll say so and point you somewhere better. That costs you one email.

Asmit Tyagi — Founder, Opryon Labs