Skip to content

Product Studio

Products built by YGL.

A consulting studio that doesn't build its own products is guessing. These are ours — designed, engineered and shipped in-house, where every architectural shortcut becomes our problem rather than a client's.

In the studio

Two products, engineered end to end.

Both are AI-native rather than AI-decorated: the model work sits at the centre of what the product does, not bolted onto the side of it.

Built by YGLHealth & Wellness

FitRas

An AI-native wellness platform built by YGL.

Photograph a meal, get an honest macro breakdown. An AI nutrition, fitness and wellness platform with a vision pipeline that refuses to guess.

AI integration points
7 distinct flows
Specialised agents
Coach · Nutritionist · Health
Platforms
Web · iOS · Android
Recognition guardrail
Portion gate before macros
Read the case study
Built by YGLKnowledge & Productivity

InstaBrain

AI-powered short-form content intelligence.

Turns saved reels into a searchable library of structured, actionable notes — including Hindi and Hinglish audio that most tools drop.

Pipeline stages
Fetch → transcribe → analyse → embed
Search
Semantic, over your own library
Languages
English · Hindi · Hinglish
Capture
Reels · screenshots · share sheet
Read the case study

Why we build our own

The products are the portfolio.

Client work is usually under NDA, and a new studio has no logos to show. Building our own products solves that honestly: the architecture, the trade-offs and the failure modes are all inspectable, because we made every one of those decisions ourselves.

We carry the consequences

When the vision pipeline returns a wrong number, it's our users affected and our problem to fix. That changes the design decisions you make — usually toward the boring, reliable option.

The hard parts are real

Evaluation harnesses, fallback chains, cost ceilings, store submissions, row-level security. These only get built when something has to actually run in production.

Nothing here is theoretical

Every technique we recommend in a client engagement is one we've already had to make work, debug and pay for somewhere on this page.

On the numbers we don't show: neither product has publicly launched, so there are no user counts, revenue figures or growth charts on this site. Everything described is engineering that exists in the codebase.

Build with us

Want something like this built?

The same team, the same practices, applied to your product.