Authorize the repository
Choose the GitHub installation and repository in your Let.com project. A person connects the repository in the dashboard because future pushes can deploy code with the project’s environment.
Repository: orbit/customer-portal
GITHUB DEPLOYMENTYour commit.
Your next release.
Deploy from GitHub without moving your workflow out of Git. Connect a repository once, build from pushes, and review pull requests in their own preview environments.
Automatic deployments · PR previews · Commit-level release historyorbit / customer-portalLOCAL DEMOOPEN
Add project search #42
feature/search → main✓Source acceptedfeature/search · 72ae091
✓Build completeApplication output packaged
↗Preview availableReview this change before merging
REPOSITORY → BUILD → RELEASEConnect the source.
Connect the source.
Keep the release traceable.
GitHub stores your source. Let.com turns an authorized commit into an application deployment. Your production branch and preview branches have different jobs.
Set the production branch
Choose the branch that should publish production changes. Review the service, framework and deployment target. Keep required dependencies and a lockfile in the repository.
Production branch: mainPush and review
A push to the production branch starts a deployment. Pull requests can create previews. Follow build status, inspect the output, and trace the resulting release back to its source commit.
git push origin mainA URL FOR THE CHANGEReview the feature.
Review the feature.
Before it is production.
A preview environment gives reviewers a running application to inspect. Test navigation, forms and authenticated flows against the proposed change rather than guessing from a screenshot.
Fork pull requests need explicit approval for the reviewed commit. A new commit requires a new review. Preview access should never imply permission to run arbitrary code with production secrets.
mainProduction environment● Current releasefeature/searchPull request #42↗ Preview environmentfork / contributionUntrusted contribution◷ Approval requiredWHEN A BUILD NEEDS ATTENTIONFix the cause.
Fix the cause.
Keep the context.
A failed deployment is easier to resolve when you know which repository, commit and environment produced it. Work through the failing stage before retrying.
Deploying Next.js? Review the runtime requirements ↗01 / SOURCERepository access changed?
Check that the GitHub installation is active and still has access to the repository. Removing repository access stops new deployments.
02 / BUILDWorks locally, fails remotely?
Check the lockfile, dependency versions, build script and expected output. Keep server secrets out of browser-exposed variables and generated assets.
03 / RELEASEBuild passed, app failed?
Inspect runtime logs and the routes your users need. A code rollback is separate from restoring a database or reversing a schema migration.
GOOD IDEAS DESERVE A START
Your deployment workflow. One app plan.
Free, Pro and Team include GitHub and MCP deployment. Compare monthly capacity and choose your purchase term.
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.
- 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
POPULARBuilt for your next launch
Pro
More room for production apps and a small team.
$7/ month$14
Save $336 · regular 48-month total $672
$336 paid upfront for 48 months.
Renews at $336 / 48 months.
- Requests
- 10M
- Bandwidth
- 1 TB
- Edge CPU time
- 100M ms
- Build minutes
- 500
- Team members
- Up to 3
- Default usage budget
- $50
- 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.
- 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
| 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 |
MAKE THE BRANCH MEAN SOMETHING
A passing build.
A reviewed change.
Let.com can deploy the source you connect. Your repository defines which changes are ready to reach that source branch. Use GitHub’s available branch protections and required checks to make the team’s review policy concrete before automatic deployment begins.
Protect the production branch
Where your GitHub plan supports it, require pull request review and named status checks. Choose bypass permissions deliberately. A successful preview is useful evidence, but it does not enforce a merge rule unless the repository is configured to do so.
Test the contract
Run checks that reflect the app’s behavior: build output, critical API operations and authorization boundaries. Give required jobs unique names and keep the source revision visible. Avoid treating a green dependency install as proof that the product works.
Review the actual change
Inspect new dependencies, configuration and schema migrations along with the interface. Make the production branch the result of a decision. The hosting connection should not silently become the place where your team invents its review policy.
REPEATABLE INPUTS
Same source.
Understandable build.
Commit the files that determine the build, including the lockfile and relevant runtime configuration. Document the project root in a monorepo. A release should be explainable by its source revision, build settings and environment rather than by the state of one developer’s machine.
Keep private values separate
Store production credentials in sealed server configuration. Inspect what build-time variables can reach public bundles. Do not expose privileged deployment or database secrets to untrusted pull request code, including scripts run during dependency installation.
Keep preview data deliberate
Use test records and suitable credentials for previews. Check the environment before migrations or background jobs run. A preview URL is not a guarantee that its backend is isolated from production data; you must configure that boundary.
name: Application checks
on: [pull_request]
jobs:
app-build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: actions/setup-node@v7
with:
node-version: 22
cache: npm
- run: npm ci
- run: npm run buildIllustrative build check · select supported versions and pin actions to reviewed commit SHAs for stricter controls.
THE RELEASE HAS TWO TIMELINES
Code moves quickly.
Data needs continuity.
A source deployment and a database migration are related changes with different recovery behavior. Keep them coordinated without assuming they are one reversible operation. The previous application should remain compatible long enough to give a code rollback a useful chance.
- Expand before removing
- Add new columns or tables before deploying code that requires them. Backfill deliberately, then remove old fields only after earlier code no longer depends on them. Use the direct Postgres connection for migrations rather than the transaction pool.
- Check the live result
- After deployment, verify the critical journey and inspect status and relevant logs. Confirm new code can read existing records. A completed build does not prove the configured domain, session flow or third-party integration works.
- Recover the right layer
- Roll back code for an application regression. Use database recovery procedures for damaged data. Managed Postgres has daily backups, while optional HA and point-in-time restore depend on the database plan. Review their status before a high-impact migration.
Four collaborators. No four-seat surcharge.
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.
Hosting operations, working together.
Create.com provides web hosting, WordPress hosting, reseller plans 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.
- Backend
- PostgreSQL
- Queue
- Valkey
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
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
THE DETAILS
GitHub deployment questions.
Is this the same as GitHub Pages?
No. GitHub is the source repository in this workflow. Let.com builds and hosts the application. Static files, compatible edge applications and container services have different runtime requirements; choose the target your code needs.
Do I need to create a GitHub Actions workflow?
The repository integration uses GitHub events to start deployments. You can keep Actions for your own tests and checks, but connecting a repository does not require writing a separate deployment workflow file.
Does every branch publish to production?
No. Pushes to the configured production branch deploy production. Other branches and pull requests use preview environments when previews are enabled. Review the connected project settings before pushing.
Can an AI agent connect my GitHub repository?
The current repository connection step requires a person in the dashboard. Once connected, pushes trigger deployments. MCP provides a separate path for deploying files or source from an authorized AI workflow.
What happens when I disconnect GitHub?
New pushes stop deploying and open preview environments are scheduled for cleanup. Disconnecting source control is different from deleting the existing production project.
Where do I compare pricing and included resources?
The App Hosting Pricing page lists Free, Pro and Team, all billing terms and monthly resource allowances. Database and container compute are separate from the base edge and build plan.
Keep your source. Ship your work.
Connect the repository your team already uses. Choose the plan and runtime that fit the application.