This article is based on a piece originally published on about.gitlab.com by a GitLab team member. The observations and framing below reflect GitLab’s perspective on remote work.
As an all-remote organization, GitLab team members are frequently asked what it is like to work without a physical headquarters. People are curious — the idea of working from home is appealing, but a company that is fully remote still strikes many as unconventional. Some argue it simply cannot work at scale, despite a growing number of organizations proving otherwise. The rise of the all-remote workplace draws a compelling parallel to the rise of cloud computing: a model once dismissed as impractical that gradually became the default expectation across the industry.
Bringing Cloud Computing to the Mainstream
Network computing has existed for decades, but the concept of cloud computing gained mainstream visibility around the turn of the millennium, driven in large part by companies like Google and Amazon. The core idea was straightforward: users could access files, applications, and even raw compute resources over the network — from any location — without needing a physical data center of their own. What mattered was whether the service met their requirements, not where the hardware physically lived.
Early adoption was slow and skeptical. Performance, reliability, and security were all heavily scrutinized. But the deepest challenge was psychological: organizations were being asked to trust infrastructure they could not physically see or touch. That required a fundamental shift in mindset.
As confidence grew, software-as-a-service (SaaS) companies emerged. Salesforce and Workday were architected for the cloud from day one, and their success opened the door for a wave of SaaS applications across every business category. Today, even the most conservative enterprises are actively migrating legacy, mission-critical systems to cloud environments — something that would have been considered reckless a decade earlier. Cloud, once scoffed at by many IT leaders, is now a standard component of enterprise technology strategy.
The Evolution of the Remote Workplace
Remote work has followed a strikingly similar arc. Working off-premises has always existed in some form, but it was historically limited to specific roles, contractors, or niche companies. It was the exception, not a strategic model in its own right.
The intermediate stage — hybrid-remote, where some employees work remotely while the majority report to a physical office — mirrors the hybrid-cloud phase that many organizations passed through before committing fully to cloud-native infrastructure. Just as cloud-native companies like Salesforce demonstrated what was possible when you designed for the cloud from inception, all-remote companies like GitLab demonstrate what becomes possible when remote is not a policy addendum but the foundational operating model.
GitLab’s position, as stated in its public handbook, is that all-remote will become increasingly common as best practices mature and tooling improves — particularly for knowledge-work organizations where physical manufacturing is not a constraint. The expectation is that the question will eventually shift from “why would a company go all-remote?” to “why wouldn’t it?”
What All-Remote and Cloud Computing Have in Common
Beyond their similar adoption trajectories, the operational benefits of all-remote work map closely to the well-documented benefits of cloud computing. The following parallels are worth examining in detail:
1. Increased Agility
Cloud computing lets organizations scale resources up or down based on demand without lengthy procurement cycles. All-remote work offers a similar organizational agility: teams can be expanded, restructured, or deployed into new markets without being constrained by office space, geography, or relocation timelines.
2. Cost Reduction and Lower Barriers to Entry
Cloud computing shifts capital expenditure (CapEx) to operational expenditure (OpEx), removing the need to purchase and maintain physical servers. All-remote companies experience an analogous shift: the elimination of office leases, facilities management, and the associated overhead converts fixed costs into variable ones. This also lowers the barrier to entry for new companies, which can build and scale without requiring a physical footprint from day one.
3. Location Independence
Cloud resources are accessible from anywhere with an adequate internet connection — the physical location of the compute is abstracted away. All-remote work applies the same principle to people: the best candidate for a role can be hired regardless of where they live, dramatically expanding the available talent pool and enabling genuinely global teams.
4. Asynchronous Collaboration as a Productivity Multiplier
In cloud environments, distributed systems allow multiple processes to operate on shared data concurrently, avoiding the bottlenecks of sequential, single-threaded operations. Remote-first organizations that embrace asynchronous communication see a similar dynamic: team members across time zones can contribute to the same documents, code reviews, or decisions without waiting for a synchronous meeting to move things forward. When done well, async work reduces interruptions and increases the total throughput of a distributed team.
The Common Challenge: Trust in the Model
The deepest parallel between cloud adoption and remote work adoption is not technical — it is cultural. In both cases, the primary obstacle is trust. Organizations resisted moving workloads to the cloud because they could not physically control the infrastructure. Organizations resist going fully remote because they cannot physically observe their employees. In both cases, the shift requires moving from measuring inputs (physical hardware you own, employees you can see in an office) to measuring outputs (service reliability and uptime, work completed and value delivered).
The cloud has largely won that argument. The evidence suggests that all-remote work is following the same path — and that the organizations willing to make the cultural shift earliest will have a meaningful advantage in talent acquisition, operational flexibility, and cost structure.
Original source: about.gitlab.com. This article reflects perspectives shared by GitLab on all-remote work as of the original publication date (October 2019).