by vractal



Online open-source workplace for distributed teams.

CircleCI Status chat on Slack

Welcome to the #matrix

The objective of #matrix project is to offer a virtual environment office, as nice as physical offices. When we are working in a physical office is very common entering in discussion threads in many different environments, for example: on coffee, on lunch and others.

When we are working remotely there are no conversations like in a physical office. The #matrix project was born as a proposal to better that experience. The idea is to create a lot of virtual rooms where people can see and enter these rooms to participate.

#matrix produces a virtual office for remote teams. In this project, you can run a virtual office to simulate the physical environment. Read more on this post in Medium.

Matrix Home Screenshot

Table of Contents

Understanding #matrix


The inside of #matrix there are some rooms. In this rooms is possible to see others colleagues and if they are talking or in a meeting in the avatar will appear a head set icon. (eg. In the image the guys in the Platform-Email room are in a meeting)

Office Page With Sidebar

Availability And Meetings

#matrix is a virtual environment office, so you can show you are available for the other on enter in a room through the ENTER ROOM button. This is like "Hey, I am here in the office". Or you can enter in a meeting through the button ENTER MEETING.

The embeded meet is provided by service and this service is maintained by the Jitsi team at 8x8. Access the jitsi GitHub and learn more about this amazing video bridge service. You can change that using external meet option in any room.

Meeting Room With Sidebar


Environment Variables

The #matrix project has some environment variables that important to define.

  • We are using Google to authorizations, you need create a credential here and before define this variables:

  • You can change the secret and maximum age from session:

  • You can define a white List of trusted email domains can enter in the #matrix

  • If you are running with ssl It's important to configure SSL, to define this:

  • The #matrix needs to know, where it get rooms definitions:

  • There is a config that define the rooms of The #matrix, If you want to customize your rooms or add and a new room, you have to configure a ROOMS_SOURCE=ENVIRONMENT and config ROOMS_DATA like the example:

            "name":"WAR ROOM CDP"
            "name":"Data Services",
      	  "externalMeetUrl": "https://external-url-room/key-room"

External Meet

The embeded meet is provided by service, but you can change that in any room, using serices like Meet or Zoom. For that, you just need provide the parameter externalMeetUrl in your room config:

	      "name":"Meeting External",
	      "externalMeetUrl": "https://external-url-room/key-room"


The login is so simple. You only need to configure the Google API credentials following this step by step .

Login Login in Dark Mode

Docker Compose

If you want run the #matrix, you need docker-compose and follow steps:

  1. Clone this repository git clone

  2. We are using Google to authorizations, you need create a credential here you can follow step by step

  3. duplicate file variables.example.env and rename to variables.env, after that set your environment variables;

  4. Run application with docker compose:

     $ docker-compose up
  5. Open your browser and access:

  6. When you finish, you can run:

     $ docker-compose down


If you prefer, you can run #matrix on GCP:

Run on Google Cloud

On Heroku

If you prefer, you can run #matrix in Heroku:


On Kubernetes

It is possible to run #matrix on Kubernetes, what you need to have is a running cluster and a Docker repository to fetch image from.

Example files can be found in docs/kubernetes/. Copy the files and follow the instructions bellow:

  1. Change the values for MATRIX_IMG and MATRIX_TAG in deployment.yaml
  3. Add your Google Credentials in credentials.env and create the secret with
     kubectl create secret generic matrix-credentials --from-env-file=env_credentials
  4. Create you rooms.json file and create a config map with
    kubectl create configmap matrix-rooms --from-file=rooms.json
  5. Apply the services and deployment files
    kubectl apply -f deployment.yaml
    kubectl apply -f service.yaml

Currently the service is using a LoadBalancer, it is possible to change to ClusterIP and use it behind an Ingress as well. Also note that in the example we are using HTTP, it is highly recommended to use HTTPS instead!

If you are using HTTPS, do change ENFORCE_SSL to true and add your company domain to WHITELIST_DOMAINS.

Production concerns

If you will run in production we strongly recommend you close your environment using an internal VPN. In this solution everybody with the link and a valid google credential can enter your virtual office. Because this is important for you to maintain your environment closed. Or you can define a variable WHITELIST_DOMAINS to limit only authorized users to enter in the #matrix. You have to choose a strong key to the COOKIE_SESSION_SECRET and have to put in GOOGLE_CALLBACK_URL your production domain.



Version Name Description Docs 2.0.0 Seraph New authentication Migration guide to 2.0.0 1.1.0 Morpheus New layout Pull request 1.0.0 Neo The one project -

Frequently Asked Questions

Some questions come up over and over again. Check here first: FAQ

Get in Touch

There are several ways to get in touch with us:

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Juliemar Berri

📝 💻 🚧 📖 📢
Bruno Nardini

💻 🚧 📖
Alessandro Tegner

💻 🚧 🚇
Rogerio Angeliski

💻 🚧 📖
Diogo Nicoleti

Ricardo F. Verhaeg


This project follows the all-contributors specification. Contributions of any kind welcome!

Everyone interacting in #matrix codebase, issue trackers, chat rooms, and mailing lists is expected to follow code of conduct.


The #matrix is released under the MIT License

"The answer is out there, Neo, and it's looking for you, and it will find you if you want it to."