Workadventure

Open-source virtual office, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source virtual office platform built as a 2D, 16-bit RPG — your team navigates pixel-art rooms with avatars, and proximity triggers real video/audio conversations [README].
• Who it’s for: Remote and hybrid teams who find Zoom fatigue real, event organizers running online conferences or hackathons, educators building virtual campuses. Also founders who want to escape Gather.town’s pricing — the homepage literally offers a migration discount [website].
• Cost savings: SaaS pricing details weren’t available in scraped data (check workadventu.re/pricing), but the self-hosted path runs on Docker Compose with a few containers — a $10–20/mo VPS covers a small team.
• Key strength: Proximity-based spontaneous video conversations. You walk your avatar near a colleague and a video bubble opens. It replicates the accidental hallway conversation that fully async remote work kills [README][website].
• Key weakness: AGPL-licensed open-source core means you can self-host freely, but commercial redistribution or embedding in your own product requires a conversation with their legal team. Map-building requires a separate tile editor (Tiled), which is a real barrier for non-technical teams [README].

---

What is Workadventure

Workadventure is a browser-based collaborative virtual world rendered as a 2D, 16-bit RPG. You and your team each control an avatar on a tile map — a pixel-art office, campus, or conference venue you design. Walk close enough to another avatar and a video/audio chat bubble opens automatically. Walk away and it closes. That’s the core mechanic, and it’s deceptively simple [README].

The project describes itself as “a collaborative web application (virtual office) presented as a 16-bit RPG video game” [README]. The company’s own marketing leans harder into “Virtual Office App / Metaverse” and positions it for digital workplaces, virtual events, gamified classrooms, and virtual recruitment [website]. All of those use cases run on the same core tile-map engine.

What makes the pitch legible is the alternative: endless Zoom calls with no sense of space or serendipity. Workadventure simulates the spatial awareness of an office — you can see who’s clustered in a conference room, who’s quietly at their desk, who’s available for a quick chat. The 16-bit aesthetic keeps it lightweight and browser-native, not a heavy metaverse client download [README].

As of this review the project sits at 5,326 GitHub stars and is backed by a French company (TheCodingMachine) that also sells a SaaS version and professional services [README][website].

---

Why people choose it

The case for Workadventure comes down to one failure mode it solves that other remote tools don’t: the death of spontaneous, low-stakes conversation.

Slack threads and scheduled Zoom calls cover deliberate communication. They don’t cover the ten-second “hey, quick question” that happens when you walk past someone’s desk. Workadventure simulates exactly that. Approach an avatar, a video bubble opens, the question gets answered in thirty seconds. Neither party booked a meeting [website].

The homepage explicitly calls out Gather.town migration with a discount offer, which tells you who the target switcher is. Gather.town pioneered this spatial-office concept and was popular during COVID-19, but their pricing model and reliability drew complaints. Workadventure positions itself as the open-source, self-hostable answer to the same idea — you get the spatial office concept without being locked into Gather.town’s SaaS pricing [website].

The event use case is also genuinely strong. The website shows case studies including a 100% online hackathon by Pasqal (ceremonies, webinars, 15 team offices on one map) and University of Rennes building a digital campus — not marketing filler, but operational deployments where the spatial metaphor made sense for organizing large distributed groups [website].

The GDPR and open-source positioning matters particularly for European clients. The homepage leads with both, which signals the target market: companies in regulated industries or EU jurisdictions who need data residency guarantees [README][website].

---

Features

Core spatial mechanics:

• Browser-native — no desktop client required, works on desktop, mobile, and tablet [website]
• Proximity-triggered video and audio bubbles — walk toward someone to start a conversation, walk away to end it [README]
• Private conversation bubbles — only people within range can hear/see the exchange [README]
• Avatar customization, with the option to upload your own visual assets [website]

Map system:

• Fully customizable tile maps built with Tiled editor (third-party, free, separate download) [README]
• Large community map library available at awesome-workadventure [README]
• Map objects can embed websites, YouTube streams, Google Docs, Jitsi rooms — essentially iframes in the world [README]
• White-label mode for corporate brand identity on custom maps [website]

Integrations:

• Microsoft Teams and Google Workspace connectors mentioned on the homepage [website]
• Discord, Element integration [website]
• Native Jitsi Meet support for video rooms beyond the proximity bubble [README]
• “Native integrations are our specialty” — custom app integration available on commercial tiers [website]

Auth and access:

• SSO via OIDC (OpenID Connect) — the default Docker Compose setup ships with a mock OIDC server for dev [README]
• Support for anonymous access (OIDC-less deployment option available) [README]

Use case templates:

• Virtual office (digital workplace, hybrid teams)
• Virtual events (hackathons, conferences, product launches)
• Digital classroom (gamified learning, virtual campus)
• HR and recruitment (career fairs, onboarding, job dating) [website]

