Parameterized compilation
Typed filters and values compile into parameterized SQL with allowlisted, schema-qualified identifiers.
Server-side SQL
Keep query work in Postgres, not in the browser.
Relpin compiles typed filters, sorts, and pagination into parameterized, schema-qualified SQL. The runtime resolves tenant and environment scope before returning only the working set the app requested.
assignments · dev 12 columns · 5 rows
| Employee | Project | Status | Alloc |
|---|---|---|---|
| Mina Alvarez | Northwind Rollout | ACTIVE | 40% |
| Jonah Kim | Atlas Migration | ACTIVE | 75% |
| Priya Nwosu | Northwind Rollout | PLANNED | 30% |
| Lena Richter | Mercury Support | BLOCKED | 55% |
server-side SQL · statement + lock timeouts on every transaction
The query problem
Downloading a dataset before filtering turns growth into a browser problem.
Client-side evaluation increases transfer size, exposes more data than the screen needs, and slows down as operational tables grow. Internal tools need a query path that keeps selection and ordering beside the database.
Query controls
Compile constrained requests into scoped SQL.
Relpin keeps query construction typed, tenant scope trusted, and operational limits applied inside the database transaction.
Server-side working sets
Filtering, sorting, limits, and offsets run in Postgres so the app receives the page it needs.
Transaction guardrails
Statement and lock timeouts are applied to the scoped transaction instead of relying on pooled session state.
Execution path
Define, scope, compile, execute.
The query path stays explicit from application intent to the returned working set.
- 01
Define the query
Application code supplies supported filters, sort fields, pagination, and selected data through the governed data API.
- 02
Resolve trusted scope
The runtime binds the request to the verified organization database and DEV, TEST, or PROD schema.
- 03
Execute in Postgres
Relpin compiles parameterized SQL, applies transaction limits, and returns only the requested rows.
Query evidence
Parameterized values
Schema-qualified identifiers
Server-side filter and sort
Transaction-scoped timeouts
Query questions
What the server-side SQL path does and does not expose.
Can application code execute arbitrary raw SQL?
No. Relpin compiles supported typed query operations into parameterized SQL. The page does not claim an unrestricted raw-SQL interface.
What happens when a query would evaluate in the browser?
The governed publish path can reject supported filter or sort plans that require client evaluation, keeping that fallback out of production releases.
Is server-side SQL the same as tenant isolation?
No. Tenant isolation selects the organization database and environment scope. Server-side SQL governs how a scoped application query is compiled and executed inside that boundary.
Query beside the data
Build operational screens that retrieve the working set, not the whole table.
Keep query intent typed, execution server-side, and tenant scope explicit.
Open beta · No SLA