Skip to content
AI NEWS.ccAI正在发生 未来正在更新
Bookmarks
THE JOURNAL
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

Hacker News Show HN

Show HN: Vaultbase – a self-hosted back end in a single binary

One binary to run and you have a full backend at your fingertips: a database with a REST API, sign-in, realtime, files, server-side hooks and jobs, on SQLite or Postgres. It's MIT licensed. You can try the demo at https://demo.vaultbase.sh (the login is filled in, and it resets every hour). I built it to ship fast. I always tend to write the same logic for any new project, whether it's a side project or a small to medium project for a client. I wanted something my friends and I could work with fast, try new things with, and that's easy to use. Then it became something I really wanted to work on and make as complete as I can for any type of backend. As of writing this post it has 80 releases since May this year and is backed by more than 2,800 tests. I also run security reviews with Claude and fix what they find. It hasn't had an outside audit yet. It was built with the help of Claude, from the codebase to the documentation and fact-checking it against the code. Claude helped speed up the pace, find bugs, and write tests. Vaultbase is pre-1.0, so expect some bugs and issues here and there. I'm working hard to fix each and every one of them. Thank you for taking the time to read this. I'd really appreciate any feedback, even if you didn't like Vaultbase. The demo is yours to try, and it's two commands to run locally. Comments URL: https://news.ycombinator.com/item?id=50448562 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Open-source customer-facing agents

Hi, Dmitri from Radioso here, an open-source platform to design AI agents for customers and visitors in any channel, in the style of Fin/Ada/Decagon. The repo is https://github.com/radioso-ai/radioso and our website is https://radioso.aiToday, your choices are:1. Buy a very expensive service for your vertical (usually starting with $$ five figures monthly) 2. Get a cheap off-the-shelf chatbot that mostly answers FAQs 3. Build your own, and then also build the inbox, human handoff, audit trail and integrations around itAt Radioso we wanted an open-source option that combines the best of all 3. You can integrate it with your own software via API/SDK or your CRM, or run it standalone, either self-hosted or in our cloud.The engine runs multi-step interactions and takes actions: calling your APIs, updating records, booking things. Maybe you’ve tried Parlant; Radioso is the alternative “with batteries included”: RAG, audit trail, customer service inbox, and integrations like Slack and email.Under the hood it’s plain TypeScript + PostgreSQL, works with OpenAI/Anthropic/other models, and is licensed under Apache 2.0 which includes all features (The only thing we keep under EE license is the multi-tenant layer we use to run our own cloud).We have existing customers running it for technical Q&A, course booking, online product recommendations and goods returns, among others, some reaching 92% of conversations automated. We’re currently working on voice support so we can offer a call center.Our ambition is to be “the WordPress of customer-facing AI” :), where people can contribute their favorite plugins and benefit from the ecosystem.Longer term, we think browsing the web will mostly mean talking to your own agent, and when you need a service or a purchase, your agent will talk to the vendor’s agent to get things done. For this, Radioso already publishes an A2A Agent Card and we’re working on the rest. Your Radioso services are also callable over MCP, for customers who already use it.Thanks for your attention. We’d especially love to hear which integrations you’d want, whether you’d self-host it, and what’s stopped you from deploying a customer-facing AI agent so far. Tell us what you think. Comments URL: https://news.ycombinator.com/item?id=50423820 Points: 1 # Comments: 0

AWS Machine Learning Blog

Taxonomy of agentic primitives in Amazon Quick

As we built Amazon Quick, its agents grew from answering questions to taking actions, and the same primitives kept getting rebuilt under different names. This post shares the taxonomy we converged on — triggers, agents, capabilities, and learned context — found by decomposing agentic work into four plain questions: When, What, Who, and How.

Vercel

Vercel MCP now supports MCP events

Vercel MCP now enables agents to subscribe to platform events such as deployment.succeeded and deployment.error, allowing real-time reactions to project changes without polling. Subscriptions are filtered by team, project, and environment, managed via expiring webhooks that don't count against the 40 account webhook limit. Events are delivered as signed standard webhooks with Vercel's native payload format.

Vercel

Vercel Connect adds webhook triggers for more providers

Vercel Connect now enables webhook triggers for Resend, X, Twilio, Notion, and Telegram, automatically registering webhooks for Resend and Telegram while requiring manual setup for the others. It verifies requests, handles heartbeats, and forwards events to specified endpoints in Vercel projects, with support for monitoring via the Observability tab. This expands existing trigger support for Slack, Discord, Microsoft Teams, GitHub, and Linear.

ClickHouse

Scaling ClickStack alerting with built-in anomaly detection

Managed ClickStack now flags unusual values on the charts you already use with built-in z-score anomaly detection, and a faster, sharded scheduler lets teams bring tens of thousands of alerts over from tools like Grafana.