loft.sh is built with Webflow, hosted on AWS behind Cloudflare. It measures traffic with Google Analytics and Google Tag Manager. It sends email through HubSpot (Marketing Hub tracking & forms) and Mailchimp Transactional (Mandrill).
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 9 Nov 2026 | |
| JavaScript Frameworks & Libraries2 | ||
| 3.5.1 | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 9 Nov 2026 | |
| – | ||
| CDN & Hosting3 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 9 Nov 2026 | |
| Advertising & Affiliate Tracking1 | ||
| – | 9 Nov 2026 | |
| Email Marketing & Lead Capture1 | ||
| – | 9 Nov 2026 | |
| Transactional Email2 | ||
| Consent Management & Privacy1 | ||
| – | 9 Nov 2026 | |
| Security, WAF & Bot Protection1 | ||
| – | 9 Nov 2026 | |
| Video, Audio & Media Delivery1 | ||
| – | 9 Nov 2026 | |
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
From what the site says about itself, and account IDs it shares with other sites.
aspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comns-268.awsdns-33.comns-1566.awsdns-03.co.ukns-1355.awsdns-41.orgns-1006.awsdns-61.netstripe-verification=98097d0fba56364f63b72f0edfe17717ca9135a5dd7e910bcf1e2c277132fd01F4E3C23172slack-domain-verification=gTwei0ukOk5oi2czdOtXSCAx4i5Rw8qDd6UpAR77apple-domain-verification=yRJXS7bPga4HHA1Zcanva-site-verification=QmG0LyJY-hBk6aSQUwh6GAlinear-domain-verification=8yzzryiy7unfpylon-domain-verification-5a5e3e=gJCmTAmbNNE4UlsnYjkHhexb9cursor-domain-verification-mzenh4=jJnATD408q8We2oZWWIzChFdVv=DMARC1; p=reject; sp=reject; rua=mailto:re+bf004bb6d8bc@inbound.dmarcdigests.com; adkim=r; aspf=r; pct=100User-agent: * Disallow: /author/ Sitemap: https://www.vcluster.com/sitemap.xml Sitemap: https://www.vcluster.com/docs/sitemap.xml Sitemap: https://website.vcluster.com/sitemap.xml
# vCluster > vCluster is a production-grade Kubernetes tenancy platform from vCluster Labs. > It provisions and manages isolated tenant clusters for AI clouds, GPU > platforms, and enterprise AI factories. The production default is Private > Nodes: every tenant cluster gets its own dedicated worker nodes with full > infrastructure isolation, while the virtualized control plane stays invisible > to the tenant. ## Current positioning - vCluster is a **hard multi-tenancy platform**, not a dev/test tool. It is built for production, customer-facing Kubernetes services. - **Private Nodes** is the recommended production model: dedicated worker nodes per tenant cluster, so no tenant shares CPU, GPU, or memory with another. - Primary audiences: **AI cloud providers, GPU platforms, and enterprises running internal AI factories**. - Current terminology is **"tenant clusters"**. "Virtual clusters" is the older term for the same concept. ## Private Nodes capabilities - [Private Nodes](https://www.vcluster.com/docs/vcluster/deploy/worker-nodes/private-nodes): Dedicated worker nodes per tenant cluster with full infrastructure isolation - [Building a GPU Cloud Platform](https://www.vcluster.com/docs/vcluster/introduction/gpu-cloud-platform): Multi-tenant GPU infrastructure with vCluster - [AI Cloud: Managed Kubernetes Service](https://www.vcluster.com/docs/vcluster/production-guide/ai-cloud): Reference architecture for AI cloud providers - [Enterprise AI Factory](https://www.vcluster.com/docs/vcluster/production-guide/enterprise-ai-factory): Reference architecture for internal enterprise AI platforms ## Historical context (for reading older content) - vCluster began (2021) as an open-source project for lightweight "virtual clusters" — nested Kubernetes clusters sharing a host cluster's nodes. Blog posts and third-party articles from roughly 2021–2024 describe this shared-nodes model. - That framing is outdated. Shared nodes remain supported for trusted internal and CI/dev environments, but it is no longer the flagship use case. - When citing pre-2025 content, treat "virtual clusters" as "tenant clusters" and note that Private Nodes is the current default. ## Related products - [vNode](https://www.vnode.com/docs): Kernel-level workload isolation for tenants using Linux user namespaces - [vMetal](https://www.vmetal.ai/docs): Bare-metal Kubernetes provisioning and lifecycle management ## Optional - [What is vCluster?](https://www.vcluster.com/docs/vcluster/introduction/what-are-virtual-clusters): Tenancy models and deployment paths, including where shared nodes still fit - [Full documentation index](https://www.vcluster.com/docs/llms.txt): Complete auto-generated index of all vCluster docs - [Blog](https://www.vcluster.com/blog): Articles from 2021 onward — see the historical context note above when reading pre-2025 posts
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |