[verdict][generated prompt][source: relay.app]
Can I vibecode Relay.app?
// buildable in a weekend, but real gaps stay open
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Relay.app, build a small human-in-the-loop workflow across two approved services. The hard boundary is polished approvals, ai steps, integrations, shared workflows, and managed execution, plus connector breadth and execution reliability.
confidence: medium
what it is: Build a small human-in-the-loop workflow across two approved services
Buildability index · an editorial game
- Price 19 $/month weight: plus 2
- Time closest consolation build: multi-day weight: minus 1
- Category automation no weight
- Moat integrations · infrastructure scale weight: minus 3
- Confidence medium weight: zero
- What you lose 5 items weight: minus 2
- Site relay.app (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Connect two approved services, execute a small durable human-in-the-loop workflow, expose retries and logs, and avoid claiming a general integration platform.
what you need
- OAuth or API credentials for two chosen services
- PostgreSQL
- Redis
- public HTTPS endpoint
- background worker
Editorial comparison targets the Professional plan and a two-service personal automation DIY substitute. Recheck price before merge.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build a personal replacement for Relay.app in an empty repository.
Use TypeScript, Node.js 22, PostgreSQL, Redis, BullMQ, and Docker Compose; do not offer alternative stacks.
The core loop is: connect two approved services, execute a small durable human-in-the-loop workflow, expose retries and logs, and avoid claiming a general integration platform.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement a fixed trigger, transform, condition, and action workflow model rather than a general visual language.
Connect exactly two named services using documented APIs and encrypted credentials.
Store every run, step input hash, output summary, retry, and final status in PostgreSQL.
Make side effects idempotent and support retry from the failed step without repeating completed actions.
Add rate limits, backoff, dead-letter handling, manual replay, cancellation, and secret rotation.
Ship Docker Compose, health checks, sample workflows, tests, backups, and connector-limit documentation.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a broad connector marketplace.
Deliberately leave out unreviewed user code execution.
Deliberately leave out enterprise governance, guaranteed execution, and vendor-operated OAuth apps.
Finish by running the tests and listing the exact commands used. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- polished approvals, AI steps, integrations, shared workflows, and managed execution
- thousands of connectors
- maintained OAuth applications
- schema-drift handling
- high-scale durable execution and support
Why people still pay
People still pay for Relay.app because one automation is easy; maintaining hundreds of connectors and making every run recoverable is the business. The recurring cost buys OAuth review, token refresh, webhooks, polling, schemas, retries, idempotency, queues, secrets, rate limits, observability, and upgrades, not just the visible interface.
moat: Integrations Infrastructure scale what a moat is
connector breadth and execution reliability
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Activepieces (opens in a new tab) — Active open-source automation platform with connectors and durable workflow execution.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.