HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
CerebriumAI
examples
Python2024–2025
CerebriumAI / examples

examples

Examples for Cerebrium Serverless GPUs

4Distinct people
5Mentions
0Explicit recommenders
526GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Examples for Cerebrium Serverless GPUs

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2024-07-24 13:41:10 UTC to 2025-02-25 15:37:58 UTC. Weeks start Monday, UTC.

0122024-07-22 00:00:00 UTC to 2024-07-29 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 222024-07-29 00:00:00 UTC to 2024-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-05 00:00:00 UTC to 2024-08-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-12 00:00:00 UTC to 2024-08-19 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2024-08-19 00:00:00 UTC to 2024-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 00:00:00 UTC to 2024-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-02 00:00:00 UTC to 2024-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-09 00:00:00 UTC to 2024-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-16 00:00:00 UTC to 2024-09-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-09-23 00:00:00 UTC to 2024-09-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-30 00:00:00 UTC to 2024-10-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-07 00:00:00 UTC to 2024-10-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-14 00:00:00 UTC to 2024-10-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-21 00:00:00 UTC to 2024-10-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-28 00:00:00 UTC to 2024-11-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-04 00:00:00 UTC to 2024-11-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 42024-11-11 00:00:00 UTC to 2024-11-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-18 00:00:00 UTC to 2024-11-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-25 00:00:00 UTC to 2024-12-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-02 00:00:00 UTC to 2024-12-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-09 00:00:00 UTC to 2024-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-16 00:00:00 UTC to 2024-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-23 00:00:00 UTC to 2024-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-30 00:00:00 UTC to 2025-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-06 00:00:00 UTC to 2025-01-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-13 00:00:00 UTC to 2025-01-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-20 00:00:00 UTC to 2025-01-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-27 00:00:00 UTC to 2025-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-03 00:00:00 UTC to 2025-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-10 00:00:00 UTC to 2025-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-17 00:00:00 UTC to 2025-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-24 00:00:00 UTC to 2025-03-03 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 24

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 222024-07-22 00:00:00 UTC2024-07-29 00:00:00 UTC110
Jul 292024-07-29 00:00:00 UTC2024-08-05 00:00:00 UTC000
Aug 52024-08-05 00:00:00 UTC2024-08-12 00:00:00 UTC000
Aug 122024-08-12 00:00:00 UTC2024-08-19 00:00:00 UTC220
Aug 192024-08-19 00:00:00 UTC2024-08-26 00:00:00 UTC000
Aug 262024-08-26 00:00:00 UTC2024-09-02 00:00:00 UTC000
Sep 22024-09-02 00:00:00 UTC2024-09-09 00:00:00 UTC000
Sep 92024-09-09 00:00:00 UTC2024-09-16 00:00:00 UTC000
Sep 162024-09-16 00:00:00 UTC2024-09-23 00:00:00 UTC101
Sep 232024-09-23 00:00:00 UTC2024-09-30 00:00:00 UTC000
Sep 302024-09-30 00:00:00 UTC2024-10-07 00:00:00 UTC000
Oct 72024-10-07 00:00:00 UTC2024-10-14 00:00:00 UTC000
Oct 142024-10-14 00:00:00 UTC2024-10-21 00:00:00 UTC000
Oct 212024-10-21 00:00:00 UTC2024-10-28 00:00:00 UTC000
Oct 282024-10-28 00:00:00 UTC2024-11-04 00:00:00 UTC000
Nov 42024-11-04 00:00:00 UTC2024-11-11 00:00:00 UTC000
Nov 112024-11-11 00:00:00 UTC2024-11-18 00:00:00 UTC000
Nov 182024-11-18 00:00:00 UTC2024-11-25 00:00:00 UTC000
Nov 252024-11-25 00:00:00 UTC2024-12-02 00:00:00 UTC000
Dec 22024-12-02 00:00:00 UTC2024-12-09 00:00:00 UTC000
Dec 92024-12-09 00:00:00 UTC2024-12-16 00:00:00 UTC000
Dec 162024-12-16 00:00:00 UTC2024-12-23 00:00:00 UTC000
Dec 232024-12-23 00:00:00 UTC2024-12-30 00:00:00 UTC000
Dec 302024-12-30 00:00:00 UTC2025-01-06 00:00:00 UTC000
Jan 62025-01-06 00:00:00 UTC2025-01-13 00:00:00 UTC000
Jan 132025-01-13 00:00:00 UTC2025-01-20 00:00:00 UTC000
Jan 202025-01-20 00:00:00 UTC2025-01-27 00:00:00 UTC000
Jan 272025-01-27 00:00:00 UTC2025-02-03 00:00:00 UTC000
Feb 32025-02-03 00:00:00 UTC2025-02-10 00:00:00 UTC000
Feb 102025-02-10 00:00:00 UTC2025-02-17 00:00:00 UTC000
Feb 172025-02-17 00:00:00 UTC2025-02-24 00:00:00 UTC000
Feb 242025-02-24 00:00:00 UTC2025-03-03 00:00:00 UTC101

