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
37 Takip Edilen20.3K 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
7
36
51.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
0
0
1
98
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
146
15.4K
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
15
2.8K
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
66
25.4K
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
12
1.1K
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
738
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.3K
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.4K

Keşfet

@ojusave @itsclelia @llama_index @stripe @descope @autonomaai @chronark @OpenAI