--- title: Vercel now supports multi-service projects, Dockerfile... description: Vercel has launched three interconnected features for running multi-service backends: Vercel Services (collocate multiple services like a Python API, Express... canonical: https://daily.dev/posts/vercel-now-supports-multi-service-projects-dockerfile-deploys-and-internal-service-networking-rykzw5t77 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Vercel now supports multi-service projects, Dockerfile deploys, and internal service networking | daily.dev og:description: Vercel has launched three interconnected features for running multi-service backends: Vercel Services (collocate multiple services like a Python API, Express... og:url: https://daily.dev/posts/vercel-now-supports-multi-service-projects-dockerfile-deploys-and-internal-service-networking-rykzw5t77 og:image: https://api.daily.dev/og/posts/RYKZW5t77.png og:image:alt: Vercel now supports multi-service projects, Dockerfile deploys, and internal service networking og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Vercel now supports multi-service projects, Dockerfile deploys, and internal service networking **[Collections](https://daily.dev/sources/collections)** · 2 min read · 1 upvotes · 0 comments ## Summary Vercel has launched three interconnected features for running multi-service backends: Vercel Services (collocate multiple services like a Python API, Express server, and React SPA in one project with shared observability and rollbacks), Dockerfile support (deploy any HTTP server via a `Dockerfile.vercel` file with preview URLs, autoscaling, and CPU-based billing on Fluid compute), and Service Bindings (private internal networking between services via a single `vercel.json` declaration, with automatic TLS and auth, keeping traffic off the public internet). ## Content Vercel has shipped three related features that push it further into full-stack and backend territory: Dockerfile deployments, multi-service project support, and private networking between services. ## Dockerfile deployments You can now deploy any HTTP server to Vercel by adding a `Dockerfile.vercel` to your project. Vercel builds, stores, and runs the container on its Fluid compute platform. Rails, Django, Spring Boot, Go, Laravel — anything that listens on `$PORT` works. No container registry setup, no cluster management. The containers get the same treatment as Vercel frontends: preview deployments on every push, autoscaling in both directions, and built-in observability. Pricing is Active CPU — you pay for actual CPU usage, not idle time. A few constraints worth knowing upfront: containers run as serverless functions, so there are size, memory, and execution duration limits. They scale to zero after five minutes idle, are stateless by design, and durable storage isn't available yet. If you need a persistent process or local disk, this isn't the right fit. This puts Vercel in more direct competition with Render, Fly.io, and Railway. The pitch is consolidation — teams already using Vercel for frontend work can now run their backends in the same place. ## Multi-service projects Vercel now lets you collocate multiple services — say, a Python API, an Express server, and a React SPA — in a single Vercel project. All services deploy and roll back together, share the same observability dashboard, and run locally together with `vc dev`. ## Service bindings and internal networking Services within the same project can communicate over Vercel's internal network using Service Bindings. You declare a binding in `vercel.json` (one line), and Vercel injects an environment variable with an internal URL: ```js new URL("/api", process.env.BACKEND_INTERNAL_URL) ``` Requests over that URL never hit the public route table. TLS and authentication are handled automatically. It works for Node, Python, Dockerfile-based services, or any combination. Service-to-service calls show up in the observability dashboard and are billed as Service Requests and Fast Origin Transfer. Taken together, these features make Vercel a more viable option for teams running mixed frontend/backend stacks who'd rather not manage separate infrastructure for each piece. ## Similar posts on daily.dev - [Run a Dockerfile on Vercel](https://daily.dev/posts/run-a-dockerfile-on-vercel-hn3hhwkoh) · Flavio Copes · 1 upvotes · 0 comments --- Tags: [#docker](https://daily.dev/tags/docker), [#containers](https://daily.dev/tags/containers), [#microservices](https://daily.dev/tags/microservices), [#vercel](https://daily.dev/tags/vercel), [#service-mesh](https://daily.dev/tags/service-mesh) [View this post on daily.dev](https://daily.dev/posts/vercel-now-supports-multi-service-projects-dockerfile-deploys-and-internal-service-networking-rykzw5t77) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Vercel now supports multi-service projects, Dockerfile deploys, and internal service networking","url":"https://daily.dev/posts/vercel-now-supports-multi-service-projects-dockerfile-deploys-and-internal-service-networking-rykzw5t77","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/vercel-now-supports-multi-service-projects-dockerfile-deploys-and-internal-service-networking-rykzw5t77"},"datePublished":"2026-07-02T16:15:14.568Z","dateModified":"2026-07-06T09:00:15.262Z","description":"Vercel has launched three interconnected features for running multi-service backends: Vercel Services (collocate multiple services like a Python API, Express...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/vercel-now-supports-multi-service-projects-dockerfile-deploys-and-internal-service-networking-rykzw5t77","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"docker,containers,microservices,vercel,service-mesh","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Vercel now supports multi-service projects, Dockerfile deploys, and internal service networking"}]} ```