What Hacker News says

5 sources
There is a new AI agent that generates Next.js apps based on prompt. Features: - Plans frontend component architecture - Generates code in real-time based on commands - Deploys code to a secure sandboxed environment for testing - Works with any LLM - It's all built on top of Cerebrium and E2B Complete guide to building the agent: https://www.cerebrium.ai/blog/building-a-real-time-coding-as... Source Code: https://github.com/CerebriumAI/examples/tree/master/8-applic...
In Open-source alternative to v0, Lovable, bolt

Show HN: Turning a Live Video into Instant Purchases Using AI

Hi HN I am the founder of Cerebrium (https://www.cerebrium.ai), a serverless AI infrastructure platform. We released a demo showcasing a live shopping assistant - it allows you to monitor any live stream and picks up items instantaneously so that users can search/buy them. We wanted to showcase a use case for how you can extract data from a video live and deliver value to the end user immediately. It would be great to get the community to give feedback on what we could do to improve the demo (besides those mentioned below) as well as extend the demo to be much better. More importantly, if this sparks you to create something better please share it with us! You can see more in depth information here: Live Demo: https://live-stream-shopper.cerebrium.ai/ - this is very basic right now. Tutorial Blog post: https://www.cerebrium.ai/blog/buildin
Read the rest
g-a-real-time-shopping-... Code here: https://github.com/CerebriumAI/examples/tree/master/27-ecomm... Basic Flow We use a variety of tools in order to achieve the end-to-end functionality. - *Daily* - We use Daily to extract video frames from the live stream every 150ms. This allows us to run object detection and our search function on each frame. - *Yolov8*: We use a custom trained Yolov8 model to detect objects in our live stream that we must search for. - *Turso*: We store our product catalog in Turso's embedding database that searches for matches against the detected objects. - *Supabase*: We use Supabase to store detected images and we store items found via our search function in a database that allows our client application to update with the results in real-time. - *Serp API* (Bonus): We use the SERP API to search Google for a product match using only the image of the detected item. - *Cerebrium*: The entire solution is hosted on Cerebrium serverless CPU/GPUs. It manages all auto-scaling and orchestration. ### Things to improve - Instead of only detecting a class image once and never again, I would store the embeddings of previously searched items and if an image makes it through the search criteria you can compare it to past embeddings. This means you could search multiple books, cups etc. - Train a better model. We trained our model on 6 classes (book, shoe, watch, cup etc) and about 40 images. Depending on your use case, I would train it on a lot more data for your use case to get more accurate. - Facebook recently released their SAM 2 model that can follow items through a video. It would be very cool to incorporate this, showing a user what items have already been searched as time progresses. - If a user has a bad camera, the accuracy of the YOLO model is much lower. I would recommend training on a diverse set of data across different quality cameras.
3 points · Open discussion
AdamRomyn·Aug 14, 2024Submission

Show HN: Turning a Live Video Stream into Real-Time Purchases With AI

Hi HN We released a demo showcasing a live shopping assistant - it allows you to monitor any live stream and picks up items instantaneously so that users can search/buy them. We wanted to showcase a use case for how you can extract data from a video live and deliver value to the end user immediately. It would be great to get the community to give feedback on what we could do to improve the demo (besides those mentioned below) as well as extend the demo to be much better. More importantly, if this sparks you to create something better please share it with us! You can see more in depth information here: Live Demo - (https://live-stream-shopper.cerebrium.ai/) - this is very basic right now. Tutorial Blog post - (https://www.cerebrium.ai/blog/building-a-real-time-shopping-...) Code here - (https://github.com/CerebriumAI/examples/tree/master/2
Read the rest
7-ecomm...) Basic Flow: We use a variety of tools in order to achieve the end-to-end functionality. - Daily - We use Daily to extract video frames from the live stream every 150ms. This allows us to run object detection and our search function on each frame. - Yolov8: We use a custom trained Yolov8 model to detect objects in our live stream that we must search for. - Turso: We store our product catalog in Turso's embedding database that searches for matches against the detected objects. - Supabase: We use Supabase to store detected images and we store items found via our search function in a database that allows our client application to update with the results in real-time. - Serp API (Bonus): We use the SERP API to search Google for a product match using only the image of the detected item. - Cerebrium: The entire solution is hosted on Cerebrium serverless CPU/GPUs. It manages all auto-scaling and orchestration. Things to improve - Instead of only detecting a class image once and never again, I would store the embeddings of previously searched items and if an image makes it through the search criteria you can compare it to past embeddings. This means you could search multiple books, cups etc. - Train a better model. We trained our model on 6 classes (book, shoe, watch, cup etc) and about 40 images. Depending on your use case, I would train it on a lot more data for your use case to get more accurate. - Facebook recently released their SAM 2 model that can follow items through a video. It would be very cool to incorporate this, showing a user what items have already been searched as time progresses. - If a user has a bad camera, the accuracy of the YOLO model is much lower. I would recommend training on a diverse set of data across different quality cameras.
3 points · Open discussion

Show HN: A personalised AI tutor with < 1s voice responses

TLDR: We created a personalised Andrej Karpathy tutor that can response to questions about his Youtube videos in sub 1 second responses (voice-to-voice). We do this using a voice enabled RAG agent. See later in the post for demo link, Github Repo and blog write up. A few weeks ago we released the worlds fastest voice bot, achieving 500ms voice-to-voice response times, including a 200ms delay waiting for a user to stop speaking. After reaching the front page of HN, we thought about how we could take this a step further based on feedback we were getting from the community. Many companies were looking for a way to implement function calling and RAG with voice interfaces while retaining a low enough latency. We couldn’t find many resources about how to do this online that: 1. Allowed us to achieve sub-second voice-to-voice latency 2. Was more
Read the rest
flexible than existing solutions. Vapi, Retell, [Bland.ai](http://Bland.ai) are too opinionated plus since they just orchestrate API’s which incur network latency at every step. See requirement above 3. The unit economics actually work at scale. So we decided to create a implementation of our own. Process: As we mentioned in our previous release, if you want to achieve response times this low you need to make everything as local as possible. So below was our setup - Local STT: Deepgram model - Local Embedding model: Nomic v1.5 - Local VectorDB: Turso - Local LLM: Llama 3B - Local TTS: Deepgram model From our previous example, the only new components where: - Local Embedding model: We chose Nomic Embed text v1.5 model that gave a processing time of roughly ~200ms - Turso offers local embedded replicas combined with edgeDB’s which meant we were able to achieve 0.01 second read times. Pinecone also gave us good times of 0.043 seconds. The above changes led us to achieve sub 1 second voice-to-voice response times Application: With Andrej Karpathy’s announcement around [Eureka Labs](https://eurekalabs.ai/), a new AI+Education company we thought we would create our very own personalised Andrej tutor. Listen to anyone of his Youtube lectures, as soon as your start specking, the video will pause and he will reply. Once your question has been answered you can then tell him to continue with the lecture and the video will automatically start playing. Demo: https://educationbot.cerebrium.ai/ Blog: https://www.cerebrium.ai/blog/creating-a-realtime-rag-voice-... Github Repo: https://github.com/CerebriumAI/examples/tree/master/19-voice... For demo purposes: - We used OpenAI for GPT-4-mini and embeddings (its cheaper to run on a CPU than GPU’s when running demos at scale. These changes add about ~1 second to the response time - We used Eleven labs to clone his voice to make replies sound more realistic. This adds about 300ms to the response time. The improvements that can be made which we would like the community to contribute to are: - Embed the video screens as well that when you ask certain questions it can show you the relevant lecture slide for the same chuck that it got context from to answer. - Insert the timestamps in the vectorDB timestamps so that if a question will be answered later in the lecture he can let you know This unlocks so many use cases in education, employee training, sales etc that it would be great to see what the community builds!
72 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.