CodeNXT Lab · Services
What we build.
Five capabilities, no subcontractors. Each one states what it is, when you actually need it, what it runs on, and what it does not include. That last part is the one most proposals leave out.
01
Backend & Infrastructure
Go services. Edge deployment. No rewrite at scale.
The part of your product nobody sees. Where your data lives, and what keeps it quick when a thousand people show up at once.
Go services built for concurrency, deployed close to the request. The data model, the failure modes, and the cost envelope are written down before the first file is committed, because those three are what a backend is actually made of.
When you need it
When the thing you have works at current traffic and you already know it will not work at four times current traffic. Month six is the usual moment: the schema starts fighting back, one endpoint carries the whole load, and nobody left on the team wrote it.
Stack
Go · Postgres · Redis · NATS · Docker · Cloudflare Workers
What we don't do in it
- No Kubernetes clusters for services that fit on a single machine. Most do.
- No microservice split as a starting position. It is a response to a measured problem, not an architecture.
- No on-call rota for you. We hand over a runbook so your own team can carry it.
02
Commerce & Content Platforms
The owner edits it. No developer call.
Online shops, and websites you can change yourself. Update a price or swap a photo without emailing a developer.
Online stores and content platforms rendered from Cloudflare's edge, so a page arrives from the data centre nearest the buyer. Prices, photographs, copy: everything the business changes weekly is data the owner edits directly, not a deploy.
When you need it
When your catalogue changes faster than your release cycle, or when the last site went stale because updating it required calling the person who built it.
Stack
SvelteKit · Cloudflare Pages · R2 · D1 · Stripe · Razorpay
What we don't do in it
- No page-builder with sixty blocks. A small set of blocks that match your catalogue beats a builder nobody opens twice.
- No headless CMS subscription bolted on by default. If your content model is simple, the platform carries it.
- No SEO retainer. We ship the markup correct and hand you the keys.
03
Mobile Applications
One codebase. Native where it matters.
Apps for iPhone and Android, built once so both stay in step.
Flutter applications where one codebase covers both platforms, dropping to native only at the points that genuinely differ: hardware, background execution, platform payment rails. Store submission and release signing are set up as part of the build, not left as an exercise.
When you need it
When the product needs to be on a phone rather than in a browser: offline tolerance, hardware integration, or a workflow someone runs standing up.
Stack
Flutter · Dart · Firebase · Fastlane
What we don't do in it
- No two separately-written native apps. If your requirements genuinely need that, we will say so and decline the work.
- No app for something that should be a website. A wrapped web view is a slower website with a download step.
- No ongoing store management. We hand over the signing keys and the release pipeline.
04
Applied AI
A component in a working system.
AI fitted into software that already works. Search that understands a plain question, or a step that used to need a person.
Retrieval, agents, and model integration wired into systems that already do their job. The model call is the easy part. Retrieval quality decides whether the answers are any good, and an evaluation harness is what tells you when they stop being good.
When you need it
When there is a real corpus or a real workflow to point it at. AI added to a product with neither is a demo with a running cost.
Stack
Python · PyTorch · Anthropic API · pgvector · LangGraph
What we don't do in it
- No foundation model training. We integrate models; we do not pretend to build them.
- No chatbot bolted onto a homepage. It answers questions nobody asked and buries the ones they did.
- No accuracy promises. We build the evaluation set so you can measure it yourself.
05
India Payments & Compliance
Structures that survive a regulator reading them.
Taking money in India properly. UPI, GST-correct invoices, and a paper trail that holds up when someone checks.
UPI collection flows, GST-correct invoicing, and fund-flow structures designed to be read by someone with the authority to stop them. Reconciliation is designed in at the start, because retrofitting it means reconstructing history from logs.
When you need it
When money moves between more than two parties, when invoices have to be right rather than approximately right, or when a payment aggregator has started asking questions about your flow of funds.
Stack
UPI · NPCI Rails · GST e-Invoice · Setu · Decentro
What we don't do in it
- No legal, tax, or regulatory advice. We build to what your CA and counsel sign off on.
- No holding of customer funds in a structure that needs a licence we do not have.
- No custom card processing. That belongs with a regulated aggregator, and we will integrate one.