← Products

in development

Working together without pooling your data.

mesorium connects groups, chats, forums, meetings and shared working spaces with profiles, feeds, audio, video and public content. Internally, what should stay private stays private.

Join the waitlist

The problem

Collaboration and public communication live in separate worlds.

Inside a team: chats, meetings, files, forums and projects.

Facing outwards: social media, posts, videos, events and public profiles.

Content gets copied between them, knowledge loses its context, and the same people maintain several platforms in parallel.

The solution

mesorium brings private working space and public platform into one system.

Groups, chats, forums, meetings and shared working spaces meet profiles, feeds and public content.

You decide what stays internal and what gets published.

Collaboration, content and community can be part of the same system instead of living on separate platforms.

Further federation, and publishing structured research projects in full, are things we are building out step by step.

The interface

What you see when you open it.

Public feed with posts from connected areas.
Feed. Public posts, connected to the open network. Real interface, development state — “Resonance” was the internal working title of mesorium.
Video view with content from connected areas.
Video. Runs over the same connection as text. Real interface, development state — working title “Resonance”.
Messenger with a chat list, an encrypted one-to-one chat, a voice message and an attachment.
Messages. End-to-end encrypted, with voice notes and attachments in the same thread. Real interface, development state — working title “Resonance”.
Forum list with communities, reply counts and an agreement rate.
Forums. Communities with an agreement rate rather than an outrage metric. Real interface, development state — working title “Resonance”.
Event page with RSVP, stream connection and a discussion thread.
Events. RSVPs, stream and public discussion in one place. Real interface, development state — working title “Resonance”.
Audio home with library, queue and a persistent player bar.
Audio. Library and queue, connected to the open network. Real interface, development state — working title “Resonance”.
Profile page with posts, media, forums and personal details.
One profile for every format. Posts, media and forums in one place. Real interface, development state — working title “Resonance”.

Internal really is internal

Your area belongs to you.

Internal area, calendars, forums, encrypted direct messages. Each unit has its own area with its own data — no central pool for someone to object to. Who can see your member list is something you decide technically, not just contractually.

And outwards

A public face that belongs to you.

Profiles, public posts, a feed to follow and discover. Projects and events reach people, not only members — and what you publish is connected to the open network rather than locked in a walled garden.

Public read access is not built yet: today, someone who is not a member sees nothing. It is the next large block of work.

Part of it

The cockpit — your working space.

The cockpit is the working environment alongside the platform. It complements smolit rather than replacing the local assistant — and it sends nothing without your approval.

For those who want the detail

What runs underneath.

  • mesorium: Django backend, React client · connection outwards over ActivityPub (WebFinger, nodeinfo, signed inbox and outbox, Follow/Accept, taking in posts and videos)
  • Cockpit: Tauri 2, React and Rust · actions run through a gate with a confirmation layer · local merging of simultaneous changes (CRDT/Yjs)
  • Licences: mesorium under MIT, the cockpit under AGPL-3.0
  • Both run independently, with no hard dependency on each other

Where it stands

Where mesorium is.

Today

  • Private areas, groups and connections between areas are working.
  • The connection outwards works for text.

Next

  • Public read access — the next big block.
  • Signed builds for desktop and Android.

After that

  • Further work on the connection between areas.
  • Publishing the repositories.

This is where results from laborium are meant to land — so others can read, check and rebuild them.

Waitlist

Test mesorium with your organisation.

We are preparing the first supported organisation pilots. Sign up if you would like us to get in touch once places open.

Join the waitlist

Non-binding, and not a guarantee of access.