What’s missing from the open-source tier: The website advertises “personalized customer support,” “dedicated support,” “fast onboarding,” and custom map building — these are all commercial/SaaS perks, not bundled with self-hosting [website].

---

Pricing: SaaS vs self-hosted math

Official SaaS pricing: The scraped website content links to a pricing page (workadventu.re/pricing) but the actual tier prices weren’t captured in the data available for this review. The homepage mentions “Try for free, No registration,” which suggests a free tier exists. Check the current pricing page directly — SaaS pricing for spatial office tools changes frequently as the category is still maturing.

The migration angle: The explicit “Migrating from Gather.town? Get a discount!” banner on the homepage is the most useful pricing signal available. If you’re already paying for Gather.town, Workadventure’s team will negotiate [website].

Self-hosted cost:

• Software: open source, $0 [README]
• Infrastructure: Docker Compose setup — you need a VPS with Docker, Redis, and a reverse proxy. A $10–15/mo Hetzner or DigitalOcean node handles a small team (under 50 concurrent users)
• Domain + TLS: Caddy or nginx + Let’s Encrypt adds $0–10/mo
• Your time: see Deployment section below

Gather.town for comparison (the explicit competitor): Free up to 25 participants; paid plans historically ran $7/user/month for larger teams, which for a 20-person company means ~$140/mo. Self-hosted Workadventure on a $12 VPS replaces that completely, assuming you have someone technical enough to deploy it.

---

Deployment reality check

Workadventure is architecturally more complex than most self-hosted tools in this category. The README’s /etc/hosts entry for local development lists thirteen separate subdomains: oidc, redis, play, traefik, matrix, extra, icon, map-storage, uploader, maps, api, front — all workadventure.localhost variants [README]. That’s a microservices architecture with a Traefik reverse proxy, and it’s not what you’d expect from a simple self-hosted tool.

What you actually need for production:

• A Linux VPS (4GB+ RAM recommended — multiple services run concurrently)
• Docker and docker-compose
• Redis (bundled in the docker-compose or external)
• A reverse proxy with TLS (Traefik is the default in their compose file)
• OIDC provider if you want SSO (or remove it for anonymous access via the docker-compose-no-oidc.yaml override) [README]
• Kubernetes + Helm for larger deployments — that option is supported [README]

Map building is the real barrier. Creating your virtual world requires using Tiled, a free open-source map editor. It’s not hard, but it’s a separate tool with its own learning curve. The community provides pre-built maps, and there’s a healthy awesome-workadventure resource list [README]. But “download Tiled, learn tile layers, design a map, export it, upload it” is a non-trivial ask for a non-technical founder doing this alone.

Windows gotcha: The README explicitly warns Windows users to set core.autocrlf false before cloning or the line endings will break the Docker setup [README]. Worth knowing if your team is Windows-heavy.

Realistic time estimates:

• Technical user who knows Docker: 1–2 hours to a working instance, half a day to a decent-looking map
• Non-technical founder with a guide: budget a full day including map setup, or hire someone for the initial deployment
• Custom-branded map with company assets: add another day for anyone who hasn’t used Tiled before

The project’s production install guide lives at docs/others/self-hosting/install.md in the repo — read it before you start, not after you’re stuck.

---

Pros and Cons

Pros

• Proximity-based conversation is genuinely the right UX for this problem. Walking toward someone to talk and walking away to end the call maps to human spatial instincts. It beats every scheduled-meeting-first tool for low-stakes communication [README][website].
• Browser-native. No app download, no plugins. Works on mobile and tablet too. That matters for contractors, clients, and event attendees who you can’t ask to install anything [website].
• GDPR-compliant self-hosting. Your video streams, chat, and user data stay on your infrastructure. For European companies this is table stakes, and Workadventure delivers it [README][website].
• Rich event and conference use cases. The tile-map engine naturally supports distinct rooms, hallways, and social zones — organically solving the “breakout rooms feel sterile” problem of Zoom events [website].
• Active community. awesome-workadventure, a Discord server, a community map library — the project has genuine ecosystem depth for customization [README].
• Helm chart for Kubernetes. Serious self-hosters who want the full production stack can do it properly [README].
• SSO via OIDC out of the box. SSO isn’t paywalled — it’s in the default Docker Compose, configurable [README].

Cons

