AI · alternatives · 2026
24 alternatives to valv - TS library
Give AI agents safe, scoped access to your database
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
- 2
Give AI agents access to real-time data across 200+ apps
May 2026 · apideck.com · its alternatives →
- 3
- 4VT
Hey HN! We're so excited to show you Val Town (https://val.town)! A "val" is a JavaScript/TypeScript function or value that runs on our servers. We aim to get you from idea to running code in seconds: type code, run it, get its API endpoint, schedule it - all from the browser, in a couple keystrokes. We're a startup of 4 people, mostly in NYC. We've been working on this for 6 months and are eager for feedback from the HN community. Why do we need yet another online coding IDE? While researching devtools[1], I found myself wanting something halfway between Replit and Zapier: a…
2023 · val.town · its alternatives →
- 5
AgentSky▲430Any harness, any LLM — cloud-hosted agents on demand.
Aug 2026 · agentsky.dev · its alternatives →
- 6
A SQL database implemented purely in TypeScript type annotations. - codemix/ts-sql
2020 · github.com · its alternatives →
- 7
- 8
We built OneCLI because AI agents are being given raw API keys. And it's going about as well as you'd expect. We figured the answer isn't "don't give agents access," it's "give them access without giving them secrets." OneCLI is an open-source gateway that sits between your AI agents and the services they call. You store your real credentials once in OneCLI's encrypted vault, and give your agents placeholder keys. When an agent makes an HTTP call through the proxy, OneCLI matches the request by host/path, verifies the agent should have access, swaps the placeholder for the real…
Mar 2026 · github.com · its alternatives →
- 9
Today we released an open, Valkey-native context layer for AI agents as part of our packages at BetterDB (agent memory, semantic + multi-tier caching, typed retrieval) that run on a Valkey instance no matter where it is - no vendor lock-in. We even started provisioning Valkey instances starting today. Packages are shipped on npm and PyPi. Why we made it: BetterDB originally started as a monitoring and observability platform for Valkey, Redis and any RESP compatible db. This is still the core of the product, but in the process of building this, we kept seeing that one of the fastest-growing…
Jun 2026 · github.com · its alternatives →
- 10
- 11
SnapQL is an open-source desktop app (built with Electron) that lets you query your Postgres database using natural language. It’s schema-aware, so you don’t need to copy-paste your schema or write complex SQL by hand. Everything runs locally — your OpenAI API key, your data, and your queries — so it's secure and private. Just connect your DB, describe what you want, and SnapQL writes and runs the SQL for you.
2025 · github.com · its alternatives →
- 12
Hey HN, I’m Austin, founder of Salestrics (salestrics.com). The Problem: > Most AI agents today are trapped in chat windows. While models are smart enough to run complex multi-step workflows, giving them production access to business context (CRM, support, billing) usually means managing unsafe local API keys or hacking together fragile point-solution scripts. What We Built: We built Salestrics to serve as both an all-in-one revenue workspace (CRM, service desk, billing, docs, email) and a production-grade Model Context Protocol (MCP) execution proxy. How It Works: Unified Context: Instead…
Aug 2026 · salestrics.com · its alternatives →
- 13
Datatune ▲38Modern AI tools use SQL/Code generation agents or RAG to access the user data to perform transformations. However, the drawback is that this doesn't provide row-level intelligence, especially in case of semantic intelligence is required to understand how to perform the transfromations on each row of the data. We've released Datatune (https://github.com/vitalops/datatune) as a tool to let users connect entire user Data with LLMs and Agents, to help users access their entire data with just a prompt. While building Agents for a customer who had large amounts of data, we…
Jan 2026 · github.com · its alternatives →
- 14
- 15
- 16
Hey HN, A few months ago, I tried to automate some of my work with the popular AI agent OpenClaw, and then I quickly realized how difficult it is to get it to work with APIs and third-party services securely, which is essential for a lot of work-related tasks. Then I realized OpenClaw is more of a personal assistant and it was not designed to get actual work done as a coworker. So I started to build Valmis, an alternative to OpenClaw that works with more than 100 apps and services, with security being the priority. Valmis addresses the security issue by designing a proxy system: dockerized…
Jul 2026 · github.com · its alternatives →
- 17
AI SQL builder that speaks your language.
Oct 2025 · npmjs.com · its alternatives →
- 18
- 19
Hi HN, i am Dimitris, I have been using Claude Code and Codex agents, for some time now from the beggining i had been using them from inside my terminal mainly for coding. For the past 3 years i kept building so i have a homelab and a business server, which already has a lot of vms, so a lot of things to manage. So i decided to start building my own ideal version of using claude code, and codex flexibly and connect them easily with all my vms and infra but at the same time keep using them for coding, and as a personal assistant for daily use. So for the past months I built OtoDock. Its a…
Sep 2026 · github.com · its alternatives →
- 20
Hey HN, I just spent the last few weeks building a database for agents. Over the last year I built PostHog AI, the company's business analyst agent, where we experimented on giving raw SQL access to PostHog databases vs. exposing tools/MCPs. Needless to say, SQL wins. I left PostHog 3 weeks ago to work on side-projects. I wanted to experiment more with SQL+agents. I built an MVP exposing business data through DuckDB + annotated schemas, and ran a benchmark with 11 LLMs (from Kimi 2.5 to Claude Opus 4.6) answering business questions with either 1) per-source MCP access (e.g. one Stripe…
Apr 2026 · github.com · its alternatives →
- 21
Hi HN, We’re building security tooling around agentic AI systems. Today, we're releasing our public MCP catalog with detailed risk analysis for every MCP server we've found on the internet: https://mcp.armor1.ai/mcp-directory We all love agents and the power that MCPs unlock: suddenly your AI assistant can query databases, manage files, call APIs, and interact with the real world. But when we started adopting MCPs ourselves, we kept running into the same nagging questions: Is this MCP safe? Where is my data actually going? Could it execute destructive actions? Is it…
Feb 2026 · mcp.armor1.ai · its alternatives →
- 22
Hello HN! If you want to connect your agent to a database (say, to build a data analyst chatbot or any kind of agentic app) today you have 2 options: an SQL MCP server or a semantic layer. SQL MCP is the easiest path to setup, especially if you also have a .md knowledge base which the agent can update. It gets quite messy quickly though, especially if there's many interactions or DB is large. Generated SQL is hard to review if you want to understand where the numbers came from, and related queries can be hard to align and compare. The natural alternative is a semantic layer, which is an…
May 2026 · github.com · its alternatives →
- 23AC
Multi-tier exact-match cache for AI agents backed by Valkey or Redis. LLM responses, tool results, and session state behind one connection. Framework adapters for LangChain, LangGraph, and Vercel AI SDK. OpenTelemetry and Prometheus built in. No modules required - works on vanilla Valkey 7+ and Redis 6.2+. Shipped v0.1.0 yesterday, v0.2.0 today with cluster mode. Streaming support coming next. Existing options locked you into one tier (LangChain = LLM only, LangGraph = state only) or one framework. This solves both. npm:…
Apr 2026 · its alternatives →
- 24
I’ve been experimenting with AI agents lately, and one problem kept coming up: they either get a raw API key with full access or nothing at all. That’s risky, especially if you’re testing agents that can make arbitrary calls. So I hacked together a tiny package called Kage Keys - https://github.com/kagehq/keys It lets you wrap agent actions with scoped, short-lived tokens instead of handing over your real API keys. Example: ```js import { withAgentKey, getLogs } from "@kagehq/keys"; async function main() { await withAgentKey("github:repos.read", async () => {…
2025 · github.com · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →