flat.social vs Meetropolis

flat.social is a browser-based virtual meeting and events space where people move around shared rooms and talk with nearby participants. Audio volume and video connection respond to proximity. A flat can combine Open Spatial rooms for mingling, Conference rooms for presentations, and Chat rooms for text. Participants can draw, write and add images to shared whiteboards and sticky notes; built-in activities include football, chess, surfing, dice and arcade cabinets. Conference rooms support screen sharing and speaker or gallery layouts. Guests can join from a link, and the service runs in Chrome, Edge, Firefox and Safari. The Free plan costs nothing and allows up to five people at once with unlimited session length. A Day Pass costs $2, paid once, billed at $2 per seat for 24 hours, requires at least 10 seats and supports up to 100 people. Monthly costs $6 a month, billed at $6 per seat per month, with 10 to 100 seats, attendance insights, branding removal, roles and advanced access control, and priority support. Larger capacity can be discussed with the company. Slack users can start a flat with /flat and schedule recurring weekly events.

Meetropolis is an open-source virtual office for remote teams, set in a live 2D world with proximity-based spatial audio and video. Guest access and screen sharing are available. Phaser provides the live-world layer, while Colyseus powers real-time multi-user interaction. Teams can use the web application or self-host it with the supplied Docker Compose setup, which includes the web app, server, database, and LiveKit service. The self-host configuration uses PostgreSQL and documents SMTP email settings for invites, guest magic links, verification links, and welcome messages. Personal API tokens can control microphone, camera, screen sharing, and do-not-disturb status. Server components use AGPL-3.0-only; the web client and shared types use MIT. Tiamat UG offers a commercial license. The open-source server permits 25 concurrent users across the whole server, and the 26th user is kicked. Production self-hosters must supply a TLS terminator, configure production secrets and allowed CORS origins, and may need TURN for restrictive networks.