Pinned Tweet
Huge day for us at @render! We just announced a $100M raise at a $1.5B valuation.
As a DevRel, it's inspiring to see the investment we're already putting into our developers. And we're just getting started.
Check out the announcement below!
We’ve raised $100M at a $1.5B valuation.
We built Render to give developers an intuitive path to reliable and scalable cloud infrastructure.
Now, we are bringing that same philosophy to long-running, stateful infrastructure for AI apps & agents.
🧵
5
284
Render is now a supported connector in @FactoryAI.
Assign a task to a Droid and it can write the code, set up the services and database it needs, and deploy it to Render.
Connect Render in Factory to get started 👇
app.factory.ai/settings/conn…
4
5
22
1,225
If you're at @WeAreDevs in San Jose today, stop by the Render booth for cool swag and cooler conversations with our DX team about hosting your AI and agent workloads.
6
7
26
1,883
Render Workflows are incredibly for orchestrating agentic tasks. This is the new standard
Research agents split complex questions into multiple subtasks. But what happens when a branch fails?
Our latest open-source template uses @p0 's Search and Extract to research topics in parallel, fanning out subtasks on Render Workflows to provide isolation and retries.
The agent synthesizes successful results into a cited report.
Deploy with one click → render.com/templates/paralle…
21
Shifra Williams retweeted
Come say hi at the booth! The whole DX team will be there to talk shop and show you what we've been building. See you there.
Agent workloads are unpredictable by definition. Is the next request 3 tasks or 400?
Provisioning compute assumes you know the answer.
Our answer is Application-Defined Compute. Render CEO @anuraggoel explains it tomorrow at @WeAreDevs. 11 AM, Stage 1.
Find us at booth #734 after.
2
9
196
Can't wait for this!
Agent workloads are unpredictable by definition. Is the next request 3 tasks or 400?
Provisioning compute assumes you know the answer.
Our answer is Application-Defined Compute. Render CEO @anuraggoel explains it tomorrow at @WeAreDevs. 11 AM, Stage 1.
Find us at booth #734 after.
23
Introducing Build Reuse: Build once and reuse across multiple Render services and environments.
Save time. Save compute. Promote the build you actually verified to production.
Now in Private Beta. Learn more and request access: render.com/blog/build-reuse-…
9
7
32
1,830
Your next coding interface might just be iMessage.
Use this template to get your own Codex agent running in iMessage:
render.com/templates/photon-…
8
7
26
3,957
Shifra Williams retweeted
We spent years hearing: “Will Render scale?”
OpenAI builds on Render. Base44 scales on Render.
Meanwhile, weekly paid service creation looks like this.
I think we can retire the question.
24
18
186
200,845
Love how this video deconstructs a workflows failure and shows how Render handles it gracefully! That's how you demo like an engineer
At PR.ide, Blue demoed a RAG agent on Render that fact-checks its own answers, powered by Render Workflows. One task failed mid-demo. It retried automatically while every other task kept running like nothing happened.
That's the point: retries and fan-out, handled for you.
piped.video/watch?v=hzuV8cE4…
4
33
Shifra Williams retweeted
Donated as promised and requested an employer match to 2x the impact.
Get your card before they sell out! #RDC26
You can help provide life-saving services by funding The Trevor Project’s mission to end suicide among LGBTQ+ youth.
give.thetrevorproject.org/bo…
1
2
23
2,541
Shifra Williams retweeted
Your agent isn't failing because it can't reason. It's failing because it has too many tools and no clarity on which to use.
Arcade’s River Stevens and @render on why tool selection is a retrieval problem, plus a live demo of Arcade as a Claude plugin: piped.video/watch?v=kiUTMCtQ…
3
8
583
Give your agents a hammer, not a hardware store 🔨
River Stevens from @TryArcade spoke at PR.ide about why agents struggle with too many tools. Tool selection is a retrieval problem, not a reasoning one. Job-oriented tools and dynamic selection mean fewer tokens and higher recall.
piped.video/kiUTMCtQL_g
1
3
16
1,986
A GitHub token works for the demo. It breaks with multiple users.
Our PR summarizer template uses @scalekitinc for per-user auth. Each user connects their own GitHub, scoped per session.
Ship secure agents on Render →
render.com/deploy-template/a…
1
7
19
1,384
OpenAI uses Render to ship apps like gpt-oss playground and ChatKit Studio, supporting hundreds of thousands of concurrent users.
Recently, they used Render Workflows + Codex to launch a guide generation agent on the @OpenAIDevs site.
Here’s how: render.com/customers/openai
2
15
31
1,596
Shifra Williams retweeted
OpenAI used Codex to migrate its docs agent to Render Workflows in a single prompt.
@kagigz didn’t write a line of code.
“It told me how to run it, and that was it. It just worked.”
4
9
37
1,753
It's official: We're partnering with TanStack 🌴
We're building together to make it simple to ship applications that do more than serve pages: long-horizon agents, real-time collaboration, jobs that run for hours—anything you imagine.
Deploy: render.com/templates/tanstac…
🚨 New partner alert!
🚀 @Render and TanStack are joining forces to help you ship better, faster apps with zero ops. Whether that's your first user or your billionth, Render has everything you'll ever need to get to production.
Start building now 👇
tanstack.com/partners/render
8
6
42
3,135
Shifra Williams retweeted
Let sleeping CPUs lie. Unbilled.
@render Workflows charges for active CPU and memory, so your agent can wait on an LLM or tool call without paying for compute to keep it company.
2
5
28
1,350