Sferarc builds developer infrastructure for PostgreSQL and for the AI agents that talk to it. Several separate projects live here. PgBeam is the largest, and it is not the whole of them: alongside it are standalone Go libraries and a language-neutral conformance corpus, each released on its own and usable with nothing else from this organization installed.

Everything published here is Apache-2.0. Issues and pull requests are welcome on all of it — see CONTRIBUTING.md, and SECURITY.md for reporting a vulnerability privately rather than in a public issue.

Each solves one problem, needs nothing else from this organization, and is versioned and released independently. They were written while building PgBeam, which is the reason they exist and not the limit of where they are useful.

go get github.com/sferarc/pgscram

Produce and read PostgreSQL's stored SCRAM-SHA-256 verifier — the SCRAM-SHA-256$<iterations>:<salt>$<StoredKey>:<ServerKey> string that lives in pg_authid.rolpassword. Derive one from a password and hand it straight to CREATE ROLE … PASSWORD, and the plaintext never reaches the server.

For anyone who issues or holds Postgres credentials: a pooler, a wire-protocol proxy, a control plane that provisions roles, a migration moving credentials between systems. It is deliberately not a SCRAM authentication implementation — it is the on-disk format only, and composes with xdg-go/scram for the RFC 5802 exchange. No dependencies outside the standard library; needs Go 1.24 for crypto/pbkdf2.

go get github.com/sferarc/schemadigest

Read a PostgreSQL catalog over a pgx connection and reduce it to a compact JSON summary sized for a language model's context: qualified table names, approximate row counts from pg_class.reltuples, comments, primary keys, foreign keys rendered as col -> ref_table(ref_col), and per column only the name, the type and a masked flag.

Two halves that are usable separately — Read is a plain catalog reader over four catalog queries, and From is the opinionated reduction. For text-to-SQL and agent tooling that would otherwise paste a pg_dump --schema-only into the prompt.

go get github.com/sferarc/auditchain

Tamper-evident append-only logs. Records are hashed into a chain and keyed with an HMAC, so editing a record, deleting from the middle, rehashing the tail, or continuing past a truncation are all detectable by an offline walk of the stored rows.

The threat model is stated plainly in the README, including the one attack a hash chain cannot catch on its own — truncating the tail and stopping — and the anchor subpackage of Merkle checkpoints that closes it. The core package has no dependencies outside the standard library; anchor is the only thing that pulls in transparency-dev, and only if you import it.

A language-neutral corpus of (policy, statement) → expected decision cases for wire-level Postgres policy enforcement: 44 cases across 10 profiles, covering read-only mode, statement allowlists, fail-closed input handling, relation allow/deny matching, column masking, row filters, lock-taking DDL, and bounded write counts.

For anyone building a proxy, an MCP server, or a driver shim that stands between an agent and a database and wants "the policy is enforced" to be a checkable claim rather than a marketing one. The vectors are one implementation's answers, published as such and not as a standard — running them against something else and publishing the diff is the intended use.

Safe Postgres access for AI agents — https://pgbeam.com

PgBeam is a globally distributed PostgreSQL proxy that enforces policy in the wire protocol, so an agent gets a scoped credential instead of your database password. Read-only mode, table and column allowlists, row filters, PII masking, query budgets and a kill-switch are all decided before a statement reaches your database, and every decision lands in a tamper-evident audit log. Connection pooling and query caching come with it. It works with any Postgres host and needs no application changes: swap the connection string, or point the agent at the hosted MCP endpoint. Using it needs an account.

• Documentation: https://pgbeam.com/docs
• Quickstart: https://pgbeam.com/docs/quickstart
• Security practices: https://pgbeam.com/security
• Status: https://status.pgbeam.com

The proxy and the control plane are developed privately. These are the published parts: