Let.com Web App Hosting

Your code.
Production infrastructure.

Deploy from GitHub. Configure your runtime. Deliver through a global CDN. One platform for your frontend, server routes and application services.

$0 to start · commercial projects welcome

workspace / application Deployment example
RELEASE HISTORY
GitBuildDeploy
Configure API routesa7e93c1 · main → productionBuild output ready. Environment attached. HTTPS connected.
DEPLOYMENT OUTPUTrelease / a7e93c1
GitHubSource
BUILDLet.comassets + runtime
◈Global CDNstatic assets
λEdge requestsserver handlers
▣Containerfull services
↳ /assets/index.js STATIC↳ /api/projects SERVER↳ application.example HTTPS

Runtime compatibility varies. Container compute is separately metered.

BUILD LOG · EXAMPLEReady
✓ npm ci --ignore-scripts✓ npm run build✓ Package assets + server output✓ Release ready for review
Explore releases · illustrative configuration
GOOD IDEAS DESERVE A START

A plan for your next release.

Start with a commercial-friendly Free plan. Add capacity and teammates as your application grows. No per-seat fees.

50% off · every renewal, too
Your first big idea

Free

Start building. Put something real on the web.

$0/ month

No base plan charge

Free to start. No upfront plan charge.
Commercial projects welcome.

Start building free
Requests
1M
Bandwidth
100 GB
Edge CPU time
10M ms
Build minutes
100
Team members
Solo
Default usage budget
$0 · hard stop
  • AI website builder included
  • 5,000+ themes to start from
  • Commercial use allowed
  • No per-seat charges
  • GitHub + MCP deployment
  • Global CDN + DDoS protection
Make room for everyone

Team

Shared projects. More resources. Unlimited members.

$12.50/ month$25

Save $600 · regular 48-month total $1,200

$600 paid upfront for 48 months.
Renews at $600 / 48 months.

Choose Team
Requests
25M
Bandwidth
2.5 TB
Edge CPU time
250M ms
Build minutes
1,250
Team members
Unlimited
Default usage budget
$100
  • AI website builder included
  • 5,000+ themes to start from
  • Commercial use allowed
  • No per-seat charges
  • GitHub + MCP deployment
  • Global CDN + DDoS protection

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.

Compare every plan inclusion
App hosting plans · included resources
Your plan, in detailFreeProTeam
Monthly equivalent$0$7$12.50
Upfront plan total$0$336$600
Renewal total$0 / 48 months$336 / 48 months$600 / 48 months
Requests1M10M25M
Bandwidth100 GB1 TB2.5 TB
Edge CPU time10M ms100M ms250M ms
Build minutes1005001,250
Team membersSoloUp to 3Unlimited
Default usage budget$0 · hard stop$50$100
Commercial useIncludedIncludedIncluded
No per-seat chargesIncludedIncludedIncluded
AI website builderIncludedIncludedIncluded
5,000+ themesIncludedIncludedIncluded
GitHub integrationIncludedIncludedIncluded
MCP integrationIncludedIncludedIncluded
Global CDNIncludedIncludedIncluded
DDoS protectionIncludedIncludedIncluded

GitHub deployments

Your repository.
Your release pipeline.

Keep source control at the center. Your framework tells the build what to produce; the hosting environment supplies the settings it needs to run.

  1. Connect the projectSelect your GitHub repository and the source branch for deployment.
  2. Review the buildCheck the project root, install command, build script, and output against your framework.
  3. Attach the environmentAdd private values as server secrets. Review the release, then connect your domain.
Working from an AI editor? See the MCP workflow ↗
Import a projectConfiguration example
Repositoryworkspace / frontend
Build commandnpm run build
Outputdist/ · static assets
EnvironmentPublic configuration only
Review before release

A Vite frontend builds to static files. Private API keys belong in a backend, never in the browser bundle.

One platform. Different workloads.

Match the runtime.
Know what you’re paying for.

A frontend, a request handler and a long-running service do different work. Choose a deployment around the code you actually have.

01 / DELIVER

Static assets

