惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
博客园 - 司徒正美
博客园_首页
Jina AI
Jina AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
月光博客
月光博客
I
InfoQ
M
MIT News - Artificial intelligence
T
Tailwind CSS Blog
L
LangChain Blog
Last Week in AI
Last Week in AI
A
About on SuperTechFans
B
Blog
博客园 - 叶小钗
雷峰网
雷峰网
H
Help Net Security
WordPress大学
WordPress大学
大猫的无限游戏
大猫的无限游戏
博客园 - 【当耐特】
云风的 BLOG
云风的 BLOG
Microsoft Azure Blog
Microsoft Azure Blog
小众软件
小众软件
aimingoo的专栏
aimingoo的专栏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻

Railway Blog

Where Railway is, and where it's going (Summer 2026) PaaS vs IaaS vs SaaS: What Each Means and Who Should Pick What in 2026 The Best Continuous Deployment Tools in 2026 The Best PaaS for Multi-Region Deployments in 2026 The Best Platforms for Monorepo Deployments in 2026 Compliance Isn't a Feature, It's a Posture What is BYOC (Bring Your Own Cloud)? A Developer's Guide for 2026 The Best Managed Kubernetes Hosting in 2026 The Best Container Registries in 2026 The Vanilla Cloud Tax: What Rolling Your Own on AWS Actually Costs What is a PaaS? A Developer's Guide for 2026 The Best Cloud Observability and Logging Tools in 2026 The Best PostgreSQL Hosting for Developers in 2026 The Best Multi-Region Hosting Platforms in 2026 The Best Platforms to Deploy AI Apps in 2026 (Not the Models, the Apps Around Them) Incident Report: May 19, 2026- GCP Account Suspension Counting to 3 with a new builder processing 50M+ monthly builds Railway iOS preview now available via TestFlight Kill your onboarding: selling to 10,000+ new users a day Your AI wants to nuke your database. Guardrails fix that. Better Rails for Agents: A New Remote MCP and Railway Agent in the CLI Moving Railway's Frontend Off Next.js One command deploys, there's a Stripe APP for that From registrar to deployed: buying a domain inside Railway A letter to open source builders who deserve more Networking is a black box, we used eBPF to open it Heroku Walked So Railway Can Run Security Features Your Security Team Will Love Railway Runs Open Source, Now We're Funding It Railway raises $100M Series B to unburden the builders
How Bilt's Marketing Engineering Team Delivers at Scale w...
Angelo Saraceno · 2025-12-07 · via Railway Blog

Bilt, the nationwide loyalty program for renters, faced a familiar challenge: how to move fast without sacrificing engineering velocity. When their marketing team restructured around dedicated engineering pods, they needed infrastructure that could keep pace with their rapid deployment cycles and high-traffic events.

Railway's developer-first platform enabled the marketing engineering team to focus on what matters most: shipping features that serve millions of customers across the country.

The Challenge: Speed vs. Infrastructure Complexity

Bilt's marketing engineering team operates unlike traditional marketing teams, running full engineering operations with backend engineers, frontend engineers, and full-stack developers building everything from QR code scanning systems for events to an entire booking platform for experiences.

"On the marketing team we move fast. We need our tech stack to allow for that in a scalable, safe way."

— Kartik Aggarwal, Tech Lead at Bilt

Bilt wanted to avoid a common pattern seen across the industry: a web hosting platform for frontend deployments and a hyperscaler cloud platform for backend infrastructure. The pain points they would’ve encounter with this approach were clear:

  • Manual deployment processes
  • Complex infrastructure management
  • Time drain, with too much time spent managing Terraform
  • Lengthy onboarding for new engineers to learn cloud patterns

When shopping for a platform provider, Bilt was looking for simplicity.

"Most of the knobs to tweak aren't relevant to a feature-oriented team. I don't need to configure 20 different knobs just to get my feature shipped."

Traditional Cloud vs Railway: Development in Just Hours

When Bilt evaluated infrastructure platforms, they tested three different solutions with a simple benchmark: how quickly could they deploy their new backend and get a testable URL?

“What takes an hour on Railway could take 10x more on a traditional cloud platform.  Railway was the fastest, giving us the most seamless, no config system. We just connected our monorepo project and then Railpack automatically identified our Node.js projects.”

The productivity transformation was immediate:

  • Time to deploy from what would have been a week on a different cloud provider to an hour
  • 95% of engineering time spent on feature development
  • Zero-config deployments resulted in no manual infra configuration

Scaling to Millions of Requests per Second Seamlessly

Bilt operates at significant scale during high-traffic bursts, like the first of the month when most customers pay rent and unique benefits are offered. Their Railway-hosted experiences platform handles this scale:

  • 1,500+ requests per second during peak traffic
  • Sub-50 millisecond response times under full load
  • 32 cores and 32GB RAM per container with cost-effective resource allocation

The generous resource allocation particularly impressed the team as they did not have to request additional resources or go through a lengthy approval processes.

"It was pretty mind-blowing when we saw that we have 32 cores and 32 GBs of RAM per container. The resources per container are really cheap, and there are a lot of them."

50% Cost Reduction from Traditional Cloud to Railway

With Railway’s pay-per-use model, the large containers handle bursty traffic but don’t require Bilt to pay for the resources when idle.

This resulted in direct cost efficiency when comparing Railway to a traditional cloud provider:

  • ~50% lower infrastructure costs than expected
  • $200 monthly bill for one service handling millions of requests

The team continues to launch backend projects on Railway, with engineers freed from infrastructure concerns to focus on actually writing code.

Bilt’s Appreciation of Railway’s Support

Bilt has benefited from Railway’s incredibly responsive support team.

"Something that has really helped build trust from the Bilt side is the Slack channel that we have with your team and how responsive Railway has been, iterating even on smaller feedback. That direct communication has been really integral for us."

The success has created a template for other engineering teams at Bilt who could unlock developer velocity benefits like the marketing engineering team did with Railway.

The Bottom Line

For engineering managers evaluating infrastructure platforms, Bilt's Railway adoption delivered measurable results.

Railway enabled Bilt's marketing engineering team to operate efficiently at scale—moving fast, shipping frequently, and focusing on customer impact rather than infrastructure complexity.

The platform's developer-first approach doesn't just reduce operational overhead; it fundamentally changes how engineering teams think about and interact with infrastructure, creating a competitive advantage in markets where both velocity and security matter.