Compatibility
This page says which configurations Udria supports. It is versioned because the version in force when you buy forms part of your contract, and because a refund under our compatibility guarantee depends on what this page said on that day.
What “reference-tested” means here.
A row is marked reference-tested only when the package’s host contracts have passed conformance inside a real, independent repository, and only for the rows those runs actually prove. Two installs passing does not make every line below proven — a claim is promoted when a run proves it, not when a neighbouring claim is proven.
Rows marked not yet reference-tested are statements about how the package is built and tested, not about an installation into somebody else’s codebase. We would rather say that plainly than describe an untested configuration as proven.
Framework and router
| Configuration | Support | Note |
|---|---|---|
| Next.js 16.x App Router | Supported — reference-tested | Primary target.Tested against cal.com 6bc45298 and rallly 563742d5. |
| Next.js 15.5+ App Router | Supported — not yet reference-tested | Promoted only after a reference install passes host conformance. |
| Next.js Pages Router | ||
| Non-Next.js frameworks |
Database
| Configuration | Support | Note |
|---|---|---|
| Supabase Postgres | Supported — not yet reference-tested | First-class. |
| PostgreSQL (Neon, RDS, self-hosted) | Supported — reference-tested | Contract-supported.Tested against cal.com 6bc45298 and rallly 563742d5. |
| MySQL, MongoDB, other engines |
Connection mode
| Configuration | Support | Note |
|---|---|---|
| Direct PostgreSQL | Supported — not yet reference-tested | |
| Session-mode pooler | Supported — not yet reference-tested | |
| Transaction-mode pooler | Supported — not yet reference-tested | No session-scoped advisory lock is used (REQ-DB-001). |
| Supabase Data API only | Supported — not yet reference-tested | Through the shipped RPC/stored-function transaction adapter. |
| No atomic transaction mechanism |
Runtime and hosting
| Configuration | Support | Note |
|---|---|---|
| Vercel Node serverless | Supported — not yet reference-tested | |
| Long-running Node or Docker | Supported — not yet reference-tested | |
| AWS Lambda, Netlify, Render, Fly with Node and a durable scheduler | Supported — not yet reference-tested | |
| Cloudflare Workers or Edge-only | Stripe server and webhook paths require the Node runtime (REQ-RUN-002). |
Authentication
| Configuration | Support | Note |
|---|---|---|
| Any auth provider satisfying the identity and billing-authorisation contracts | Supported — reference-tested | Proven against two different auth systems (REQ-REF-002): NextAuth and better-auth.Tested against cal.com 6bc45298 and rallly 563742d5. |
What “not supported” means
The package ships a pre-flight check that runs against your repository before anything is installed. If your configuration is one we do not support, that check reports UNSUPPORTED and stops, rather than installing something that half works.
If this page listed your configuration as supported and the pre-flight check then reports it unsupported, that is the situation our compatibility refund covers. The conditions are in clause 9 of the terms.