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

推荐订阅源

V
Visual Studio Blog
Recent Announcements
Recent Announcements
雷峰网
雷峰网
The GitHub Blog
The GitHub Blog
罗磊的独立博客
月光博客
月光博客
J
Java Code Geeks
A
About on SuperTechFans
Microsoft Security Blog
Microsoft Security Blog
D
Docker
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
F
Fortinet All Blogs
U
Unit 42
C
Check Point Blog
Martin Fowler
Martin Fowler
有赞技术团队
有赞技术团队
博客园 - 叶小钗
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
酷 壳 – CoolShell
酷 壳 – CoolShell
Blog — PlanetScale
Blog — PlanetScale
大猫的无限游戏
大猫的无限游戏
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
阮一峰的网络日志
阮一峰的网络日志
MyScale Blog
MyScale Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
We stopped sharing one staging server — here's what we bu...
Cristian Iri · 2026-05-04 · via DEV Community

Cristian Iridon

We stopped sharing one staging server — here's what we built instead

Every team I've been on has had the same problem.

You have 4 engineers. You have one staging server. Every morning there's a Slack message: "who's on staging right now?" Someone has to wait. Someone always merges before QA finishes. Someone's PR sits in review for 3 days because the environment is occupied.

The frontend teams solved this years ago. Vercel gives you a preview URL for every branch automatically. It's genuinely great — if your stack is Next.js.

But if you're running Django, Rails, Laravel, FastAPI, Spring Boot, or anything else that needs a real backend process? You're stuck with the shared staging server. Or you spend two weeks wiring up Kubernetes preview environments.

We got tired of it and built PreviewDrop.


How it works

PreviewDrop spins up an isolated Docker environment for every GitHub branch or pull request. Each environment gets its own URL. When the PR closes, the environment is automatically cleaned up.

Setup is one command:

npx previewdrop init

Enter fullscreen mode Exit fullscreen mode

That writes a GitHub Actions workflow file to your repo. After that, every PR gets a preview URL automatically — no manual steps, no shared state, no "who's on staging" Slack messages.


What it supports

If it runs in Docker, PreviewDrop can preview it. That includes:

  • Django (the one Vercel explicitly can't do)
  • Rails
  • Laravel
  • FastAPI
  • Spring Boot
  • Node/Express
  • Any custom Dockerfile

What it costs

$19/mo flat for the Starter plan — 5 concurrent previews, 3 team members. No per-second billing, no per-seat fees, no surprises at month end.

Compare that to Railway's pay-per-second model, which gets unpredictable fast when you're spinning up preview environments 20 times a day.


Who it's for

Three use cases where it genuinely solves a real problem:

1. Agency developers sending clients preview links
You're building a Django or Rails site for a client. They need to review the new feature. Right now you either keep a staging server running 24/7 (costs money, needs maintenance) or you send a Loom video. With PreviewDrop, you send a URL.

2. Small product teams with a QA bottleneck
One staging environment + multiple engineers = a queue. PreviewDrop gives every PR its own environment. QA can test 5 PRs in parallel.

3. Teams that evaluated Kubernetes-based solutions and gave up
Bunnyshell is powerful but the onboarding assumes you have a platform engineer with Kubernetes experience. PreviewDrop is Docker — if you can write a Dockerfile, you're done in under 10 minutes.


What we're not

To be clear: PreviewDrop is not production hosting. The environments are ephemeral. If you need Vercel-style CDN and ISR for a Next.js frontend, use Vercel — it's genuinely better for that use case.

PreviewDrop is for the backends that Vercel can't run.


Try it

We're in public beta. Free tier available, no credit card required.

previewdrop.dev

The GitHub App install takes about 90 seconds. If you have a Dockerfile, you'll have your first preview URL before your next coffee.


Feedback welcome — what's missing? What would make you actually switch?