This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
OpsGraph
Evidence-first agentic investigations for PostgreSQL
OpsGraph is a self-hosted, public-validation alpha for evidence-first PostgreSQL investigations. A model may propose bounded read-only queries; OpsGraph enforces schema and table scope, timeouts, row limits, policy gates, source-owned evidence bindings, citations, and a local audit chain. Start with the bundled synthetic workspace. Use only synthetic data or non-production replicas for now.
The idea started from a fairly simple constraint: an AI system investigating operational data probably shouldn’t be given an unrestricted database connection and a vague prompt.
So for this alpha, I’ve intentionally kept the scope narrow:
a separately provisioned, read-only PostgreSQL role
AST-validated, bounded `SELECT` queries executed in read-only transactions
source-owned evidence bindings, so the model can’t simply declare its own evidence coverage
evidence hashes and a local tamper-evident audit chain
local-first operation, with cloud-model egress only when explicitly enabled
This is still a public-validation alpha, not something intended for production or customer data.
I’d especially appreciate feedback from platform, SRE, and data teams: what would you need to see before you’d feel comfortable trusting a self-hosted investigation workspace against a non-production replica?
About OpsGraph on Product Hunt
“Evidence-first agentic investigations for PostgreSQL”
OpsGraph was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #60 on the daily leaderboard. OpsGraph is a self-hosted, public-validation alpha for evidence-first PostgreSQL investigations. A model may propose bounded read-only queries; OpsGraph enforces schema and table scope, timeouts, row limits, policy gates, source-owned evidence bindings, citations, and a local audit chain. Start with the bundled synthetic workspace. Use only synthetic data or non-production replicas for now.
On the analytics side, OpsGraph competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how OpsGraph performed against the three products that launched closest to it on the same day.
Who hunted OpsGraph?
OpsGraph was hunted by Arittra Bag. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of OpsGraph including community comment highlights and product details, visit the product overview.
Arittra Bag
Hi, I’m Arittra, and I’ve been building OpsGraph.
The idea started from a fairly simple constraint: an AI system investigating operational data probably shouldn’t be given an unrestricted database connection and a vague prompt.
So for this alpha, I’ve intentionally kept the scope narrow:
a separately provisioned, read-only PostgreSQL role
AST-validated, bounded `SELECT` queries executed in read-only transactions
source-owned evidence bindings, so the model can’t simply declare its own evidence coverage
evidence hashes and a local tamper-evident audit chain
local-first operation, with cloud-model egress only when explicitly enabled
This is still a public-validation alpha, not something intended for production or customer data.
I’d especially appreciate feedback from platform, SRE, and data teams: what would you need to see before you’d feel comfortable trusting a self-hosted investigation workspace against a non-production replica?