HTML, styles, images and browser JavaScript. Use the global CDN to serve the public files your build produces.

  • Vite frontends and generated content sites
  • Custom domains and HTTPS
  • Requests and bandwidth use plan allowances
02 / RESPOND

Edge requests

Application logic at request time. Validate your framework adapter and runtime APIs before deploying server features.

  • Request handlers and compatible server routes
  • Private server-side configuration
  • Edge CPU time uses plan allowances
03 / RUN

Container services

A full application process for workloads that need it. A Node.js server may need a container rather than an edge handler.

  • Review ports, start scripts and dependencies
  • Managed Postgres available separately
  • Container and database compute billed separately

After the first deployment

Ship the next change
with a way back.

A release is more than a successful build. Inspect the result, verify the routes customers use, and keep an earlier application version within reach.

01

Find the failing step

Inspect build and deployment failures before changing production settings. A missing dependency and a bad environment value need different fixes.

02

Review application changes

Keep commits small enough to understand. Test authentication, forms, deep links and third-party calls against the deployed version.

03

Separate code from data recovery

Application rollback restores code. A database migration or deleted upload needs its own backup and recovery plan.

Get specific

What are you deploying?

Next.js

Server-rendered pages & route handlers

View deployment details ↗
React

Interactive frontends & client routing

View deployment details ↗
Node.js

APIs & container services

View deployment details ↗
Vue

Reactive interfaces & Nuxt decisions

View deployment details ↗
Astro

Content sites & selective interactivity

View deployment details ↗
Svelte

Forms, SvelteKit & adapters

View deployment details ↗

THE WHOLE APPLICATION

Frontend to database.
One connected project.

Your frontend, backend and data, connected in one Let.com project.

INPUTBrowser
APPLICATIONFrontend / API
DATA & SERVICESPostgres + Valkey

Deliver

Deliver cacheable assets through the global CDN.

Execute

Run API handlers or a full container service.

Persist

Add managed Postgres, Valkey and persistent storage.

Databases and containers are metered separately.

Technical details

A working product needs somewhere to deliver its interface, execute private logic and keep customer data. Bring those pieces together in a Let.com project, with a resource choice for each job. Your public website and your private database should have very different network boundaries.

Deliver

Publish the files your frontend builds through the CDN. Keep versioned assets cacheable, compress large images and avoid making a database request for content that could be generated ahead of time.

Execute

Run compatible request handlers for application logic, or deploy a container image for a full server process. Connect services with server configuration, and choose CPU and memory around the workload you measure.

Persist

Add managed Postgres for relational records, Redis-compatible Valkey for cache and session workloads, or a persistent volume for a service that needs durable files. Database and container resources are metered separately.

Architecture example · public delivery, private application data

Managed PostgreSQL

DATA THAT OUTLIVES A RELEASE

A database is part of the product.

Private Postgres connections. Daily backups. Data that survives your next release.

Pooled application traffic

Pooled connections for everyday application queries.

Direct administration

Direct connections for migrations and administration.

Recovery choices

Daily backups, with optional HA and point-in-time recovery.

HA and point-in-time recovery depend on your database plan.

Technical details

An account, an order and a permission are durable records. Managed Postgres gives them a private home with daily backups. Connect through references rather than copying a database password into source code or a support conversation.

Pooled application traffic

Use the pooled connection for ordinary application queries. Keep transactions short, bound connection counts and add indexes for the queries your customers actually run. More application instances should not mean unlimited database connections.

Direct administration

Use the direct connection for migrations and features that need a session connection, such as LISTEN/NOTIFY. Ship schema changes deliberately; deploying earlier application code does not undo a destructive migration.

Recovery choices

Check backup status and retention before launch. Optional high availability and point-in-time recovery depend on the database plan. A standby helps availability; a backup supports recovery. They solve different problems.

SECURITY + SPEED

Make the fast path
the sensible path.

Keep private data protected and heavy work off the request path.

  1. Keep the boundary private

    Sealed server secrets. Authorization in your application.

  2. Move slow work off the page

    Queue slow jobs with retries and dead-letter handling.

  3. Measure before adding capacity

    Measure CPU, queries and memory before scaling.

Technical details

