Which hosting platform would you pick for a small production app: Render vs Railway vs Cloudflare Workers?

I’m building something like a inventory management app and website — authenticated users, a Node/TypeScript API, PostgreSQL, background jobs/cron, and potentially a few thousand users over time.

Currently considering **Render, Railway, and Cloudflare Workers**.

For a production app where reliability, scaling, DB latency, and predictable costs matter, which one would you choose and why?

Would you recommend something else like **Fly.io, AWS, or Vercel + another backend** instead?

Curious to hear from people who’ve actually run production workloads on these.

I'm looking for a workable solution or recommendations to provide a client's credentials to that client in the event of my untimely demise or absence. (E.g. hit by a bus - falling out and need to hand everything over, etc.) I also don't want to mix MY credentials with theirs.

So my primary work isn't webdev, but I do some for clients as part of my general services. Generally this means me building everything from scratch and leaving the client(s) out of the day-to-day management entirely.

I'm trying to figure out the best way to have their business' credentials saved, updated as they are changed, and set aside for if I get "hit by a bus" so they won't be locked out of everything.

I also don't want them "futzing" with things (because some of these clients have impulse control issues and would 100% give their credentials to someone on Fiver to update a paragraph on their website at 2am when I don't answer my phone.) So access while I'm not dead or fired isn't a real option.

I understand that I can make "organizations" in some of the password managers and have emergency hand-over to pre-selected people, but I work alone, and don't "have a lawyer" that can manage it for me.

A feature common to a great very many HTML boilerplates is this line:

html <meta name="viewport" content="width=device-width, initial-scale=1.0">

The initial-scale=1.0 bit was present to fix an ancient issue on iPhones. When rotating the screen into a landscape orientation, the page would keep the same width as when it was in portrait, making everything appear very zoomed in.

This isn't an issue any more. I've tested it across very many devices, and it appears it was fixed in iOS 9, which released back in 2015. In addition to testing, I've consulted a great number of other professionals, and nobody has been able to find evidence of it being needed any longer.

You can safely simplify the meta viewport declaration down to:

html <meta name="viewport" content="width=device-width">

It isn't hurting you to leave it there, but it is vestigial and unnecessary.

Further details: - https://vale.rocks/micros/20260902-1350 - https://quirksmode.org/quirksblog/2026/0902-initial.html

Hi can anyone help me with finding this theme?

Does anyone know how to add completely secure video calls to a website? I’m struggling to find the best way.

Additionally, how do I then host this for free / as low cost as possible.

If anyone has advice that would be great!

I think this is a pretty common thing, but it's my first time doing it so I'm a bit lost. Basically I need to make a booking or an appointment. For that I need a customer to attach it too, so when the user first wants to create an appointment, they have to select a customer first, but if the customer doesn't exist, I want them to create a customer. I'm confused as to what should be on what page, should my 'create appointment' button go to select/create customer, which can the go to 'create customer' and back to 'create appointment', it seems clunky? I'm making this app for computer illiterate people so I want to the process to be smooth.

Please, any advice would be very much appreciated.
Thanks

I’m a full-stack developer with nearly six years of experience

Since the start of the year, I’ve integrated AI tooling heavily across my day job (Claude Code) and freelance work (Gemini Antigravity). The trade off is clear, I write significantly less code, but I ship significantly more. Taking time off recently gave me the space to reflect and I have realised how I barely write code manually anymore and I’m torn about where the profession is headed.

On one hand, this feels like natural career evolution, hands on syntax matters less as the job shifts toward high level architecture, systems design, and code reviews. On the other hand, the shift leaves me alienated from the craft that drew me into engineering in the first place. 

I want to hear from engineers with at least a few years of professional experience:

1. How do you feel about the transition from writing code to orchestrating AI output?
2. Do you still write code manually on purpose? If so, what justifies it?
3. Have we crossed the point of no return on writing the vast majority of our codebase by hand?

I am considering building a family website for my family. My mother's extended family built one, but it's something nobody really ever visits. I'm considering building a wiki-style site (locked behind user accounts) to have a page for each family member, each nuclear family, and then they can build upon it and create pages for vacations and things like that. I would then have a mini social feed for us each to share pages we've created. For example, my sister might say "Just made a page for our Disney Land 2026 trip! Here's the link."

Might be overscoped, but I thought it'd be a fun way to start capturing family stories.

If you've built a family site for your family (or someone else's) what did it have? What purpose did it serve and what features were built into it?

It used be be that CSS resets were important to smooth over differences between default browser styling, but browsers have for the most part gotten their act together.

It's more popular nowadays to do a micro reset/normalize/whatever you want to call it to get rid of annoyances. It might contain rules such as * { all: unset }, or * { margin: 0; padding: 0 }, or input, button, textarea, select { font: inherit }, or commonly * { box-sizing: border-box }.

I see the appeal. But at the same time, I find a major downside to all of this that never seems to be discussed - code portability. I write a component in one UI project and want to copy it to another project or to a shared component library, and it's not so simple because the other project(s) may be using slightly different CSS resets.

It's not like it's easy to update projects to use the same resets either, it's so engrained in how everything else was built up in the project.

But there's also a natural desire to revisit what reset you're using whenever you're building a new project, as opinions change, problems are found in existing ones, etc.

Or, on the flip side, maybe I'm wanting to use a third party tool, then find out that my global CSS rules cause issues with their styling.

