Software solutions & engineering

We build the systems that don't fall over.

Web, iOS, Android, meta apps, backends, and cloud infrastructure — one team builds the whole product, and keeps it running.

01 — Who we are

Small team. Production scale.

Four years building and running software in production — web apps, iOS and Android, meta-platform integrations, and the backends behind them — including sole ownership of a fast-growing consumer app with real traffic, real payments, and real uptime pressure.

Most agencies ship a repo and leave. We've been the one on call at 2am. We build for that from day one.

0

Years in production

0

Of what we design, we can operate

0

Platforms from one backend

02 — The stack

Boring tools. Chosen on purpose.

We pick technology you can hire for in five years, not whatever shipped last quarter.

Language & framework

  • Java & Kotlin

    Static types catch at compile time what dynamic languages find in production.

  • Spring Boot

    Two decades of production hardening. Every failure mode is already documented.

Data

  • PostgreSQL

    Correct under concurrency, and it scales far past where most products ever get.

  • Redis

    Caching and distributed locks. The difference between holding load and folding.

Infrastructure

  • AWS

    EC2, Lambda, S3, SQS, SNS, EventBridge — assembled so you can still read the bill.

  • Docker & CI/CD

    Reproducible builds. What passes locally is what runs in production.

Client & interface

  • Nuxt & Web Components

    Standards-based front ends that outlive framework churn.

  • iOS, Android & Meta

    Native mobile and meta-platform apps against one backend, not three divergent implementations.

03 — Selected work

Shipped. Running.
Load-tested by reality.

01 E-commerce · live

Indiknots

Full product — web storefront, backend, infrastructure

A handcrafted-rug marketplace with the full stack behind it: product catalogue, payments, order management, and the AWS infrastructure keeping checkouts fast under festival traffic.

Spring Boot · Postgres · Nuxt · AWS

Visit indiknots.com
02 Consumer · live

Sacrena

Backend, iOS & Android, meta-platform integrations

A consumer app shipped across iOS and Android with subscriptions, Apple offer codes, and meta-platform integrations — backed by one Spring Boot backend operated through sustained growth.

Spring Boot · Postgres · Redis · iOS · Android · Meta APIs

Visit sacrena.com
03 Open source

Dota Workspace

Author & maintainer

A frontend framework built from scratch on native web components — core, wrap, and rest packages. Sometimes the right tool doesn't exist yet.

Web Components · TypeScript

View on GitHub
01 / 03

04 — What clients say

Ask the peoplewho hired us.

[PLACEHOLDER — replace before launch]

0

Projects delivered

0

Uptime across managed systems

0

Clients on retainer

0

On-time delivery

Our backend was falling over every weekend. Six weeks later it wasn't, and we finally understood why it had been. The handover documentation alone was worth the engagement.

[Client name]

[Role] · [Company]

We'd been quoted twice the price by an agency who wanted three months just to scope it. Got a fixed quote in a week and shipped ahead of the date.

[Client name]

[Role] · [Company]

The thing that stood out was being told no. We asked for a feature and got a straight explanation of why it would cost us later. Nobody had done that before.

[Client name]

[Role] · [Company]

Worked with

[Client 01][Client 02][Client 03][Client 04][Client 05]

05 — What we do

Four things.Done properly.

06 — Engagement models

Priced by scope.Not by page count.

Starting points. Final scope sets final price.

Launch

₹25k

starting

Get a real product in front of real users.

  • Frontend and backend, one app
  • Database and API layer
  • Cloud deployment
  • 1 month support

Partner

₹40k

per month

An engineering function, not a project.

  • Ongoing architecture and development
  • Infrastructure ownership
  • Security review and hardening
  • Direct access, no ticket queue

Consultancy

Hourly

by arrangement

Architecture review, infra audit, security assessment, or a second opinion before you commit.

India rates. International engagements quoted separately.

07 — How it runs

From first call
to running system.

Step 01 / 05

01Discovery call

We find out if this is even a fit.

Thirty minutes on what you're building, where it stands, and what's actually blocking you. No deck, no pitch. If we're wrong for the work we say so and point you at someone better.

You leave with

An honest read on feasibility, rough cost, and whether you need us at all.

~30 minutes · free

02Written scope

Fixed price. Fixed date. In writing.

We write down exactly what gets built, what it costs, and when it lands. You read it before any money moves. Anything not in the document is not in the project — that protects both of us.

You leave with

A scope document with deliverables, milestones, price, and delivery date.

2—5 days · free

03Build in the open

You watch it happen, not wait for it.

Work happens in your repository from commit one. You get a checkpoint at every milestone with something running, not a status update. If something's going wrong you hear it that week, not at the deadline.

You leave with

Working software at each checkpoint, in your own repo, reviewable at any time.

4—16 weeks · by scope

04Handover

Everything, in a state you can use.

Architecture diagrams, API documentation, runbooks, and a walkthrough with whoever will maintain it. The test we hold ourselves to: if we disappeared tomorrow, could your team keep going? If not, we're not done.

You leave with

Full ownership — code, infrastructure, accounts, documentation. No lock-in.

