Replace Relay.app?
KINDA · weekend projectThe 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.
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.
$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR
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.
xpolished approvals, AI steps, integrations, shared workflows, and managed execution
xthousands of connectors
xmaintained OAuth applications
xschema-drift handling
xhigh-scale durable execution and support
What does the Relay.app verdict mean?
The core job looks buildable, with meaningful gaps: polished approvals, AI steps, integrations, shared workflows, and managed execution, thousands of connectors. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.
What price does this directory record show for Relay.app?
The directory records $19/month for Professional, checked 2026-07-31. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
What do I lose by replacing Relay.app?
Honestly: 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. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Relay.app?
The listed prior art includes Activepieces (Active open-source automation platform with connectors and durable workflow execution.). Inspect those projects before starting from a blank prompt.