Contact PgBeam

Email is the way in. Pick the address that matches what you need, and include enough detail (project slug, region, a rough timestamp) that the first reply can be an answer rather than a question.

Which address should you use?

Support and general questions: support@pgbeam.com: Product questions, bug reports, help with a policy that is not behaving, and anything that does not fit a category below.
Sales and custom limits: sales@pgbeam.com: Volume above the Scale tier, custom connection counts, annual invoicing, procurement paperwork, and security questionnaires.
Security reports: security@pgbeam.com: Vulnerability reports and anything that looks like a way around the guardrails. Include the steps to reproduce. We will not pursue action against good-faith research.
Privacy and data requests: privacy@pgbeam.com: Access, correction, export, and deletion requests, plus GDPR and DPA questions about how data is processed.
Legal: legal@pgbeam.com: Terms of service, the data processing agreement, and contract redlines.

What if something is broken right now?

Check status.pgbeam.com first. It reports the control plane and the gateway regions, so an outage is visible there before anyone has to describe it. If the status page is green and your traffic is not, write to support@pgbeam.com with your project slug, the region, and a rough timestamp. That is enough to find the affected connections in the audit log. The troubleshooting guide covers the failures that turn out to have a local cause.

If an agent is misbehaving and you need it stopped, do not wait for a reply. The kill-switch in the dashboard revokes one credential or every credential on a project immediately, and it does not require rotating your database role.

Where do account and billing questions go?

Plan changes, invoices, receipts, and cancellation are self-serve in the dashboard, through the billing portal. Write to sales@pgbeam.com if you need an invoice changed, a refund considered, or terms that the portal cannot express.

Can an agent get an answer without emailing anyone?

Usually, yes. The documentation is served as Markdown to any client that asks for it: request a page with Accept: text/markdown, or append .md to its URL. The site also publishes machine-readable indexes so an agent can find the rest on its own.

/llms.txt: the site index, written for language models, including every developer resource below.
/llms-full.txt: the full documentation as one plain-text document.
/docs: the documentation, including the PgBeam REST API, CLI, TypeScript SDK, and Go SDK references.
/openapi.json: the PgBeam REST API described as OpenAPI 3.1.
/skill.md and /auth.md: how to install the CLI, authenticate, and provision a scoped credential, written for a coding agent to follow unattended.
/docs/mcp: the hosted PgBeam MCP server, its tools, and how to point an MCP client at it.

What should a compliance review ask for?

Start with the public documents, because they answer most of a questionnaire without a thread: the security overview, the terms of service, the privacy policy, and the data processing agreement. Anything they do not cover goes to legal@pgbeam.com for contractual questions, or security@pgbeam.com for technical ones.