This is a submission for the Bright Data AI Web Access Hackathon
We built NewsPulse AI to explore a simple but powerful question:
"What if you cou...
For further actions, you may consider blocking this person and/or reporting abuse
Been cool seeing steady progress - it adds up. What do you think actually keeps things growing over time? Habits? Luck? Just showing up?
I think it's mostly habits and consistency. Even on days when things arenβt perfect, just showing up makes a difference over time.
Super impressive to see the real-time insights without any DB in the loop. Really curious, how do you handle scaling when queries spike up?
Absolutely β scaling is definitely something weβre thinking about for the next stage.
Right now, the system is optimized to meet the hackathon goals: fully real-time, stateless, and DB-free, focusing on live data access and analysis. It performs well under moderate load and showcases the core value of Bright Dataβs infrastructure.
But for production-level traffic or query spikes, weβd definitely need to:
Implement request queues and concurrent workers
Add rate-limiting to protect both system and target sites
Possibly introduce a temporary cache layer (e.g., Redis) for recent results
And eventually move to autoscaling infrastructure like AWS Fargate or GCP Cloud Run
So yes, the current setup is hackathon-ready β but scaling and load management are high on the roadmap as we evolve this into a production-grade tool. π
The Github link in this blog post is broken.
I have update the repo url
Suggestion - After the news analysis gets completed, it would be great to programmatically scroll to the "Article Analysis" section.
Added the scroll brother, thanks
Loved the idea!!
I had a question though β I noticed you used the API
https://api.brightdata.cominstead of@brightdata/mcpHow does that work? Does@brightdata/mcpuse the API under the hood, or are they two separate things? In the documentation, the only method I saw was using@brightdata/mcp.Heyy thanks! Glad you liked it π
Yes, the @brightdata/mcp use the same api.
So actually, I just took Bright Dataβs FastMCP server code and plugged it into my Express backend directly. Basically doing the same thing as @brightdata/mcp, just manually. I'm still using api.brightdata.com under the hood, but with a bit more control on how things run.
Very interesting and impressive project!
But what makes it different to say engines like ground.news/ ?
Thanks for the great question! π
Ground News offers static, outlet-level bias insights.
NewsPulse AI gives dynamic, live, article-level intelligence.
Right now, we use OpenAI for content analysis, but weβre already planning to train our own models tailored for news sentiment, propaganda detection, and political bias β optimized for real-time media monitoring and transparency.
That's really cool!
I am definitely going to keep an eye out for your continued development! :)