We try hard to avoid any kind of global pollution in JavaScript, but make it a best practice to do just that in CSS.

So, I try to avoid these kinds of resets. I don't even do the "box-sizing: border-box" thing, it turns out that this box sizing issue doesn't come up very often (for me at least), and when it does, I just add the rule to the specific places that need it. I'll still set a default font to everything, but that's about it.

But, when I look around online, it seems that most everyone still uses some kind of reset. Guess I'm curious if I'm abnormal in my stance here or if there's others out there who also avoid them. Also curious if those who do use resets have ran into problems like the ones I've described above.

I’m part of a community and saw a need that I could fill and have been working on an idea for it for awhile, so I mapped out an infrastructure for a website and started directing Vercel on the build, connecting GitHub as well as Resend. I used Cloudflare for the domain. So far it’s used Next.js, React, TypeScript, PostgreSQL, Drizzle ORM, Better Auth, and Tailwind CSS all deployed on Vercel.

That was until I switched to building on Hermes with an Ollama sub because Vercel cost me an astronomical amount for just the homepage.

I’m learning bits and pieces as I go but I feel like the code is probably a giant mess even though everything looks really beautiful on the consumer side and navigates great.

I have my checkout/subscriptions connected to Stripe.

Ideally I will get this off the ground and have it sustain itself, pull in some revenue, and then bring it all to a developer and say “Help, please?” Unless going through 32,000 lines of code (and counting) and 287 files is doable for someone with exactly this much experience in web development.

Are there people who offer services to go over builds like this and refine them or am I going to get laughed off the face of the earth?

Let’s share hidden gem tools, not the usual stuff that shows up in every "top developer tools" post, but smaller tools and projects that made you think, "wait, this is actually really useful."

I'll start with 3 I've come across:

1. Archify
https://github.com/tt-a1i/archify

Found this recently. It's an agent skill that works with Claude Code, Cursor and Codex and basically turns a codebase into an interactive architecture map.

You can export it as HTML/PNG/SVG/WebM, and one thing I thought was pretty cool is that you can diff the architecture before a merge to see how a PR changes the system.

2. boneyard-js
https://boneyard.vercel.app

Generates skeleton screens from your actual UI instead of making you manually recreate the layout with placeholder components.

Pretty nice alternative to manually maintaining react-loading-skeleton stuff.

3. Gradient Studio
https://gradientsaas.blogspot.com

Simple procedural CSS gradient generator.

Has stuff like mesh gradients, aurora effects and grain. You mess with the settings and copy the result as CSS, Tailwind or SCSS.

I've been using it mostly for quick landing page backgrounds.

What's one tool you keep recommending that somehow still isn't very well known?

Guys does anyone know how to fix this? It randomly stopped working yesterday and keeps showing this whenever I try to start it again from services.msc. Please help.

As the title suggests I've been on the lookout for a CMS which allows for defining editable areas in existing pages like CouchCMS, but which is flat-file. Suggestions are appreciated.

I am doing a react native project, where i genrated some UI picture mockup in chat GPT and based on that I genrated some sample pure HTML again chatgpt and later the whole syatem was developed using sonnet where the system was audited by fable 5. For UI i have used some skill in claud which helped to make things cleaner.

Now back the UI for me does not feel AI to me but i can be wrong. How can I make sure before going live?

Things i am still considering

Font

Make things clean material design

Less animation

Littile to no shadows

Appreciate any input

No AI is used while i write THIS post

I need to test my website live. I'm hosting on Vercel but I don't want any users stumbling upon it by accident before the testing is complete. How do I prevent this?

I added a few locations in Developer Tools so that I can change my location for some sites. Is there a way to export/import these locations, or add them programmatically with a script? Or are they stored in a file somewhere that I can just replace? It gets a little tedious having to add them back in every time when setting up a new VM. I suppose I could always set up a baseline VM with them added, but curious to see what other options I may have.

Hello! I'd like some creative ideas for websites/apps. I want to go beyond the e-commerce scope and make something more creative designing/coding wise.

Beginner here, I have been learning to code for a few months now and decided to build a website with css, html and js. While it is quite easy to get started, once you try to get a little bit more low level, it seems really hard. In my example I want images to zoom in or out in a specific way and just don't know how to approach that problem, since most things in css have a pretty high level of abstraction. This is coming from someone who played around a little with graphic-librarys (SFML3) to make silly games, where you have to make most of the things from scratch. I enjoyed that, since I barely had to look up anything once I understood all the low-level stuff, which gave me a loot of freedom (and headaches, admittedly). My question now is: Is there is a way of creating websites on a lower level, is the problem I described common among other devs, or do I just need to shut up and learn the basics?

I know hes trying to monetize us better and ship aggressively in order to minimize the acquisition debt of twitter but like bro current X pay-per-use rates: $0.005 per post read, $0.010 per user read, $0.001 per owned-resource read, $0.015 per post created, and a whole fuckass $0.20 per post containing a link. he already has the blue checkmark subscription as well as x money now.

So i tested on my mcp app and 29 post reads × $0.005 = $0.145, plus one $0.010 made my balance go from $5.00 to $4.84.

While some third party providers are 35x less of the cost but they are often shady and sit in a gray zone due to scraping, plus they cant write posts only x official api could from what i've seen.

Jeez at least lower it to 0.0025 or something because that is so not friendly towards margins, I'm assuming they're trying to capitalize off of per user data too like how reddit and other social platforms do since it brings them a ton more money.