On this page
The word “cloud” does too much work in technology marketing. Inside Wonder, it names two related but different offerings. Wonder Desktop is a managed virtual desktop you open in Chrome. Wonder Cloud (cloud.thewonder.cloud) is infrastructure-as-a-service for teams that want to build and run their own workloads. Choosing correctly saves months of confusion.
Wonder Desktop in one paragraph
Wonder Desktop is a VDI-style product experience: a Windows workspace streamed to the browser, with modalities for family, education, and business; facial recognition for login trust; MYDOCS; @thewonder.email; VoIP on eligible plans; and a curated software library shaped by requests and voting. You are buying a ready workplace, not a construction kit.
Wonder Cloud in one paragraph
Wonder Cloud is IaaS: virtual machines and cloud building blocks for people who need to architect networks, automation, and custom environments. You bring more operational responsibility—and more freedom to assemble nonstandard stacks. The audience is closer to builders and IT architects than to a parent opening homework apps after dinner.
Different questions, different products
Ask Desktop questions when you care about: Can my team or family open a consistent Windows session on weak endpoints? Do we need separate profiles under one contract? Where do files and mail live? How does facial login protect shared devices?
Ask Cloud questions when you care about: Can we provision machines for a proprietary pipeline? Do we need infrastructure primitives rather than a prebuilt desktop image? Are we prepared to manage more of the stack ourselves?
If you mix the questions, you either under-serve employees with raw VMs and no workplace product, or you try to force developers to live inside a desktop modality that was never meant to replace their toolchain.
How they can coexist
Many organizations will use both. Staff live in Wonder Desktop for Office, line-of-business clients, MYDOCS, and calls. Platform teams use Wonder Cloud to host services, test beds, or specialized compute. Partners should learn to route buyers: households and schools almost always start on Desktop; engineering firms might evaluate Cloud in parallel.
What neither product is
Neither is “only cloud gaming,” though Desktop can run entertainment software from the library. Neither removes the need for network honesty—latency still shapes interactive feel on Desktop, and IaaS still needs thoughtful connectivity. Neither replaces identity discipline: Desktop emphasizes personal login trust; Cloud expects sound access control on infrastructure you design.
A quick comparison table
| Topic | Wonder Desktop | Wonder Cloud | | --- | --- | --- | | Primary user | Families, schools, business end users | Builders, architects, platform teams | | Access pattern | Chrome cloud desktop session | Infrastructure APIs/consoles for VMs and building blocks | | Included workplace services | MYDOCS, mail, VoIP (by plan), software library | You assemble what you need | | Identity focus | Profiles + facial login trust | Access control you design for infrastructure | | Best first question | “Do people need a ready Windows workplace?” | “Do we need to build systems on IaaS?” |
A decision sentence you can reuse
“If you need a workplace in Chrome for people, choose Wonder Desktop. If you need infrastructure to build systems, choose Wonder Cloud.”
That sentence keeps landing pages, reseller conversations, and internal IT roadmaps aligned. Wonder’s brand spans both, but your week will only feel coherent if the product matches the job.
Explore Desktop when you want modalities, MYDOCS, mail, and a managed library. Explore cloud.thewonder.cloud when you want IaaS. Same company, different altitude—on purpose.
Buying mistakes to avoid
Do not buy Desktop vouchers expecting to assemble custom VPC topologies. Do not hand every employee a raw IaaS project when they only needed Office, MYDOCS, and a reliable VoIP number. Resellers who keep the altitude clear reduce refund drama and support tickets.
If your roadmap includes both people workspaces and builder infrastructure, sequence intentionally: stabilize Desktop for staff first, then grow Cloud for platform needs—or the reverse if you are a product company that already lives in infrastructure and only later needs a managed desktop for operations staff.