Database

Your database. Your rules.
Your speed.

Relpin uses per-org Postgres data planes, server-side SQL execution, and governed connector paths. BYOD and broader data-source connectors are planned expansions.

Start building See It In Action
Query Console
Connected
Query
1SELECT
2 o.id,
3 o.status,
4 c.name AS customer,
5 SUM(li.total) AS amount
6FROM orders o
7JOIN customers c ON c.id = o.customer_id
8JOIN line_items li ON li.order_id = o.id
9WHERE o.created_at > '2025-01-01'
10GROUP BY o.id, c.name
11ORDER BY amount DESC
12LIMIT 50;
Dedicated Postgres

One org. Governed data plane.
Clear environment boundaries.

Relpin is built around a DB-per-org baseline with DEV, TEST, and PROD environment schemas, plus a DB-per-env path for enterprise isolation needs.

01
Org data plane

Every organization gets a dedicated Postgres with schemas owned at the org scope.

02
Environment boundary

DEV, TEST, and PROD schemas keep environment boundaries explicit and queryable.

03
Server-side access

Tenant DB credentials stay env-backed and server-side — never reach the browser.

Dedicated Postgres
Multi-tenant (others)
× Shared database for all tenants
× tenant_id on every table
× Row-level security policies required
× Shared connection pool
× Isolation depends on policy correctness
Dedicated (Relpin)
✓ Org-owned data plane
✓ Environment-scoped schemas
✓ Server-side credential handling
✓ Transaction-local settings
✓ Enterprise DB-per-env path
DB-per-org baseline with schema ownership scoped by organization
Environment schemas keep DEV, TEST, and PROD boundaries explicit
Tenant DB access stays server-side and env-backed
Enterprise path supports stronger DB-per-env isolation
DB-per-org baseline · Environment schemas · Server-side access · DB-per-env path
Query Engine

SQL on the server.
Not in the browser.

Queries execute server-side in native SQL. Sorting, filtering, aggregation, and pagination are pushed to Postgres — not loaded into browser memory.

01
Pushdown-first

Filters, sorts, and pagination compile to SQL. Publish fails if a query would evaluate client-side.

02
Server execution

Queries run inside Postgres — no 100k-row browser memory hot loops.

03
Native dialect

Parameterized SQL with schema-qualified table names — typed bindings, no string concat.

Query Engine
Query Definition
1const ordersQuery = defineQuery({)
2 table: 'orders',
3 select: ['id', 'status', 'total'],
4 joins: [{
5 table: 'customers',
6 on: 'customer_id'
7 }],
8 where: { status: 'completed' },
9 orderBy: { total: 'desc' },
10 limit: 100
11})
Server-side SQL execution — no client-side data processing
Sorting, filtering, and pagination pushed to Postgres
Parameterized query paths reduce SQL-injection surface
Pushdown-first — publish fails if a filter requires client evaluation
Server-side SQL · Parameterized · Pushdown-first · Production-safe
BYOD Coming Soon

Your Postgres.
Your infrastructure.

Planned BYOD support will target existing Postgres infrastructure while preserving server-side credential handling and tenant routing guardrails.

01
Bring your own Postgres

Target existing instances without surrendering server-side credential boundaries.

02
Credential boundary

Tenant DB credentials stay in server-side environment or secret bindings — out of browser reach.

03
Routing guardrails

Per-org and per-environment routing checks remain enforced through the same control plane.

BYOD
Connection Config
Host
db.acme-corp.internal
Port
5432
Database
relpin_prod
User
relpin_svc
SSL Mode
verify-full ▼
Test Connection
Target existing Postgres instances without exposing credentials to the browser
Keep tenant DB credentials in server-side environment or secret bindings
Preserve per-org and per-environment routing checks
Treat private networking and failover as enterprise implementation details
BYOD Postgres planned · Server-side credentials · Tenant routing guardrails
Connectors Available Catalog Planned

Slack is the reference connector.
Broader catalog planned.

The governed invocation framework is live today. Slack is the reference connector — server-side calls with idempotency keys, retries, SSRF-guarded egress, and capability gates. A broader database, API, and custom source catalog is planned through the same framework.

01
Governed invocation

Connector calls run server-side through a queued worker with idempotency keys, retries, and capability gates.

02
Slack reference connector

Slack ships today as the reference connector — SSRF-guarded egress, capability gating, and audited invocations.

03
Catalog roadmap

Database, REST, GraphQL, and custom source connectors are planned through the same governed framework.

Connectors
Connector Registry
PostgreSQL
connected
Slack
connected
MySQL
planned
MongoDB
planned
REST API
planned
GraphQL
planned
Slack ships today as the governed reference connector
Server-side invocations with idempotency keys, retries, and SSRF-guarded egress
Connector instances store config and secret references, never browser secrets
Database, API, and custom source breadth is planned on the connector roadmap
Slack connector live · Governed invocation · SSRF-guarded · Capability gates
Use Cases

What teams build on it.

From analytics dashboards to compliance reporting, the database layer powers every data-driven internal tool.

Analytics

Analytics dashboards

Operational dashboards with server-side aggregations, filters, and drill-down views on governed data.

Data Management

Data management tools

CRUD interfaces with validation, search, bulk operations, and governed mutation paths.

Customer 360

Customer 360 views

Customer views over governed data sources as connector breadth grows.

Audit & Compliance

Audit & compliance reporting

Tenant audit events with SQL-queryable history, filtered by actor, action, and time range.

Data Migration

Data migration pipelines

Schema and data changes routed through reviewed, auditable platform operations.

Multi-source Reports

Multi-source reporting

Combine app data with additional governed sources as connector coverage expands.

Ops use cases · Assignment starter · Governed data paths
Database

Stop querying in the browser.
Start querying in SQL.

DB-per-org data plane. Server-side SQL. Governed connector calls. Built for teams that take operational data seriously.

Start building Explore the platform

Open beta · Demo workspace included · Governance-focused

Server-side SQL · Tenant-isolated · Env-backed DB access · Governed connectors