We\u2019re sharing some of the challenges we faced building an AI video interface that has realistic conversations with a human, including getting it to under 1 second of latency.
To try it, talk to Hassaan\u2019s digital twin: https://www.hassaanraza.com, or to our "demo twin" Carter: https://www.tavus.io
We built this because until now, we've had to adapt communication to the limits of technology. But what if we could interact naturally with a computer? Conversational video makes it possible \u2013 we think it'll eventually be a key human-computer interface.
To make conversational video effective, it has to have really low latency and conversational awareness. A fast-paced conversation between friends has ~250 ms between utterances, but if you\u2019re talking about something more complex or with someone new, there is additional \u201cthinking\u201d time. So, less than 1000 ms latency makes the conversation feel pretty realistic, and that became our target.
Our architecture decisions had to balance 3 things: latency, scale, & cost. Getting all of these was a huge challenge.
The first lesson learned was to make it low-latency, we had to build it from the ground up. We went from a team that cared about seconds to a team that counts every millisecond. We also had to support thousands of conversations happening all at once, without getting destroyed on compute costs.
For example, during early development, each conversation had to run on an individual H100 in order to fit all components and model weights into GPU memory just to run our Phoenix-1 model faster than 30fps. This was unscalable & expensive.
We developed a new model, Phoenix-2, with a number of improvements, including inference speed. We switched from a NeRF based backbone to Gaussian Splatting for a multitude of reasons, one being the requirement that we could generate frames faster than realtime, at 70+ fps on lower-end hardware. \nWe exceeded this and focused on optimizing memory and core usage on GPU to allow for lower-end hardware to run it all. We did other things to save on time and cost like using streaming vs batching, parallelizing processes, etc. But those are stories for another day.
We still had to lower the utterance-to-utterance time to hit our goal of under a second of latency. This meant each component (vision, ASR, LLM, TTS, video generation) had to be hyper-optimized.
The worst offender was the LLM. It didn\u2019t matter how fast the tokens per second (t/s) were, it was the time-to-first token (tfft) that really made the difference. That meant services like Groq were actually too slow \u2013 they had high t/s, but slow ttft. Most providers were too slow.
The next worst offender was actually detecting when someone stopped speaking. This is hard. Basic solutions use time after silence to \u2018determine\u2019 when someone has stopped talking. But it adds latency. If you tune it to be too short, the AI agent will talk over you. Too long, and it\u2019ll take a while to respond. The model had to be dedicated to accurately detecting end-of-turn based on conversation signals, and speculating on inputs to get a head start.
We went from 3-5 to <1 second (& as fast as 600 ms) with these architectural optimizations while running on lower-end hardware.
All this allowed us to ship with a less than 1 second of latency, which we believe is the fastest out there. We have a bunch of customers, including Delphi, a professional coach and expert cloning platform. They have users that have conversations with digital twins that span from minutes, to one hour, to even four hours (!) - which is mind blowing, even to us.
Thanks for reading! let us know what you think and what you would build. If you want to play around with our APIs after seeing the demo, you can sign up for free from our website https://www.tavus.io."},"title":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["ai","agent"],"value":"Show HN: A real time AI video agent with under 1 second of latency"}},"_tags":["story","author_hassaanr","story_41710227","show_hn"],"author":"hassaanr","children":[41710455,41710484,41710563,41710586,41710612,41710662,41710696,41710769,41710793,41710802,41710808,41710855,41710866,41710906,41710946,41710979,41711066,41711103,41711314,41711456,41711463,41711661,41711692,41711853,41711863,41711898,41712014,41712034,41712113,41712191,41712507,41712567,41712720,41712777,41713068,41713357,41713358,41713371,41713389,41713408,41713433,41713567,41713591,41713703,41714172,41714406,41714486,41714714,41714782,41714791,41715079,41715088,41715420,41715447,41715644,41715722,41715826,41715897,41715916,41716108,41716680,41716699,41716856,41717131,41717185,41717451,41717480,41717484,41717642,41717664,41717951,41718021,41718114,41718126,41718137,41718185,41718357,41718382,41718483,41718700,41719198,41719656,41719725,41719955,41720188,41720906,41721081,41721783,41721808,41724488,41724554,41726110,41738016,41745319,41745792],"created_at":"2024-10-01T16:04:20Z","created_at_i":1727798660,"num_comments":256,"objectID":"41710227","points":455,"story_id":41710227,"story_text":"Hey it\u2019s Hassaan & Quinn \u2013 co-founders of Tavus, an AI research company and developer platform for video APIs. We\u2019ve been building AI video models for \u2018digital twins\u2019 or \u2018avatars\u2019 since 2020.
We\u2019re sharing some of the challenges we faced building an AI video interface that has realistic conversations with a human, including getting it to under 1 second of latency.
To try it, talk to Hassaan\u2019s digital twin: https://www.hassaanraza.com, or to our "demo twin" Carter: https://www.tavus.io
We built this because until now, we've had to adapt communication to the limits of technology. But what if we could interact naturally with a computer? Conversational video makes it possible \u2013 we think it'll eventually be a key human-computer interface.
To make conversational video effective, it has to have really low latency and conversational awareness. A fast-paced conversation between friends has ~250 ms between utterances, but if you\u2019re talking about something more complex or with someone new, there is additional \u201cthinking\u201d time. So, less than 1000 ms latency makes the conversation feel pretty realistic, and that became our target.
Our architecture decisions had to balance 3 things: latency, scale, & cost. Getting all of these was a huge challenge.
The first lesson learned was to make it low-latency, we had to build it from the ground up. We went from a team that cared about seconds to a team that counts every millisecond. We also had to support thousands of conversations happening all at once, without getting destroyed on compute costs.
For example, during early development, each conversation had to run on an individual H100 in order to fit all components and model weights into GPU memory just to run our Phoenix-1 model faster than 30fps. This was unscalable & expensive.
We developed a new model, Phoenix-2, with a number of improvements, including inference speed. We switched from a NeRF based backbone to Gaussian Splatting for a multitude of reasons, one being the requirement that we could generate frames faster than realtime, at 70+ fps on lower-end hardware. \nWe exceeded this and focused on optimizing memory and core usage on GPU to allow for lower-end hardware to run it all. We did other things to save on time and cost like using streaming vs batching, parallelizing processes, etc. But those are stories for another day.
We still had to lower the utterance-to-utterance time to hit our goal of under a second of latency. This meant each component (vision, ASR, LLM, TTS, video generation) had to be hyper-optimized.
The worst offender was the LLM. It didn\u2019t matter how fast the tokens per second (t/s) were, it was the time-to-first token (tfft) that really made the difference. That meant services like Groq were actually too slow \u2013 they had high t/s, but slow ttft. Most providers were too slow.
The next worst offender was actually detecting when someone stopped speaking. This is hard. Basic solutions use time after silence to \u2018determine\u2019 when someone has stopped talking. But it adds latency. If you tune it to be too short, the AI agent will talk over you. Too long, and it\u2019ll take a while to respond. The model had to be dedicated to accurately detecting end-of-turn based on conversation signals, and speculating on inputs to get a head start.
We went from 3-5 to <1 second (& as fast as 600 ms) with these architectural optimizations while running on lower-end hardware.
All this allowed us to ship with a less than 1 second of latency, which we believe is the fastest out there. We have a bunch of customers, including Delphi, a professional coach and expert cloning platform. They have users that have conversations with digital twins that span from minutes, to one hour, to even four hours (!) - which is mind blowing, even to us.
Thanks for reading! let us know what you think and what you would build. If you want to play around with our APIs after seeing the demo, you can sign up for free from our website https://www.tavus.io.","title":"Show HN: A real time AI video agent with under 1 second of latency","updated_at":"2026-03-10T17:23:59Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"serjester"},"title":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["ai","agent"],"value":"AI agents: Less capability, more reliability, please"},"url":{"matchLevel":"none","matchedWords":[],"value":"https://www.sergey.fyi/articles/reliability-vs-capability"}},"_tags":["story","author_serjester","story_43535653"],"author":"serjester","children":[43535834,43535849,43535855,43535902,43535919,43536049,43536147,43536155,43536226,43536242,43536416,43536506,43536553,43536700,43536781,43536983,43536986,43536997,43537010,43537027,43537189,43537230,43537255,43537299,43537301,43537354,43537496,43537513,43537682,43537707,43537801,43537840,43537850,43537877,43537990,43538030,43538248,43538417,43538425,43538462,43538709,43538871,43538960,43539077,43539126,43539561,43540458,43540486,43540865,43540917,43541284,43542680,43542963,43543231,43543233,43543386,43544333,43544423,43544643,43545035,43549024,43550850,43552258,43562446],"created_at":"2025-03-31T14:45:35Z","created_at_i":1743432335,"num_comments":253,"objectID":"43535653","points":423,"story_id":43535653,"title":"AI agents: Less capability, more reliability, please","updated_at":"2026-05-20T16:26:06Z","url":"https://www.sergey.fyi/articles/reliability-vs-capability"}],"hitsPerPage":20,"nbHits":66523,"nbPages":50,"page":0,"params":"query=AI+agent&advancedSyntax=true&analyticsTags=backend","processingTimeMS":32,"processingTimingsMS":{"_request":{"roundTrip":15},"fetch":{"query":2,"scanning":28,"total":31},"total":32},"query":"AI agent","serverTimeMS":33}