Render on X

Fan posts are short and mostly recommendations rather than stories: people call it the best product in the market, say it is "for anything serious", and tell others to try it. The reason they give most is uptime — 7 people say they have run projects for months or years with no incident, one since 2022 and one for two years, and one contrasts their projects sitting safely on Render while a competitor had a security incident.

4 praise the deploy itself: git push and it runs, "no infra, no networking, no stress", months without thinking about deploys. Several mention Render as an option mid-thread while a competitor was down; reach on individual posts is modest, a handful of likes.

The doubt is money. 2 rate the platform but say pricing stops them using it more, one unwilling to pay $25 a month once credits run out. 2 are undecided, asking for concrete reasons or for real user feedback before they move.

The most-named failure is the site: a GitHub connect popup that kept reopening the dashboard in a loop, free services that hang when someone sets up a dev environment, a site down and unable to sign in, registration emails that never arrive, and one post mocking the mobile page.

Slowness is the next cluster. The free instance sleeps and the first request pays for it, free hours run out, and one developer's backend on Render feels slow next to a frontend on Vercel.

Billing trouble is about cards that will not debit, charges people did not expect with cancellation blocked until they pay, and one user who paid but still cannot reach their services. On price, one poster puts Render's bandwidth at three times a competitor's.

Trust runs through the 3 people who doubt it. The widest-read post in the section, seen far beyond the others, says the CEO mocking a competitor's outage changed their mind; another asks how anyone can trust it will not happen here.

Most of the Railway talk is people arriving. One migrated in ten minutes and deleted the project, another ported 14 projects, others post "Bye bye Railway" and ask how the pricing compares. Not everyone moves: one would rather wait than migrate, one notes databases and Redis make it trickier, and one could not migrate at all because Railway was down.

Price cuts both ways. One poster says bandwidth is three times dearer on Render but would not give Railway another dollar; another argues the benefits outweigh the extra cost.

The VPS camp is small but argumentative: why not a VPS with Coolify, answered with it being harder to scale and "Who will protect it?", and one declaring they are done with PaaS. Vercel is named for frontends, Cloudflare Pages as fast and free but needing a rewrite for Workers, Fly.io for a side-by-side trial, and one picks PlanetScale over Render Postgres.

Pricing questions are about how the bill is built. Someone with twelve deployments on a flat competitor plan asks whether Render charges per deployment; another asks the cost per domain, because they sell self-hosted websites; others ask about outbound traffic and how the total compares with what they pay now.

The other big question is why switch at all — for specific reasons, and for a realistic run through pros and cons. One asks what Render is missing, and another asks why use Render rather than just Google.

Two people simply ask whether Render is down. Two more ask about secrets: whether environment variables are safe, and whether teams can scope cloud credentials separately for preview and production services.

One wants a $5-a-month plan with volumes, no sleeping and multiple projects, saying they will not pay $25 once free credits run out. Another wants usage-based pricing at least per environment, having paid for dev workers until they moved dev onto their own home server.

The other three are single asks. One wants servers in Sydney so the app and its database sit in the same region, saying latency is becoming an issue and they do not want to look for an alternative. One asks where the AI bot is that would diagnose deploy errors. One wants a CI/CD walkthrough with an example that waits for the deployment result and then runs a smoke test, drawing a line between a deploy request being accepted and the new version serving the critical path.