What DoorDash actually does
DoorDash is the dominant on-demand food and grocery delivery platform in the US, founded in 2013 by Tony Xu, Stanley Tang, Andy Fang, and Evan Moore. By Q1 2026 it had surpassed 56M MAUs and processed 933M orders in a single quarter (+27% YoY), generating $4.03B in revenue (+33% YoY including Deliveroo). Its $31.6B Marketplace GOV in Q1 2026 makes it the largest third-party delivery operator in North America.
DoorDash's business model is a three-tier merchant commission structure: 15% Basic, 25% Plus, and 30% Premier. The Premier tier means a restaurant doing $50K/month in delivery orders loses $15,000 per month to platform fees alone. On top of commissions, consumers pay $1.99–$7.99 delivery fees plus a service fee of approximately 15% of the subtotal. DashPass at $9.99/mo removes delivery fees for subscribers, and DoorDash has over 35M paid members across DashPass, Wolt+, and Deliveroo Plus as of end-2025.
DoorDash's October 2025 acquisition of Deliveroo for £2.9B extended its reach into the UK, France, Italy, and UAE. The company also acquired SevenRooms for $1.2B in June 2025, signaling a push into reservations. With a market cap of $66.28B as of May 2026, DoorDash is the clear category leader — but its 30% commission rates and a $16.75M NY AG settlement in February 2025 over tip misappropriation have made it a frequent target of merchant and regulatory scrutiny.
Three-sided marketplace (consumers, merchants, Dashers)
DoorDash connects consumers to 700K+ merchants and dispatches orders to a fleet of independent Dasher couriers in real time, managing all three relationships through a single platform.
Real-time order dispatch and GPS tracking
Orders are routed to Dashers using batch matching algorithms derived from the Hungarian algorithm, with live GPS tracking visible to consumers and merchants.
DashPass subscription program
DashPass at $9.99/mo or $96/yr provides $0 delivery fees on $12+ orders from eligible merchants, driving consumer loyalty and repeat order frequency.
Merchant POS integration
DoorDash integrates with Toast, Square, NCR, and other POS systems to inject orders directly into restaurant workflows, reducing manual entry errors.
DoorDash Storefront (commission-free)
Storefront allows restaurants to accept online orders through their own website with zero commission, charging only payment processing fees — DoorDash's direct concession to commission pressure.
Stripe Connect split payments and 1099 reporting
Payments are split in real time between the platform, merchant, and Dasher, with automated 1099-NEC tax reporting for independent contractors.
DoorDashpricing & limits
Based on a restaurant doing $50K/month in delivery orders on the Premier 30% tier
Where DoorDash falls short
30% Premier commission crushes independent restaurant margins
The Premier tier's 30% commission has been cited in multiple state legislative hearings as unsustainable for independent restaurants. New York City enacted a 15% cap on basic delivery commissions, and several other cities followed. A restaurant with $600K/year in DoorDash orders on Premier loses $180K/year to the platform before accounting for consumer-facing fees.
$16.75M NY AG settlement for tip misappropriation
In February 2025, NY AG Letitia James confirmed DoorDash used customer tips to offset the base pay it had already guaranteed to Dashers rather than supplementing driver income. The $16.75M settlement covered restitution to affected workers and exposed a systemic deception that lasted years.
Driver deactivations without notice or explanation
NYC Intro 1332, introduced September 12, 2025, specifically addresses courier deactivation without cause. Councilmember Brannan noted: 'there needs to be a clear — if I broke the rules, you need to tell me what the rules were before I broke them.' Dashers with 4+ year records reported account closures with no appeal pathway.
New service fees added in regulated cities passed to consumers
After Seattle enacted a deactivation law in July 2025, DoorDash added new service fees citing 'extreme regulations,' directly passing regulatory compliance costs to consumers rather than absorbing them. This pattern of fee pass-through has become a recurring response to municipal regulation.
Order accuracy and refund friction at scale
Wrong-item and missing-item complaints are a structural issue at DoorDash's volume of 933M quarterly orders. The refund process requires consumers to navigate multiple support flows, and merchants face automatic refund chargebacks that erode already-thin delivery margins.
Key features to replicate
The core feature set any DoorDash alternative needs — plus what you can improve on.
Real-time order dispatch and driver matching
DoorDash uses batch matching (Hungarian algorithm variant) to assign multiple orders to a single Dasher when routes overlap, maximizing driver efficiency. Replicating this requires a real-time dispatch engine using Redis for order queuing, a geospatial index (PostGIS or Redis GEOINDEX), and a background worker (Temporal or BullMQ) for assignment logic. A custom build can implement simpler nearest-driver matching for an MVP without the full batching optimization.
Consumer, merchant, and driver apps with live GPS tracking
Three distinct app surfaces — consumer ordering, merchant order management, and driver navigation — each with real-time GPS state. Recommended stack: React Native for mobile apps sharing a common API layer, WebSocket or Ably/Pusher for live location pushes to consumers. The merchant tablet app can be a Next.js web app rather than native to reduce scope.
Dynamic delivery fee and surge pricing engine
Delivery fees vary by distance, demand density, and time of day using ML-based demand prediction. For an MVP, a rule-based surge multiplier (e.g., 1.5x after 6pm or when driver supply falls below threshold) is buildable in 2–3 weeks and captures 80% of the business value without ML infrastructure.
Subscription program (DashPass-style)
DashPass at $9.99/mo delivers zero delivery fees and reduced service fees for eligible orders. Custom build via Stripe Billing with a subscription product and webhook-based order eligibility check. The key engineering challenge is real-time eligibility verification at checkout without adding latency.
Merchant POS integration
DoorDash integrates with Toast, Square, and NCR to inject orders directly into restaurant kitchen displays. Custom builds can use Toast's API or Square's Orders API for initial integrations; NCR requires enterprise partnership. Plan for 4–6 weeks of integration work per POS vendor and ongoing maintenance as APIs change.
Stripe Connect split payments with 1099 reporting
Platform takes its cut, the merchant receives net revenue, and the Dasher receives their delivery payment — all in one transaction. Stripe Connect Custom or Express accounts handle splits natively. 1099-NEC reporting is handled via Stripe's tax forms feature for US contractors, saving significant compliance engineering.
SNAP/EBT payment compliance
DoorDash added SNAP/EBT support for grocery deliveries. This requires a certified EBT processor (Fiserv, Worldnet, or Forage), USDA retailer authorization, and split payment logic to separate SNAP-eligible items from non-eligible items. This adds 4–8 weeks of compliance work and is only necessary if targeting grocery delivery.
Restaurant discovery and search
Consumer-facing marketplace search by cuisine, dietary filter, rating, distance, and estimated delivery time. Requires ElasticSearch or Typesense for full-text + faceted search, PostGIS for radius queries, and a ranking algorithm. For an MVP, Postgres full-text search with PostGIS handles basic discovery adequately before investing in dedicated search infrastructure.
Technical architecture
A DoorDash alternative is a three-sided on-demand marketplace requiring real-time dispatch, live GPS tracking, split payment processing, and POS integrations operating simultaneously across consumer, merchant, and driver surfaces. The dispatch layer is the core technical challenge — it must match drivers to orders within seconds while accounting for batching efficiency, driver proximity, and ETA accuracy.
Frontend (3 surfaces)
React Native (consumer + driver apps), Next.js App Router (merchant web dashboard), React Native Web (shared components)
Recommended: React Native for mobile apps — code-sharing between iOS and Android reduces scope. Next.js for the merchant dashboard provides SSR and a faster development cycle than building native.
API / Backend
Node.js + Express, Go microservices, Next.js Route Handlers
Recommended: Node.js monolith for MVP — split into Go microservices for dispatch and order routing once load demands it. Premature microservices add ops complexity without benefit at early stage.
Real-time dispatch layer
WebSocket (native), Ably, Pusher, Socket.io
Recommended: Ably or Pusher for MVP — managed WebSocket infrastructure handles scaling and reconnection logic out of the box. Self-hosted Socket.io is viable but requires careful ops at scale.
Database
PostgreSQL + PostGIS, MySQL, MongoDB
Recommended: PostgreSQL with PostGIS extension — native geospatial queries for driver radius searches and delivery zone polygon matching. Redis as caching layer for order state and driver location updates.
Payments
Stripe Connect Custom, Stripe Connect Express, Braintree Marketplace
Recommended: Stripe Connect Custom accounts for full control over driver and merchant payout timing. Stripe handles 1099 generation for US contractors, significantly reducing compliance overhead.
Mapping and routing
Google Maps Platform, Mapbox, HERE Maps
Recommended: Google Maps for consumer-facing ETAs (best consumer brand recognition) and Mapbox for driver navigation (lower cost at volume). Budget $2K–$5K/month for maps APIs at moderate order volume.
Queue and background jobs
Temporal, BullMQ + Redis, AWS SQS
Recommended: BullMQ + Redis for MVP dispatch queuing and order state machines — simpler ops than Temporal while handling the throughput needed at early scale. Migrate to Temporal as stateful workflow complexity grows.
Complexity estimate
Complexity 10/10 — three-sided real-time marketplace with dispatch algorithms, live GPS, split payments, POS integrations, and regulatory compliance across multiple jurisdictions. Plan for 6–10 months with a team of 4 experienced engineers.
DoorDash vs building your own
Open-source DoorDash alternatives
Existing projects you can self-host or use as a starting point. Each has trade-offs.
Medusa
30K+Medusa is a modular, headless commerce platform built in TypeScript with MIT license. While not a delivery marketplace out-of-the-box, its plugin architecture and fulfillment module provide a solid foundation for a restaurant-direct ordering system. Stack: Node.js + PostgreSQL + Redis.
TastyIgniter
3.5KTastyIgniter is a PHP/Laravel-based restaurant online ordering and reservation platform. It handles single-merchant ordering workflows, menu management, and delivery zones natively. v4.2.1 released January 31, 2026.
Bagisto
26.8KBagisto is a Laravel/PHP e-commerce framework with multi-vendor marketplace capabilities. It provides a product catalog, order management, and multi-vendor seller management that can be adapted for restaurant-as-merchant patterns.
Build vs buy: the real math
6–10 months
Custom build time
$250,000–$600,000 (agency)
One-time investment
14–20 months
Breakeven vs DoorDash
At DoorDash's Premier 30% commission, a restaurant doing $50K/month in delivery orders pays $180,000/year in platform fees. A custom build at $400,000 (mid-range agency cost) plus $5,000/month in infrastructure breaks even in approximately 26 months at that volume — marginal. The math improves dramatically at higher volumes: at $100K/month in orders, $360K/year in saved commissions pushes breakeven to around 14 months. The strongest case for building is not to replace DoorDash entirely but to build a restaurant-direct ordering system (Storefront equivalent) that bypasses the marketplace commission entirely. DoorDash itself offers Storefront at 0% commission — the build case is when you want to own the consumer relationship and data, add a loyalty program, or serve a niche vertical (medical delivery, B2B catering, alcohol) where DoorDash's generic marketplace is a poor fit. Do not build a generic DoorDash clone expecting to compete on network effects — supply and demand density is the moat, not the software.
DIY roadmap: build it yourself
This roadmap covers a restaurant-direct ordering and delivery platform for a single city or vertical, with a team of 3–4 engineers. A generic multi-restaurant marketplace adds significant scope — see the caveat below.
Core ordering infrastructure
6–8 weeks- Bootstrap Next.js App Router project with Supabase auth (email + phone OTP)
- Build merchant dashboard: menu management, hours, delivery zones with PostGIS polygons
- Build consumer ordering UI: restaurant discovery, cart, checkout flow
- Integrate Stripe Connect for split payments between platform, merchant, and driver
- Implement order state machine (placed → accepted → dispatched → delivered → complete)
Real-time dispatch and tracking
6–8 weeks- Build driver app in React Native with GPS location broadcasting via Ably
- Implement nearest-driver matching with Redis GEOINDEX for O(log N) radius queries
- Add order acceptance/rejection flow for drivers with 30-second auto-reassignment timeout
- Build live order tracking UI for consumers using Ably subscriptions
- Integrate Google Maps Directions API for ETA calculation and route display
Payments, subscriptions, and compliance
4–6 weeks- Implement DashPass-style subscription via Stripe Billing with order eligibility webhooks
- Build driver payout scheduling (daily or weekly) via Stripe Connect payouts API
- Add dynamic delivery fee engine: base fee + per-mile rate + demand multiplier
- Implement Twilio SMS notifications for order status updates to consumers
- Build 1099-NEC reporting export for driver tax compliance using Stripe Tax Forms
Merchant tools and POS integration
4–6 weeks- Build real-time merchant order tablet UI with audio alerts via WebSocket
- Integrate Toast POS API for direct order injection into kitchen display
- Add Square Orders API integration as secondary POS option
- Build merchant analytics dashboard: order volume, average basket, driver ratings
- Implement merchant menu sync for automatic availability updates
Operations, monitoring, and launch
3–4 weeks- Set up Datadog APM for order pipeline latency monitoring and dispatch SLA alerting
- Implement automated refund workflow for order accuracy complaints via Stripe refunds API
- Build driver deactivation and appeal workflow with admin review queue
- Conduct load test of dispatch layer at 50 concurrent orders with k6
- Launch with 10–15 pilot restaurants and 5–10 seed drivers in target geography
These estimates assume 3–4 experienced engineers and a focused single-city deployment. Building a national multi-restaurant marketplace adds 6–12 months and requires dedicated ML/data engineering for dispatch optimization. Mobile apps (iOS + Android) add 40–60% to frontend scope if built natively; React Native mitigates this significantly.
Features you can't get from DoorDash
This is where a custom build pulls ahead — features impossible or impractical on a shared platform.
Zero-commission restaurant-direct ordering
Unlike DoorDash which takes 15–30% even on Storefront orders for payment processing, a custom build lets you charge only Stripe's 2.9% + 30¢ per transaction with no platform commission. A restaurant doing $50K/month saves $12,550–$14,550 per month versus Premier or Plus tier. This is the single highest-ROI customization and the core reason to build.
Loyalty program tied to order history
DoorDash controls consumer loyalty data and owns DashPass — restaurants cannot build independent loyalty on top of it. A custom platform can implement points accumulation, tiered rewards, and birthday offers tied directly to restaurant-branded consumer accounts, creating retention that compounds over time.
B2B corporate catering and batch ordering
DoorDash's consumer-focused UX is a poor fit for corporate catering: large orders, scheduled delivery windows, cost-center billing codes, and invoiced payment. A custom platform can implement bulk ordering workflows, purchase order integration, and net-30 invoicing that DoorDash cannot offer without Enterprise contracts.
Hyper-vertical delivery (medical, alcohol, specialty)
Medical supply delivery requires HIPAA-compliant order handling and temperature logging. Alcohol delivery requires age verification (ID scan via SDK like Persona) and state-by-state compliance. DoorDash supports these categories generically; a custom platform can optimize the entire workflow for a single vertical, including regulatory reporting.
Driver income transparency and predictable earnings
One of the most-cited Dasher complaints is earnings unpredictability. A custom platform can implement guaranteed minimum earnings per hour, transparent batch pay breakdowns, and driver income dashboards showing YTD earnings and projected quarterly 1099 amounts — directly addressing the trust gap DoorDash's $16.75M settlement exposed.
White-label platform for restaurant groups
Multi-location restaurant chains pay DoorDash commission on every order across all locations. A custom white-label platform lets a 50-location chain internalize delivery, manage their own driver fleet, and capture consumer data across all locations — a $1M+ annual commission saving for chains doing significant delivery volume.
Who should build a custom DoorDash
Independent restaurant operators paying 25–30% commission
A restaurant doing $30K–$50K/month in DoorDash orders at Premier tier pays $90K–$180K/year in commissions. A custom restaurant-direct ordering system at $250K–$400K build cost breaks even in 22–27 months and eliminates commission permanently, including for all future order volume growth.
Multi-location restaurant chains
A 20-location chain with $100K/month aggregate delivery volume loses $360K+/year to DoorDash commissions. Building a white-label platform captures consumer data across all locations, enables cross-location loyalty programs, and breaks even in under 14 months at that volume.
Hyper-local delivery operators in a specific city or vertical
DoorDash's generalist marketplace is a poor fit for medical supply delivery, corporate catering, alcohol delivery, or farm-to-table CSA. Verticals with specific compliance requirements (HIPAA, ABC licensing, age verification) benefit from a custom platform that bakes compliance into the workflow rather than bolting it on.
Ghost kitchen operators
Ghost kitchens running multiple virtual brands under one roof pay DoorDash commission across every brand independently. A custom platform lets the operator manage all brands from a single merchant interface, set differential delivery zones, and avoid paying marketplace commission on orders that come through their own owned channels.
Skip the DIY — let RapidDev build it
Everything above is doable — but it takes months of full-time work. We build custom DoorDash alternatives using AI-accelerated development, delivering in weeks what used to take quarters.
Discovery call (free)
30 minWe map your exact requirements: which DoorDash features you need, what custom features to add, your users, integrations, and compliance needs. You get a detailed scope document and fixed-price quote within 48 hours.
AI-accelerated build
6–10 monthsOur engineers use Claude Code, Lovable, and custom AI tooling to build 3–5x faster than traditional development. You see progress in a staging environment every week — not a black box for months.
Launch + handoff
1 weekWe deploy to your infrastructure, transfer the GitHub repo, set up CI/CD, and walk your team through the codebase. You own 100% of the source code — no vendor lock-in, no recurring platform fees.
What you get
Timeline
6–10 months
Investment
$250,000–$600,000 (agency)
vs DoorDash
ROI in 14–20 months
30-min call. Fixed-price quote within 48 hours. No commitment.
Frequently asked questions
How much does it cost to build a DoorDash alternative?
Building a three-sided food delivery marketplace costs $250,000–$600,000 with an agency, depending on scope. A focused restaurant-direct ordering system (no marketplace, single merchant) costs $60,000–$120,000. The biggest cost drivers are the real-time dispatch engine, mobile apps (iOS + Android), and POS integrations.
How long does it take to build a DoorDash clone?
6–10 months with a team of 4 engineers for a full three-sided marketplace. A restaurant-direct ordering system (bypassing the marketplace entirely) takes 3–5 months. The dispatch and driver tracking layer alone accounts for 6–8 weeks of that timeline.
Are there open-source DoorDash alternatives?
There are open-source commerce foundations but no production-ready DoorDash clone. TastyIgniter (3.5K GitHub stars, MIT) handles restaurant ordering for single merchants. Medusa (30K+ stars, MIT) provides a modular commerce backbone. Bagisto (26.8K stars, MIT) supports multi-vendor marketplaces. None include real-time dispatch or driver tracking out of the box.
What is DoorDash's commission structure in 2026?
DoorDash charges 15% (Basic), 25% (Plus), or 30% (Premier) commission on every order. Consumer fees add delivery ($1.99–$7.99) plus a ~15% service fee on the subtotal. DashPass at $9.99/mo removes delivery fees for subscribers. NYC caps basic commissions at 15% but Premier-tier ancillary fees still apply.
Do I need WebSocket infrastructure for a delivery app?
Yes — live order tracking, driver location updates, and real-time order acceptance all require persistent connections. Managed services like Ably or Pusher handle WebSocket infrastructure reliably for MVPs. At scale (10K+ concurrent connections), a self-hosted WebSocket gateway becomes more cost-effective.
Can I use Stripe Connect to split payments between restaurants and drivers?
Yes — Stripe Connect Custom accounts support multi-party payment splits, instant driver payouts, and 1099-NEC tax form generation for US contractors. This is the recommended payment architecture for any on-demand delivery build. Expect 4–6 weeks to properly implement onboarding, KYC, and payout scheduling.
Can RapidDev build a custom DoorDash alternative?
Yes — RapidDev has built 600+ apps including on-demand marketplace and delivery platforms. We can scope your specific use case (restaurant-direct ordering, hyper-vertical delivery, white-label platform) and provide a fixed-scope proposal. Start at rapidevelopers.com/contact.
Is it worth competing with DoorDash directly?
No — DoorDash's network effects (56M+ MAUs, 700K+ merchants, dense driver supply) make head-on competition prohibitive. The viable plays are: (1) restaurant-direct ordering that bypasses the marketplace entirely, (2) a hyper-local brand in a single city with density DoorDash lacks, or (3) a vertical with regulatory requirements DoorDash handles poorly.
We'll build your DoorDash
- Delivered in 6–10 months
- You own 100% of the code
- No per-seat fees, ever
30-min call. No commitment.