1 week · included

05Support window

We stay on the hook.

One month on Launch, three on Scale. Defects in what we built get fixed at no charge. After that most clients move to a retainer or come back per project — but you're never obliged to either.

You leave with

A running system, and someone who still answers the phone about it.

1—3 months · included

08 — AI code remediation

audit in progress

01 / 06

severity high

Duplication

0×

the same feature, four times over.

Fix a bug once and it stays broken in three other places. Every change you ask for costs four times what it should — and nobody can tell you which copy is the real one.

Data leaks

0%

of the row, sent to the browser.

Password hashes. Internal flags. Other customers' records. It all works, so nobody notices — until someone opens the network tab and screenshots it.

Security

0

rate limits on your login.

Permissions checked in the browser. Secrets committed to the repo. Anyone can hammer your auth endpoint all night. This is default AI output, and it is how people get in.

Cloud spend

0×

the database calls you need.

Fine at fifty users. At five thousand it buckles, and the fix everyone reaches for is a bigger server. You pay that bill every month, forever, to hide a problem worth one afternoon.

Blind spots

0

tests. No alerts. No logs.

Payments break on Friday night. You find out Monday morning, from a customer, in public. Nothing in the system was ever built to tell you first.

Hiring

0

every good engineer will quote a rewrite.

Undocumented, untested, shaped like nothing they recognise. They are not being difficult — that is the honest number. Which is exactly the number we are here to avoid.

Audit complete

Six problems. One week to clear them.

We run a tested set of agent skills across your codebase — the same ones we use on our own production systems. Weeks of manual review, done in days. You get the written report before you owe us anything.

Get the free audit

Shipping fast with AI was the right call. Leaving it there is the expensive part.

09 — Why we exist

Most softwareis delivered.Not owned.

An agency builds, invoices, leaves. Six months later something breaks at scale and nobody left understands why the schema looks like that.

We started from the other side of that — running production systems, owning uptime, watching which decisions age well and which get expensive.

If we wouldn't run it ourselves, we won't ship it to you.

10 — How we work

Non-<br>negotiables.

01

Secure by default

Auth, rate limiting, and tenant isolation designed in — not retrofitted after an incident.

02

Documented

Architecture diagrams, API docs, runbooks. If we vanished, your team could pick it up.

03

Reviewed and tested

Git from commit one. Review on every change. Automated tests on critical paths.

04

Observable

Logging, monitoring, alerts before launch. You hear it from your dashboard, not your users.

05

You own everything

Your repos, your cloud, your data. No lock-in.

06

Honest timelines

We quote what it takes. We'd rather lose the pitch than miss the date.

11 — Where we fit

Big enough to ship.Small enough to care.

An honest comparison. There are engagements where an agency is the right answer, and we'll tell you when yours is one of them.

 

Agency

20—200 people

Melman Labs

Small, senior

Freelance marketplace

One-off hire

Who writes your code

Whoever is unassigned — often the most junior person on the floor.

The person you spoke to on the first call. Every time.

Whoever bid lowest. Skill verified by a profile rating.

Getting an answer

Account manager → project manager → developer. Days.

You message the engineer directly. Same day, usually the same hour.

Fast while engaged. Silent once the contract ends.

What you pay for

Engineering, plus sales, management, and an office you never visit.

Engineering. There is no other overhead to fund.

The lowest hourly rate — until the rework starts.

Infrastructure & ops

Separate team, separate quote, often a separate vendor.

Same person who wrote the code. We've been on call for what we build.

Usually out of scope. "Deploy it yourself."

When it breaks at 2am

A support ticket queued behind everyone else's.

Someone who already knows why the schema looks like that.

They've moved on to the next contract.

Capacity

Genuinely large. Can staff ten people next Monday.

Deliberately limited. A few engagements at a time, properly.

One person, until they take another client too.

Best when

You need many parallel workstreams and have people to manage them.

You need a system that holds up, and one person accountable for it.

The task is small, well-defined, and disposable.

Melman Labs

Small, senior

  • Who writes your codeThe person you spoke to on the first call. Every time.
  • Getting an answerYou message the engineer directly. Same day, usually the same hour.
  • What you pay forEngineering. There is no other overhead to fund.
  • Infrastructure & opsSame person who wrote the code.
  • When it breaks at 2amSomeone who already knows why the schema looks like that.
  • Best whenYou need a system that holds up, and one person accountable for it.

Agency

20—200 people

Layers between you and the code, overhead in the invoice, and infrastructure quoted separately. Genuinely better when you need ten parallel workstreams and have people to manage them.

Freelance marketplace

One-off hire

Cheapest hourly rate and fine for small, well-defined, disposable work. Ops usually out of scope, and nobody answers once the contract closes.

12 — Common questions

Before youask us.

Still unclear on something? Ask directly — we answer honestly, including when the answer is no.

Ask a question

Have somethingthat needs building?

Tell us what you're working on. We'll tell you honestly if we're the right fit — including when we're not.

Response time

Within one business day

Prefer email

webinngo@gmail.com

Based in

India — working with clients worldwide

Engagement

0 / 20 min