Gopal Singh / theunblunt

Founder. Engineer. AI researcher.

I build AI products and the infrastructure under them. My research spans transformer memory, representation geometry, and what happens when language-model systems fail.

  • Based in Jaipur, India.
  • Founder & CEO, Metriqual.
Black-and-white portrait of Gopal Singh

01 / Products

What I’m building

Two products, both live. One keeps AI applications working when a model provider fails. The other turns what you already have into motion that knows what it’s talking about.

metriqual.com

Ship the product. We keep it running.

OpenAI / Anthropic / Gemini / Mistral / MiniMax

Metriqual

An AI gateway for routing requests across providers, preserving conversation context during failover, and tracking usage and spend.

Role
Founder & CEO
Status
Live

Most gateways route each request on its own. When a provider fails, the request is retried elsewhere and the health checks stay green, but the fallback model only receives the current turn. The conversation is gone.

Metriqual carries that context across providers, shows cost per model, and runs detectors that read the answers rather than only the status codes.

OpenAI-compatible API · Rust proxy (Axum on Tokio) · Python, TypeScript and Go SDKs

motionqual.com

Understand. Create. Check. Test. Learn.

Video / Short-form / Interactive demos / Copy

Motionqual

Turns a website, product, release, idea or brief into video, short-form clips and interactive demos that stay true to what the product actually does.

Status
Live, with a free tier

Generated creative usually starts from a prompt and knows nothing about the product. It invents claims, drifts off-brand, and is forgotten after export.

Motionqual works out the context first, then creates. It checks every on-screen claim against your sources, tests one change at a time against a goal you choose, and remembers what performed. Every layer stays editable, and it works for businesses, creators and product teams alike.

Connects to websites, GitHub, Linear, changelogs, PostHog, Segment, Amplitude and Slack

02 / Research

Research

My research spans transformer memory, representation geometry, and the reliability of systems serving language models. All four papers are arXiv preprints that I co-authored.

03 / Engineering

Systems I’ve worked on

What sits underneath the products and the papers: how each system works, and the part that was hard to get right.
  • Metriqual

    An LLM gateway that streams, fails over and keeps the receipts

    One OpenAI-compatible endpoint in front of OpenAI, Anthropic, Gemini, Mistral and MiniMax, covering chat, voice, image and video.

    How it works
    A Rust proxy (Axum on Tokio) forwards provider bytes as they arrive, so streaming stays streaming. Each key has a provider chain with circuit breakers, a spend ceiling and a record of every attempt. Failovers and recoveries go out as signed webhooks and log drains to Datadog, Splunk or OpenTelemetry.
    The hard part
    The worst failures return HTTP 200. So the gateway checks the answer itself, flagging a conversation that no longer matches what was stored, or tool-call arguments that are not valid JSON.

    Rust · Axum · Tokio · Streaming proxies · Circuit breakers · Webhooks · OpenTelemetry

  • Metriqual · ContinuityBench

    Stateful failover at 100 concurrent sessions

    Carrying the whole conversation to the fallback provider, so the user never has to start over.

    How it works
    On a timeout, 429 or 5xx, the request is replayed on the next provider with its full history. To measure it, a fault injector fires failures on the turn that depends on earlier context: 750 failover events per system, scored by a calibrated model judge.
    The hard part
    At 100 concurrent sessions, parallel tasks mutated a shared history cache between async yields and conversations bled into each other. Copying each message array before yielding fixed it. Then 100 sessions hit a fallback allowing 15 requests a minute, retried in lockstep and ran out of sockets, until backoff with jitter broke the sync.

    Python · asyncio · Fault injection · Backoff with jitter · LLM-as-judge evaluation

  • Motionqual

    A creative pipeline that checks its own claims

    Understand, create, check, test, learn: a loop that turns product context into video and demos.

    How it works
    It reads a website, release or brief and works out the audience, what is true and what must not be said, before generating anything. Output stays as editable scenes and layers, and it can watch GitHub, Linear or a changelog to draft or update videos when something ships.
    The hard part
    Trusting the output. Every on-screen claim is traced to a source. Deterministic checks for readability, composition, brand and playback run first, and an AI review steps in only when judgment is needed. Variants change one thing at a time against a goal you set.

    Context extraction · Claim verification · Layered video composition · A/B testing · PostHog, Segment, Amplitude

  • Research · co-author

    Instruments for looking inside transformers

    Measurement pipelines and kernels behind the interpretability and attention papers.

    How it works
    For trajectory geometry, hidden states are mean-pooled per layer and treated as a path, with length, curvature and convergence computed in the full ambient space across GPT-2, TinyLlama and Qwen2.5. For VLA, the memory update is an online regularised least-squares step, kept current with Sherman-Morrison rank-1 updates.
    The hard part
    Trusting the numbers. Every geometric effect is checked against shuffled-layer and random-embedding controls. For VLA, a Triton-fused kernel runs 14× faster than the sequential loop and drops below softmax attention latency at around 43,000 tokens.

    Python · Transformer hidden states · Triton · Representation geometry · Statistical controls

Backend and infrastructure
Python, FastAPI, Django, Rust (Axum, Tokio), Postgres, cloud infrastructure
Interfaces
React, Next.js, TypeScript
AI and ML systems
LLM serving and routing, evaluation harnesses, interpretability, attention architectures

04 / Writing

Writing

Most of what I write at the moment explains the research in plain language: what we measured, what broke, and what the numbers do and don’t show. These pieces are published on Metriqual Research.
  • Metriqual Research

    A forward pass has a shape.

    Measuring the path a prompt takes through a model instead of inspecting one layer at a time.

  • 2024theunblunt.com

    Notes archive

    Short notes on television and books from an earlier version of this site, alongside my reading and watching lists.

05 / About

About

I’ve worked in technology for about nine years, most of it with my hands in the code. I build backends in Python with FastAPI and Django, interfaces in React and Next.js, data models in Postgres, and the cloud infrastructure underneath. I’ve led technical work for teams, and I’ve taught at university level.

Right now I split my time between building products and doing research, and I don’t treat them as separate jobs. Metriqual started from a reliability problem: gateways kept requests alive but lost the conversation. The failover and failure-mode papers came out of fixing that properly. The interpretability and attention work comes from the other direction, from questions I wanted answered for their own sake.

The questions that hold my attention are usually mathematical or conceptual: why a representation takes the shape it does, or what memory means for a model with a fixed-size state. Outside software I read computational neuroscience, study Advaita Vedanta, and lift and run most days.

Contact

Get in touch

For research discussions, collaborations, or a conversation about something I’m building.

[email protected]