A full-viewport ASCII world transforms from an open aperture into a data passage and a layered database. Query decisions change the aperture into a protective sphere or a closed gate.
00 / the aperture
connection.open

SOFTWARE FOR PEOPLE WITH DATABASES

A small door.
A safer way in.

Give your people access to production. Keep the credentials, policies, and sensitive fields under your control.

Get early access ↗Try a command ↓

Your database. Your tools. A little less friction.

Scroll to step inside

PostgreSQL psql · DBeaver · TablePlus

THE LIFE OF ONE QUERY

A familiar command.
A different kind of access.

A query travels in. A considered answer comes back. Your credentials stay inside your network.

FOLLOW A QUERY

01 / A FAMILIAR BEGINNING

It starts where you work.

Your terminal. Your database client. Open a local connection with Relay, and keep the tools you already know.

rafael@local:~
$ relay connect pg-prod↳ local connection ready>_

↳ The database credentials stay with the agent.

Open this connection

02 / A QUERY, WITH CONTEXT

A name behind every query.

Relay knows who is asking. The agent checks your query policies before forwarding the statement to the database.

member / rafael@example.com
select email, cardfrom customers limit 3; policy → allowed

↳ The rules belong to your team.

Run this query

03 / A CONSIDERED RESPONSE

The answer knows its audience.

The data stays in your infrastructure. On the way back, masking shapes the response for the person at the keyboard.

response / member view
email  a***@example.comcard   **** **** **** 2718 3 rows → returned

↳ Same query. A different view for each identity.

Compare the identities

An illustrated local session. All records are fictional.

01 / A LOCAL SESSION

Make yourself at home.

A terminal, a fictional database, and room to experiment. Nothing here touches production.

relay@pg-prod:~

Ready when you are.

Try a command below, or type help to look around.

LOCAL SIMULATION / fictional data / ↑ ↓ command history

When you’re ready for your own terminal:

02 / A CONSIDERED BOUNDARY

Same query. Different view.

The person at the keyboard matters. Change the identity and see what comes back.

your clientpsql / 127.0.0.1Relay agentidentity → policy → maskyour databasepg-prod
Fig. 02 — the answer depends on the personinside your network

Query policies on the way in. Identity-aware masking on the way out.

View as
rafael@example.com
idemailcard
1042a***@example.com**** **** **** 2718
1043r***@example.com**** **** **** 0461
1044p***@example.com**** **** **** 8823

↳ Sensitive fields partially masked for the member.

Fictional records. Masking is determined by the selected role.

03 / FIELD NOTES

Less to carry around.

A few things we think good database access should make possible.

Leave the passwords behind.

Your identity gets you in. Relay’s agent resolves database credentials inside your network, so your team doesn’t need to pass them around.

Keep the tools you like.

Use a local connection with the PostgreSQL clients you already know. A new boundary doesn’t have to mean a new workflow.

Give every query a little context.

Who ran it, which database, which decision. Policies and audit events make access something you can understand and adjust.

— Built for people who care about their tools.

Does Relay host my database?

No. Your database stays on your infrastructure. Relay’s agent runs alongside it and controls how clients get access.

Can I use my existing database client?

Yes. Relay connects native database clients through a local port. You can keep using tools such as psql, DBeaver, and TablePlus.

Is this a real database connection?

This page is a local simulation with fictional records. The terminal, masking example, and session log run entirely in your browser.

04 / AN OPEN INVITATION

Good work needs a way in.

Leave your email to join Relay’s early access list.

Your email is used for early access updates.

One connection at a time.