The stack, and what each thing is for.

A wall of logos proves nothing, so every tool below carries the job it does here and the place it actually runs. This is the stack we bring; the model layer inside an engagement is chosen with you.

Agents & models

What the agents in our shop run on. The model layer inside client products is chosen per engagement — vendor-honest, not vendor-loyal.

Tool What it does here Where it runs
Claude live Research fan-outs, first drafts, and the review passes that check them. Our shop — every phase of this site included.
Claude Code live Code, tests and documentation drafted under an engineer’s direction. Our shop — this site was built with it.

Backend

What the products’ servers are written in — and what we bring to an engagement unless your estate says otherwise.

Tool What it does here Where it runs
Node live Service APIs and the glue between agents and the systems they act in. Spans the five products.
Python live Agent orchestration, pipelines, and everything model-adjacent. Spans the five products.
Django live Where a product needs a full application framework and an admin from day one. Product backends.
FastAPI live Where the surface is an API and latency matters more than scaffolding. Product and agent services.

Frontend & mobile

The interfaces people actually touch — web and native, from one team.

Tool What it does here Where it runs
React live Product interfaces, dashboards, and anything with real interaction. Spans the five products.
React Native live One codebase where a product needs to be on a phone as well as the web. Mobile surfaces of the portfolio.
Astro live Static sites that ship every word without waiting for JavaScript. This website.
GSAP live The one scroll-scrubbed motion the design law allows, and nothing more. This website.

Data & retrieval

Where the facts live, and how an agent finds the right one instead of guessing.

Tool What it does here Where it runs
Postgres live The system of record. If a fact matters, it lives here. Spans the five products.
pgvector live Retrieval over your own documents — grounded answers, inside the boundary. Retrieval features in the portfolio.
Redis live Queues, caches and the short-term memory between agent steps. Spans the five products.

Evals & machine gates

What tells us the work is right before a person is asked to approve it.

Tool What it does here Where it runs
Playwright live Real-browser checks: it also runs this site’s zero-leak language gate. This site’s QA run, and product test suites.
Lighthouse live The performance and accessibility bar, recorded in the build report. This site, every phase.

Marks are the honesty grammar: ● in production in our products or our own shop. Beyond these, the model layer inside an engagement is chosen with you — vendor-honest, not vendor-loyal.

Your estate will have its own stack, and that is fine: the practices are integration-first, and the legacy audit starts by reading what you already run. How an engagement starts →

The signal · the first conversation is free — and taken seriously

Tell us what you're building.

Made with love in Naya Bharat