Show HN: SerenDB – A Neon PostgreSQL fork optimized for AI agent workloads

Show HN (score: 6)
Found: October 22, 2025
ID: 2039

Description

Database
Show HN: SerenDB – A Neon PostgreSQL fork optimized for AI agent workloads Show HN: SerenDB – Neon PostgreSQL fork optimized for AI agent workloads

We forked Neon to make database operations faster and safer for AI agents. The goal is to enable instant experimentation with production data and catch prompt injection attacks before they hit your DB. The open-source repo is at https://github.com/serenorg/serendb

The coolest current features are:

1. Time-travel queries: Query your database as it existed at any timestamp. SELECT * FROM orders AS OF TIMESTAMP '2024-01-15 14:30:00'. Essential for debugging agent decisions and auditing what data an agent saw.

2. Scale-To-Zero with pgvector: Built-in vector embeddings that sleep when idle. Pay nothing for dormant agent databases, auto-scale to 16 vCPU when needed.

The coolest features in development are:

1. Prompt injection detection: Fingerprinting and context-aware policies to catch injection attempts before they reach your data. We're extending Postgres's security model to understand AI-specific attack patterns.

2. 100ms branch creation: Clone your entire production database in 100ms (vs Neon's 500ms). Enables branch-per-agent patterns and instant rollback. Great for faster testing of multiple prompt variations on real data.

This is early - we're working on the hosted service now.

Technical folks: curious if anyone else is hitting the "how do I safely test my agent on prod data" problem. Happy to answer questions about our updates to the branching architecture or our proposed context security approaches.

Website: https://serendb.com/

More from Show

Show HN: Control Claude permissions using a cloud-based decision table UI

Show HN: Control Claude permissions using a cloud-based decision table UI We’ve been building visual rule engines (clear interfaces + API endpoints that help map input data to a large number of outcomes) for a while and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.<p>The result is a surprisingly useful policy&#x2F;gating layer– these tables let your team:<p>- Write multi-factor, exception-friendly policies (e.g. deny rm -rf &#x2F; when --force; allow cleanup only in node_modules; ask on network calls like curl&#x2F;wget; block kubectl delete or SQL DROP, each with a clear reason)<p>- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull, agent restart, or coordination)<p>- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP&#x2F;skills&#x2F;etc)- just add columns&#x2F;rules as new tools and metadata show up<p>- Get a quick central utility to understand which tools are being used, which tools get blocked most often, and why

Show HN: Claude Code Scheduler

Show HN: Claude Code Scheduler I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that.<p>To install: &#x2F;plugin marketplace add jshchnz&#x2F;claude-code-scheduler &#x2F;plugin install scheduler@claude-code-scheduler<p>Then just tell Claude what you want (some examples):<p>Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers.<p>Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error handling gaps, and code that needs comments. Summarize with file:line references.

Show HN: Webctl – Browser automation for agents based on CLI instead of MCP

Show HN: Webctl – Browser automation for agents based on CLI instead of MCP

Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT

Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT

No other tools from this source yet.