Render

2K posts

Render banner
Render

Render

@render

The fastest path to production for full-stack applications and agents. Join the Discord: https://t.co/g5PgbKMFXt

San Francisco, CA Katılım Aralık 2020
36 Takip Edilen20.4K Takipçiler
Sabitlenmiş Tweet
Render
Render@render·
Building reliable apps and agents shouldn’t mean managing queues, workers, and retry infrastructure. With Render Workflows, you just push your code. Turn functions into durable, composable tasks → Trigger tasks from anywhere → Execution is automatic ↓ render.com/blog/durabilit…
English
2
9
39
56.6K
Render
Render@render·
At @joeybaker 's “Should agents be durable?” workshop for @AICouncilConf, we demoed a multi step LLM pipeline running on Render Workflows. The agent runs without pre-provisioned infrastructure, custom retry logic, or external state management. Explore the template: render.com/templates/self…
Haze Mestci@hazemestci

@joeybaker 's "Should agents be durable?" workshop at @AICouncilConf was packed. We demoed self-orchestrating agents that don’t require pre-provisioned infrastructure, custom retry logic, or separate configuration to manage state or recovery.

English
0
3
5
927
Render
Render@render·
Voice AI breaks when orchestration blocks the conversation. See how to use Render Workflows to run retries, parallel search, and synthesis in the background while keeping voice interactions real-time.
AssemblyAI@AssemblyAI

Ask a research question out loud. Under 60 seconds later, you have a complete, sourced answer. We built a reference architecture with @Render using AssemblyAI's Voice Agent API + Render's new Workflows. Core insight: keep the voice channel separate from background orchestration. Don't block audio waiting on tool execution. The stack: → @AssemblyAI Voice Agent API handles real-time audio streaming → @render Workflows classify, plan, search, synthesize as isolated tasks → @mastra agents classify question "shapes" before searching → @youdotcom powers parallel search branches Repo includes the Render Blueprint, Mastra configs, and a live demo. Full tutorial + source code: assemblyai.com/blog/voice-age…

English
2
1
9
1.3K
Render
Render@render·
Deploy headless Flue agents on Render in one click. Template ships with two example agents to get you started. To add a new one, drop a .ts file in .flue/agents/ and push. render.com/templates/flue
fks@FredKSchott

Introducing Flue — The First Agent Harness Framework Flue is a TypeScript framework for building the next generation of agents, designed around a built-in agent harness. Flue is like Claude Code, but 100% headless and programmable. There's no baked in assumption like requiring a human operator to function. No TUI. No GUI. Just TypeScript. But using Flue feels like using Claude Code. The agents you build act autonomously to solve problems and complete tasks. They require very little code to run. Most of the "logic" lives in Markdown: skills and context and AGENTS.md. Flue is like Astro or Next.js for agents (not surprising, given my background 🙃). It's not another AI SDK. It's a proper runtime-agnostic framework. Write once, build, and deploy your agents anywhere (Node.js, Cloudflare, GitHub Actions, GitLab CI/CD, etc). We originally built Flue to power AI workflows inside of the Astro GitHub repo. But then @_bgiori got his hands on it, and we realized that every agent needs a framework like Flue, not just us. Check it out! It's early, but I'm curious to hear what people think. Are agents ready for their library -> framework moment?

English
4
4
36
13.4K
Render
Render@render·
We're hosting PR.ide, a celebration of LGBTQ+ builders shipping in production 🌈 Join us for demos plus food, drinks, and real technical conversations on June 30th in SF. All are welcome. Come as you are, stay for the builds. RSVP → luma.com/8rw9j9t5
English
1
2
9
948
Render retweetledi
Jerry Liu
Jerry Liu@jerryjliu0·
Building a document processing pipeline at scale is hard, and is one of the reasons that it's hard to DIY your own document OCR solution by relying on LLM APIs. Your orchestration pipeline needs to handle rate-limit issues, handle parsing failure exceptions, handle retries due to timeouts without restarting the whole workflow. We're excited to collab with @render on this blog post. Get extremely high-quality, scalable document parsing APIs with LlamaParse, and make it even more scalable/resilient in a multi-step workflow through @render's infrastructure! Blog: render.com/blog/building-… Sample repo: github.com/render-example… LlamaParse: cloud.llamaindex.ai/?utm_source=xj…
Jerry Liu tweet media
LlamaIndex 🦙@llama_index

