Engineering Blog

How to Deploy Fast on Exovon

A practical guide from two real deployments.

We deployed two real projects on Exovon — one built in a hurry, one built with care — and measured everything. We are sharing this because we believe the best way to learn is to see what actually happens when code meets infrastructure. Whether you are just starting out or shipping your tenth app, we hope this helps you make informed choices about your stack, your plan, and your optimization strategy.

— Ayan Safik Khan, Exovon

The Two Apps We Tested

Both are real projects with real users. One was built quickly with lots of features. The other was optimized step by step. Both teach us something useful.

MinimanusDeadlyvoid
What it isA Manus-style AI agent cloneAn SSR + client-side game
Code approachFeature-first, optimize laterBuilt with performance in mind
Bundle sizeLarge (6MB+ JS)Moderate, code-split
ImagesPNG, served as-isWebP, lazy-loaded
DependenciesMany, some unusedMinimal, tree-shaken
Deploy regionMumbai (asia-south1) [Tested from Los Angeles]Mumbai (asia-south1) [Tested from Pune, India]
Exovon planStarter (₹349)Starter (₹349)

Both apps ran on the exact same Exovon Starter tier (₹349). Same pricing. Same container technology. The primary differences were bundle optimization and physical client distance to Mumbai. This demonstrates how much performance depends on application architecture alongside infrastructure.

Part 1: When the App Carries Extra Weight

What we learned from deploying a feature-heavy project across a long distance

Minimanus is a real, working product. It has AI agents, skill files, and a rich UI. It was built quickly to test ideas and ship features. Along the way, the bundle grew, images stayed in their original formats, and some dependencies were added but never removed. We also tested it from Los Angeles while it was hosted in our default Mumbai container pool — about 13,000 kilometers of transatlantic fiber away. Here is what we measured.

The Numbers

MetricResultWhat this tells us
Cold TTFB (26 min idle)1.506 s averageThe container is warm, but the round-trip is long.
Cold TTFB (worst)2.099 sNetwork variance across the Pacific adds up.
Warm TTFB (average)1.412 sConsistent, but still limited by distance.
Lighthouse Score (CLI)64 / 100Google flags this as needing improvement.
FCP4.20 sThe browser waits for a large JS bundle to parse.
LCP7.39 sA big hero image and heavy layout slow things down.
Speed Index5.90 sThe page fills in gradually rather than all at once.

These numbers are not a failure of Exovon. They are a reflection of what happens when a large bundle, unoptimized images, and a distant server all come together. We have seen similar results on other platforms with the same app. The good news: every one of these factors is within your control to improve.

If you are seeing numbers like this on your own project, do not worry. It is a common starting point. The next section shows what is possible with a few thoughtful changes.

Part 2: When Code and Geography Work Together

What thoughtful optimization and the right region can achieve

Deadlyvoid is a game. It has real-time interactions, database queries, server-side rendering, and client-side logic. But it was built with performance in mind from the start. The team used WebP for images, split the JavaScript bundle so only necessary code loads first, and removed dependencies that were not being used. It was deployed to our default serverless containers located in Mumbai (asia-south1), and tested in Pune, India — right where their players are. Here is what that looks like in practice.

The Numbers

MetricRun 1Run 2Run 3MeanGrade
Performance Score98989898Excellent
FCP1.5 s1.5 s1.5 s1.5 sFast
LCP2.5 s3.4 s2.0 s~2.6 sGood
Speed Index1.5 s2.7 s1.5 s~1.9 sFast
TBT70 ms120 ms80 ms~90 msGood
CLS0000Perfect

A 98 Lighthouse score. Sub-two-second First Contentful Paint. Zero layout shift. This is what Exovon delivers when your app is lean and deployed close to your users. It is not magic. It is the result of good habits applied consistently.

The same platform. The same container technology. The same pricing tier. The only things that changed were the code quality and the deployment region. That is empowering, because both are entirely in your hands.

Part 3: Three Lessons for Every Developer

Practical insights from running these two deployments side by side

Lesson 1: Small Code Changes Have Big Performance Impact

The difference between a 64 Lighthouse score and a 98 score is not the hosting platform. It is the bundle size, the image format, and whether you are loading only what the user needs. If your app feels slow, start here before looking at your host. Run next-bundle-analyzer. Check your image sizes. Lazy-load anything below the fold. These are free changes that often deliver the biggest speedups.

