Google AlloyDB

Reads tables from a Google AlloyDB instance. AlloyDB is PostgreSQL-compatible, so it connects exactly like a self-hosted Postgres database. Flitch only issues read queries, so it can never write to your database.

Add a source

AlloyDB supports a connection string (a database user over TLS).

Prerequisites

An AlloyDB instance reachable from Flitch (a public IP, or private IP with connectivity to Flitch's connector).
A user with read access to the tables you want.

Create a read-only user

CREATE USER flitch_readonly WITH PASSWORD 'choose-a-strong-password';
GRANT CONNECT ON DATABASE mydb TO flitch_readonly;
GRANT USAGE ON SCHEMA public TO flitch_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO flitch_readonly;

Build the connection string

Copy the instance IP from the AlloyDB console (your instance → Connectivity).

postgresql://flitch_readonly:password@10.x.x.x:5432/mydb?sslmode=require

Open the form

Go to Data → Add → AlloyDB, paste the connection string, then pick datasets.

Network access

Flitch connects from its own server, not your browser. AlloyDB uses a private IP by default, so make it reachable from Flitch (for example via a public IP or by allowing Flitch's connector egress IP, shown in the Add Source form, on the database port).

Team-wide credential (optional)

A team admin can store one shared credential in Settings → Data connections; new connections then default to it, with no per-connection secret.

Refresh

Refresh is off by default. Enable it to schedule a background refresh and serve from cache between runs. See Refresh.

Troubleshooting

Connection timed out. AlloyDB is on a private IP that Flitch can't reach. Expose a public IP or route Flitch's egress IP to the instance.

Authentication failed. Check the user and password, and that the user can connect from any host.

SSL required. Keep sslmode=require.

Google AlloyDB

On this page