Building scalable, distributed document processing pipelines isn’t easy. That’s why we teamed up with @render to build a system that: 📝 Leverages the LlamaParse platform to parse, classify, extract, and retrieve information from documents ⚙️ Uses Render Workflows to distribute tasks across nodes and accelerate background processing ⚡ Deploys a lightweight server and database on Render, giving you an instant interface to interact with your pipeline 👩‍💻 Explore the repo to see it in action: github.com/render-example… 📚 And check out the step-by-step breakdown by @ojusave and @itsclelia: render.com/blog/building-…

English
5
16
150
15.9K
Render retweetledi
Anurag Goel
Anurag Goel@anuraggoel·
You TOO can build resilient, long-running pipelines without contorting your app to fit your workflow vendor's arcana.
LlamaIndex 🦙@llama_index

Building scalable, distributed document processing pipelines isn’t easy. That’s why we teamed up with @render to build a system that: 📝 Leverages the LlamaParse platform to parse, classify, extract, and retrieve information from documents ⚙️ Uses Render Workflows to distribute tasks across nodes and accelerate background processing ⚡ Deploys a lightweight server and database on Render, giving you an instant interface to interact with your pipeline 👩‍💻 Explore the repo to see it in action: github.com/render-example… 📚 And check out the step-by-step breakdown by @ojusave and @itsclelia: render.com/blog/building-…

English
0
3
16
2.9K
Render retweetledi
LlamaIndex 🦙
LlamaIndex 🦙@llama_index·
Building scalable, distributed document processing pipelines isn’t easy. That’s why we teamed up with @render to build a system that: 📝 Leverages the LlamaParse platform to parse, classify, extract, and retrieve information from documents ⚙️ Uses Render Workflows to distribute tasks across nodes and accelerate background processing ⚡ Deploys a lightweight server and database on Render, giving you an instant interface to interact with your pipeline 👩‍💻 Explore the repo to see it in action: github.com/render-example… 📚 And check out the step-by-step breakdown by @ojusave and @itsclelia: render.com/blog/building-…
GIF
English
6
14
68
26.6K
Render
Render@render·
Document processing pipelines are a pain to scale. Here's how to build one with @llama_index and Render Workflows. LlamaParse handles parsing, classification, extraction, and retrieval. Workflows distributes the background work. Try it: …der-workflows-llamaindex.onrender.com Full walkthrough from @ojusave and @itsclelia 👇
LlamaIndex 🦙@llama_index

Building scalable, distributed document processing pipelines isn’t easy. That’s why we teamed up with @render to build a system that: 📝 Leverages the LlamaParse platform to parse, classify, extract, and retrieve information from documents ⚙️ Uses Render Workflows to distribute tasks across nodes and accelerate background processing ⚡ Deploys a lightweight server and database on Render, giving you an instant interface to interact with your pipeline 👩‍💻 Explore the repo to see it in action: github.com/render-example… 📚 And check out the step-by-step breakdown by @ojusave and @itsclelia: render.com/blog/building-…

English
0
4
13
1.2K
Render
Render@render·
Shipping an MCP server without auth is like leaving your front door open and hoping for the best. Learn how to deploy a secure, scalable MCP server with @descope auth and no IAM headaches → render.com/blog/enterpris…
Render tweet media
English
0
1
10
792
Render
Render@render·
Did you know Render can create a temporary instance of your service for every pull request, automatically? Service Previews spin up a standalone instance with its own URL, copying settings from your base service. When the deploy succeeds, it fires a deployment_status event you can hook into for automated testing with tools like @autonomaai. Here's a walkthrough : getautonoma.com/blog/render-au…
English
3
1
10
1.4K
Render
Render@render·
On our new workspace plans, 75% of paying customers will see their Render bill decrease or stay the same. More information on the changes we're making and how to opt in↓ render.com/blog/better-pr…
English
0
0
5
1.6K
Render
Render@render·
No changes to compute pricing. The changes we are making are exclusive to our workspace plans. Render compute pricing is staying the same. You can keep running your services on the same compute plans with predictable, usage-based billing.
English
1
0
6
1.8K
Render
Render@render·
We're removing seat fees from our pricing. Our new Pro plan is $25/mo, flat. Add your entire team at no additional cost. We've structured our new plans from the ground up to make pricing fairer and more scalable for teams shipping faster with AI. What we're changing 🧵
English
15
8
209
69.6K

Keşfet

@joeybaker @AICouncilConf @ojusave @itsclelia @llama_index @stripe @descope @autonomaai