Lesson 2: Deploy Close to Your Users

Network distance matters. We hosted Minimanus in our default Mumbai (asia-south1) container pool, but we tested it from the USA. That is 13,000 kilometers of fiber, and the physical network routing adds unavoidable latency. Because all Exovon projects are currently deployed to Mumbai by default, users in South Asia will automatically experience blazing fast speeds.

FAQ: What if my primary user base is in the USA or Europe?

You can configure your origin compute region directly in your project dashboard (Settings > Regions). Select Iowa (us-central1) or Belgium (europe-west1) as your primary origin, or replicate your application across regions (1 region on Starter, up to 3 on Pro, and all 5 on Enterprise) so users get domestic execution latency.

Lesson 3: Choose the Right Plan for Your Stage

Exovon Free is perfect for learning, portfolios, and experiments. The container sleeps when idle, so you will see cold starts. When you are ready to scale, Starter (₹349) gives you 1GB RAM, 10GB origin bandwidth (with unmetered global edge CDN), and dedicated compute limits. The jump from Free to Starter is about capacity and performance for your users.

If you are ever unsure whether your app or the platform is the bottleneck, try this: deploy a simple hello-world page on the same plan and region. If that loads fast, the platform is fine and your app has room to optimize. It is a quick way to isolate the issue without guessing.

Part 4: A Practical Optimization Checklist

Five steps that will make almost any Exovon deployment faster

You do not need to do all of these at once. Pick one, measure the difference, then move to the next. Each of these changes will improve your performance on Exovon and on any other platform you might use in the future.

StepWhat to doWhy it helps
1. Audit your bundleRun next-bundle-analyzer. Look for large packages you are not using.A smaller bundle parses faster. FCP and LCP both improve.
2. Optimize imagesConvert PNG/JPEG to WebP. Use Next.js <Image> with priority on hero images. Lazy-load the rest.Images are usually the largest assets. WebP is 25-30% smaller than JPEG.
3. Use a CDN for static filesServe images, fonts, and CSS from Cloud CDN instead of your container.Your container handles dynamic requests. The CDN handles static files infinitely faster.
4. Cache database queriesUse Redis for frequently accessed data. Cache SSR pages with stale-while-revalidate.Fewer database round-trips mean lower TTFB and less backend strain.
5. Pick the right regionDeploy to the node closest to most of your users.Shorter network paths mean lower latency. It is the easiest speed boost available.

These habits are portable. Whether you stay on Exovon for years or move to another platform tomorrow, a lean bundle, optimized images, and smart caching will always serve you well. Think of them as foundational skills, not platform-specific tricks.

Part 5: Which Exovon Plan Is Right for You?

Honest guidance based on what we have seen from real deployments

PlanPriceBest forWhat to expect
Free₹0Learning, portfolios, experiments1GB origin bandwidth (unmetered edge CDN). 30 build mins/mo. Scale-to-zero microVMs.
Starter₹349MVPs, side projects, early SaaS10GB origin bandwidth (unmetered edge CDN). 1GB RAM. 150 build mins. Up to 5 custom domains.
Pro₹1,499Production SaaS, e-commerce, apps40GB origin bandwidth (unmetered edge CDN). 1GB RAM. 200 build mins. Unlimited custom domains & ExoStore DB support.
Heavy₹3,999100K+ users, high-traffic agencies1,000 GB (1 TB) origin bandwidth. 4GB+ dedicated RAM. 500 build mins. 500h compute. Dedicated fleet.

At Exovon, we are rapidly evolving and working to enhance your experience and your users' experience. We are building a platform focused on what actually matters for modern shipping: transparent pricing, powerful bundled databases, and honest performance metrics. Whether you are deploying autonomous AI agents, full-stack Next.js applications, or scalable serverless compute APIs on our global edge network, we believe developers deserve to see real numbers—not just synthetic benchmarks. If building on an AI-friendly platform that prioritizes clarity, fair pricing, and rapid deployment resonates with you, we would love to have you on board.

— Ayan Safik Khan

Founder, Exovon

August 2026

Methodology: All tests run on production Exovon infrastructure in August 2026. TTFB measured via curl. Lighthouse via Chrome DevTools (mobile) and headless CLI. Cold start = first request after 26-30 minutes idle. Warm = 5 consecutive requests. Apps are real production deployments, not synthetic benchmarks.