Good hosting foundations work best with explicit application rules. HTTPS and delivery protection help traffic reach your app; the app still decides which user may read a record, change a setting or start expensive work.

Keep the boundary private

Store credentials as sealed server secrets. Return only the fields a client needs, redact sensitive values from logs and check authorization on every protected operation, including requests made outside your interface.

Move slow work off the page

Use a queue for emails, imports or report generation. Durable jobs can retry with backoff and reach a dead-letter state for inspection. Make the consumer idempotent so a retry cannot duplicate a payment or send.

Measure before adding capacity

Distinguish asset transfer, request CPU, database wait and container memory. Improve the bottleneck you can observe, then review allowances and separately metered services together. One account does not mean one unlimited resource pool.

Let.com × VERCEL / COST MODEL

Four builders. One application budget.

Choose a monthly workload and purchase term. See the included capacity, team seats and modeled delivery costs together.

4 deploying members10M requests / month1 TB transfer / month500 build minutes / month

Static delivery + builds. Commercial use. Zero server compute in this example.

Explore all plans ↗
Let.com Team$12.50/mo

$600 paid upfront for 48 months. Same-term renewal: $600.

Deploying members
No seat charge
Delivery + builds shown
Within plan limits
Vercel Pro · modeled$83.50–$100/mo

$4,008–$4,800 over 48 months, billed monthly. Constant usage and today’s rates.

Deploying seats
$80/mo
Flat Rate CDN tier
$20/mo
Basic builds, before credit
$3.50/mo
Monthly usage credit
Up to −$20
$3,408 less over 48 monthsCompared with the lower Vercel estimate, for only the services modeled above.
How this comparison works + sources

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

Different businesses.
One flexible foundation.

Architecture examples for brands in our portfolio. These are planned deployments, not completed migrations or measured case studies.

Property search, ready for the next listing.

Realty.com brings home listings, saved searches and agent discovery together. The proposed Let.com stack pairs a search API with managed PostgreSQL, Valkey caching and queued listing updates.

  • Backend
  • PostgreSQL
  • Valkey
  • Queue
Explore app hosting
Message.com

Every conversation, one connected inbox.

Message.com brings chat, email and phone conversations into one team workspace. A proposed Let.com deployment would pair conversation records in managed PostgreSQL with Valkey for transient state and queued channel events.

  • Backend
  • PostgreSQL
  • Valkey
  • Queue
Explore backend hosting
Audit.com

Keep assessment work moving.

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.

  • Backend
  • PostgreSQL
  • Queue
  • Assets
Explore app hosting

Before you deploy

Hosting questions.
Practical answers.

Is Web App Hosting the same as shared web hosting?

No. These plans are for applications deployed from source code, with build and runtime configuration. Traditional cPanel web hosting is a separate product. Choose based on whether you are deploying an application repository or managing a conventional website hosting account.

What happens when my Free plan reaches its allowance?

Free includes 1M requests, 100 GB bandwidth, 10M ms of Edge CPU and 100 build minutes per month. Its $0 hard stop prevents paid usage; reaching limits can interrupt service. Upgrade or wait for the allowance reset.

Can I host the backend for a phone app?

You can deploy a compatible web API used by a mobile app. Hosting does not compile or distribute native iOS and Android applications; those still use the relevant platform build and app-store processes.

Does a deployment include my database?

Your application connects to its database through server configuration. Managed Postgres and container compute are separately metered services. Database migrations, backups and persistent uploads require their own plan.

Is every team member charged separately?

No. Pro includes up to three members for a $14 monthly base price. Team includes unlimited members for a $25 monthly base price. Resource usage remains subject to plan allowances and any applicable additional charges.

Do the multi-year savings disappear at renewal?

No. These are term discounts, not first-purchase offers. Renewing for 48 months keeps the 50% term discount. A different renewal term uses the discount for that term.

Let.com Web App Hosting

Your next commit
has somewhere to go.

Compare app hosting plansNeed to build the app first?

Let.com

Coming soon.

Account sign-up, log-in and checkout are not available yet. You can explore our products and compare plans while we get everything ready.

Compare plans