• Map-building requires Tiled. The visual environment that makes Workadventure compelling has to be built separately with a tile editor. Non-technical teams need help here, or need to use pre-built community maps [README].
• Microservices complexity. Thirteen subdomains in the local dev setup is a signal: this is not a single-container deploy. Upgrades, debugging, and maintenance are more involved than a monolithic tool [README].
• License is not permissive. The open-source core is AGPL-licensed (based on the project’s documented licensing history) — fine for internal self-hosting, but if you want to embed this in your own SaaS or redistribute it commercially, you need a commercial agreement. The merged profile doesn’t list the license, which itself is a yellow flag.
• No pricing transparency. The website pushes to a pricing page without showing numbers in page copy. For a self-hosted tool targeting founders who want to escape SaaS bills, that’s an odd omission.
• The metaverse framing is overselling it. “Virtual Office App / Metaverse” headline, “immersive experience” copy — it’s a 2D tile map with video bubbles. That’s genuinely useful, but it’s not a metaverse. Non-technical buyers may feel misled after signup [website].
• Relatively modest GitHub traction (5,326 stars) compared to category peers. Gather.town alternatives have fragmented; this is one of several rather than the dominant open-source leader [README profile].
• Mobile experience is secondary. The README mentions mobile support, but a 2D tile-based virtual office designed for keyboard-and-mouse navigation will always be a compromise on a phone screen.

---

Who should use this / who shouldn’t

Use Workadventure if:

• Your remote team has 5–50 people and you’re trying to rebuild the serendipitous communication that disappeared when you went fully remote.
• You run online events (conferences, hackathons, career fairs) and Zoom breakout rooms feel sterile and hard to navigate.
• You’re an educational institution (university, coding bootcamp) running virtual classes or campuses where spatial presence helps engagement.
• You’re in Europe and need data residency — self-hosting Workadventure keeps everything on your infrastructure.
• You or someone on your team is comfortable with Docker and doesn’t mind spending a day on initial setup.

Skip it if:

• You need a plug-and-play tool with zero technical setup. The Tiled map requirement and microservices stack will frustrate a non-technical solo founder without help.
• Your team is already-distributed async and primarily communicates via Slack/Notion/Linear. Workadventure solves synchronous presence; if you’ve built an async culture intentionally, the spatial office adds overhead without benefit.
• You want to embed this in your own product or SaaS. AGPL licensing makes that complicated.
• You’re a very large company (500+ people) evaluating enterprise-grade virtual office — there are more enterprise-hardened options, and Workadventure’s self-hosted path requires proportionally more DevOps investment at scale.

Stay on Gather.town if:

• You’re already using it and it works. Gather.town’s managed SaaS removes all the self-hosting complexity. If you don’t have technical resources and the pricing is tolerable, don’t migrate for the sake of it.

---

Alternatives worth considering

• Gather.town — The original spatial office tool, fully managed SaaS. Easier to start, no self-hosting, but pricing scales with team size and you’re locked to their infrastructure. Workadventure explicitly targets Gather.town migrants [website].
• Teamflow — Slicker UI than Workadventure, but closed-source and SaaS-only. Targets the premium segment.
• Kumospace — Another spatial video platform, SaaS, polished UI. No self-hosting option.
• Hubs by Mozilla — Open-source 3D virtual spaces, more immersive but heavier and less practical for daily office use.
• Jitsi Meet — If what you actually need is just video conferencing without the spatial metaphor, Jitsi is simpler to self-host and operationally lighter.
• Miro or FigJam — If your remote collaboration pain is around whiteboarding and async visual work rather than synchronous presence, these solve a different but related problem.

For a non-technical founder, the realistic decision is Workadventure (self-hosted) vs. Gather.town (SaaS). The self-hosted path saves money and gives you data control; the Gather.town path saves time and removes operational responsibility. The migration discount Workadventure offers suggests the cost comparison lands in Workadventure’s favor often enough that they want to make it frictionless.

---

Bottom line

Workadventure solves a real problem — the serendipity deficit of fully remote work — with a genuinely clever mechanic. Proximity-triggered video conversations in a spatial environment are more natural than most remote-work tooling. The 16-bit RPG aesthetic is a choice that some teams will love and others will find juvenile; that’s a culture call, not a technical one.

The self-hosted path is viable but not lightweight. You’re deploying a multi-service architecture with Redis, Traefik, an OIDC provider, and map assets built in a separate tile editor. For a technical founder or a team with a DevOps person, that’s fine. For a non-technical founder who just wants remote team presence and no SaaS bill, the operational overhead is real. If that’s the gap — Workadventure is exactly what upready.dev deploys for clients: one-time setup, your infrastructure, no recurring vendor dependency.

---

Sources

Primary sources used:

• GitHub repository and README: https://github.com/workadventure/workadventure (5,326 stars, open source)
• Official website and homepage: https://workadventu.re
• Pricing page: https://workadventu.re/pricing
• Self-hosting documentation: https://github.com/workadventure/workadventure/blob/develop/docs/others/self-hosting/install.md
• Community resource list: https://github.com/workadventure/awesome-workadventure

Note: The third-party review sources provided for this article were unrelated to Workadventure (baby name databases, tourism guides). No external review data was available for synthesis. All claims in this article derive from the official GitHub README, website scrape, and product profile data.