Meter moves from lengthy AWS builds to one-click Vercel deploys
Meter, a full-stack networking provider, delivers internet access to businesses and schools of all sizes. Its platform spans two main application layers: Command, a generative UI for IT and networking teams, and Dashboard, the primary web interface. Both applications operate on top of Meter’s vertically integrated hardware and software stack, and Vercel has become the deployment layer that lets engineers iterate quickly across all of it.
The shift: from slow AWS builds to a unified pipeline
Before moving to Vercel, Meter’s Dashboard was hosted on a patchwork of AWS services. Builds clocked in at more than ten minutes, and engineers struggled with limited change visibility. The team wanted faster iteration, more efficient deployments, and tighter integration between frontend and backend work. Vercel checked those boxes.
The migration happened in two phases: core Dashboard components went first, then the remaining features were folded in. Meter’s engineers had to manage remote caching and consolidate repo structures along the way, relying on Vercel’s React and Vite build support, plus per-branch previews to keep the move smooth. Today all of Meter’s deployed assets sit in a single repository, which makes code management and team collaboration more straightforward. The build time dropped from over 10 minutes to under one minute.
Command: where Vercel and Next.js meet real-time data
Meter built Command—a tool that answers network questions in natural language and creates custom, real-time software—on Next.js and Vercel. The payoff is the ability to push daily production changes, review every feature branch in a production-like environment, and shrink reliance on manual QA.
Command’s backend handles substantial data processing that powers each interaction, while the Next.js frontend communicates via API Routes. That architecture keeps an explicit separation between client-side and server-side logic, while allowing the same sync and data exchange needed for a responsive interface. Vercel’s git-integrated workflow supports rapid iteration on the frontend without burdening engineers on the model side with infra details. The quick feedback loop also means the Command team can push changes, see updates immediately on the dev site, and refine the product continuously.
A faster path to production
Since the migration, Meter’s engineering team has seen measurable improvements in CI/CD speed and the flow of code reviews. Previewing every feature branch before it hits production has become a reliable process for maintaining quality, while the ability to push upgrades daily has accelerated feature releases across products. With the system living in a unified repo on Vercel, Meter’s team can focus on frontend logic and backend synchronization rather than deployment logistics, leaving more time to refine their full networking stack.
