Nicheloom visits: 58,050 all-time · 7,694 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

Render Workflows

Durable task orchestration without queues or workers

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hey HN, I'm Anurag, founder and CEO of Render, a cloud for application developers. We've just launched Render Workflows, a way to define durable tasks by decorating plain TypeScript or Python functions and running them on Render without operating queues, worker pools, retry logic, and state management. Code example below [1].The use cases we have in mind include agent loops, ETL/data pipelines, billing flows, and other long-running jobs. The model is simple: mark an existing function as a Task, deploy the repo as a Workflow, then trigger runs from your application code or via our API.Each task can run continuously for up to 24 hours and set its own retry policy, timeout, and compute instance type. Tasks can call other tasks like normal functions, and fan out in parallel with `Promise.all` or `asyncio.gather`. Each task run gets its own isolated container, and Render handles the queuing, orchestration, and observability.You can inspect logs, traces, and metrics for each run in the Render dashboard. If you're running other services on Render, you can connect to them from your tasks using built-in private networking. Billing is based on task instance type and run duration, prorated to the second.This is a public beta, so rough edges are possible. Today, task definitions are TypeScript and Python only, and built-in cron schedules aren't available yet. You can still trigger tasks from the SDK/API, or use a Render Cron Job for scheduled entry points. We're also working on pause/resume, checkpointing, vertical autoscaling, and support for more languages.We're not claiming this replaces every task orchestration system (yet). The goal is to make the common cases much simpler to use and troubleshoot, especially for Render users.Docs and examples: https://render.com/docs/workflowsI'd especially love feedback from folks who have built similar systems with Celery, BullMQ, Temporal, or other queues and workers. What would you want to see before GA?[1] ---- TS example ---- import { task } from '@renderinc/sdk/workflows' import { Render } from '@renderinc/sdk' const chargeCard = task( { name: 'chargeCard', retry: { maxRetries: 5, waitDurationMs: 1000, backoffScaling: 2 }, timeoutSeconds: 300, plan: 'standard', }, async function chargeCard(invoiceId: string) { // call Stripe or your payment provider here return { invoiceId, chargeId: `ch_${invoiceId}` } } ) const writeLedger = task( { name: 'writeLedger' }, async function writeLedger(invoiceId: string, chargeId: string) { // persist accounting entry } ) const sendReceipt = task( { name: 'sendReceipt' }, async function sendReceipt(invoiceId: string, chargeId: string) { // email customer } ) const processInvoice = task( { name: 'processInvoice' }, async function processInvoice(invoiceId: string) { const charge = await chargeCard(invoiceId) await Promise.all([ writeLedger(invoiceId, charge.chargeId), sendReceipt(invoiceId, charge.chargeId), ]) return { chargeId: charge.chargeId } } ) // from your app: const render = new Render() const startedRun = await render.workflows.startTask( 'billing/processInvoice', ['inv_123'] ) const finishedRun = await startedRun.get() console.log(finishedRun.results)

HN · launched Apr 9, 2026 · 7 upvotes (top 61%) · 0 views

Niche: backend development platforms and services · 94 launches, 6 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Workflow automation
  • Developer
  • Not AI
  • Commercial product

Visit website ↗ Source listing ↗

Could you build this?

No Building a durable execution engine requires complex distributed systems engineering, event sourcing, and cloud infrastructure guarantees.

What it would actually take: The architecture requires an event-sourced distributed state store (e.g., distributed Raft or CockroachDB), language SDK runtimes capable of deterministic execution replay and function suspension, and a fault-tolerant multi-tenant scheduler. The hardest engineering challenges are preventing split-brain states, handling arbitrary worker failures without state loss, and guaranteeing determinism. This requires senior distributed systems engineers and cloud infrastructure specialists.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one : 198 launches clear the similarity bar, closest 8 shown.

Attention rank: #129 of 199 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 159 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.