ref()Store the input.
Use reactive state for values the user changes. Keep each state owner clear as the application grows.
Build with Vue’s reactive model. Ship a focused frontend, or choose a Nuxt runtime for the routes that need a server.
Explore Vue hostingVue + Vite / Vue Router / Nuxtconst concurrency = ref(3)workers.slice(0, concurrency)3 selected / 6 example workers
3 workers selected · 3 availableDerive values instead of maintaining duplicate state. Keep side effects intentional and network operations explicit.
ref()Use reactive state for values the user changes. Keep each state owner clear as the application grows.
computed()Use a computed value for data that follows from state. Filtered lists and totals should follow the same source.
watch()Use watchers for effects such as fetching data. Handle cancellation and errors when inputs change during a request.
Rendering decisions determine deployment requirements. Inspect the build output before choosing a target.
npm run build→ dist/Test a direct request to a nested route. Public frontend variables must contain no secrets.
Vue production deployment ↗rendering mode→ Nitro presetReview the Nitro target for server features. Container compute is billed separately from edge and build allowances.
Nuxt rendering modes ↗Free, Pro, and Team. Shared hosting allowances, GitHub + MCP deployment, and a global CDN. Choose the resources your project needs.
Start building. Put something real on the web.
No base plan charge
Free to start. No upfront plan charge.
Commercial projects welcome.
More room for production apps and a small team.
Save $336 · regular 48-month total $672
$336 paid upfront for 48 months.
Renews at $336 / 48 months.
Shared projects. More resources. Unlimited members.
Save $600 · regular 48-month total $1,200
$600 paid upfront for 48 months.
Renews at $600 / 48 months.
USD, before tax. Resource allowances reset monthly. Monthly equivalents are rounded for display; the upfront total is exact. Term discounts apply at every renewal. The 48-month term includes 24 free months.
Paid-plan usage budgets cover on-demand usage beyond included resources and add-ons; they exclude the base plan charge. Pro defaults to $50; Team to $100. Budget controls are not an instant hard-stop guarantee. Free has a $0 hard stop. These plans include edge and build allowances. Container compute and database services are metered separately.
| Your plan, in detail | Free | Pro | Team |
|---|---|---|---|
| Monthly equivalent | $0 | $7 | $12.50 |
| Upfront plan total | $0 | $336 | $600 |
| Renewal total | $0 / 48 months | $336 / 48 months | $600 / 48 months |
| Requests | 1M | 10M | 25M |
| Bandwidth | 100 GB | 1 TB | 2.5 TB |
| Edge CPU time | 10M ms | 100M ms | 250M ms |
| Build minutes | 100 | 500 | 1,250 |
| Team members | Solo | Up to 3 | Unlimited |
| Default usage budget | $0 · hard stop | $50 | $100 |
| Commercial use | Included | Included | Included |
| No per-seat charges | Included | Included | Included |
| AI website builder | Included | Included | Included |
| 5,000+ themes | Included | Included | Included |
| GitHub integration | Included | Included | Included |
| MCP integration | Included | Included | Included |
| Global CDN | Included | Included | Included |
| DDoS protection | Included | Included | Included |
VUE SPA OR NUXT SERVER
Deploy a Vue SPA or choose a compatible server target for Nuxt.
Pre-render public content for CDN delivery.
Keep personalized routes on a server-capable runtime.
Add backend services for forms and durable data.
RUNTIME CONFIGURATION
Keep production credentials behind the server boundary.
Keep private values out of public configuration.
Connect application services through private resource references.
export default defineNuxtConfig({
runtimeConfig: {
serviceApiKey: "",
public: {
apiBase: "/api"
}
}
});CONSISTENT RENDERING
Coordinate the first render, cached reads and persistent updates.
Use framework data fetching for SSR and hydration.
Scope cached reads by account and freshness.
Validate mutations and queue slower side effects.
Database and container resources are metered separately.
Choose a monthly workload and purchase term. See the included capacity, team seats and modeled delivery costs together.
Static delivery + builds. Commercial use. Zero server compute in this example.
Explore all plans ↗$336 paid upfront for 48 months. Same-term renewal: $336.
$3,014.40–$3,840 over 48 months, billed monthly. Constant usage and today’s rates.
USD before tax. Monthly requests are CDN asset requests, not unique people or page views; GB uses decimal units. Vercel is modeled with Flat Rate CDN enabled for an eligible web application and Basic 2-vCPU builds at $0.007 per minute. Build times are equal in the example, not a performance benchmark. Viewer seats are free on Vercel; the count above is deploying members.
The range reflects unclear credit eligibility for the fixed CDN tier: the lower estimate lets the $20 credit offset CDN plus builds; the upper applies it to builds only. Savings use the lower estimate. Actual invoices depend on configuration. This is a selected Flat Rate CDN configuration, not a claim that it is Vercel’s cheapest possible setup.
Excluded on both sides: server/edge execution, database and container compute, image processing, storage, model/API fees, add-ons and taxes. Let.com’s Edge CPU allowance cannot be equated directly to Vercel’s Fluid Compute CPU and memory billing. Workloads beyond Let.com inclusions are deliberately unpriced here. Multi-year totals assume constant usage and current prices; Vercel is billed monthly, not sold as a four-year commitment.
Rates reviewed October 20, 2026: Vercel Pro + seats · Flat Rate CDN · Basic build rates. Let.com rates come from the plans on this page.
Brand portfolio · planned deployments
Architecture examples for brands in our portfolio. These are planned deployments, not completed migrations or measured case studies.
Let.com is preparing web hosting, WordPress hosting and domains. A planned Let.com operations backend would track provisioning in managed PostgreSQL and process setup tasks through a queue, with Valkey for short-lived status.
Audit.com offers security assessments, readiness services and remediation engineering. The proposed Let.com workspace would use managed PostgreSQL for engagement tracking, queued report jobs and asset storage for project files.
Document.com
Document.com combines guided templates, document storage and e-signatures. A planned Let.com backend would keep workflow records in managed PostgreSQL and send document generation to a queue, with files in asset storage.
Framework decisions that change what you ship.
Yes. Confirm its Vite build command and output directory, then publish production assets. Test API requests and Vue Router behavior after deployment.
A typical static SPA does not need Node.js at request time. HTML5 history mode does need suitable host fallback rules for direct visits. Server rendering has separate runtime requirements.
No. This page models a reactive dependency using local browser state. The controls change a displayed selection only; they do not allocate compute or call an API.
Consider Nuxt when you want framework-managed routing, generated pages, request-time rendering, or server endpoints. Its rendering mode and runtime target determine the deployment.
Frontend bundle values are public. In Nuxt, review which runtime configuration is public and which stays server-side; do not return private configuration through page data or API responses.
Deploy your Vue frontend with the rendering model it needs.
Compare hosting plans