Configure modules
The server provides feature availability and role settings. Choose the tools available to users instead of presenting the entire system to everyone. The client respects the connected server’s policy.
Deployment · Access management
Your own GoMsg server with Docker.
GoMsg supports a separate deployment and connecting its client to your own server. You can determine available modules and access rules for your team. Deployment needs infrastructure preparation and ongoing maintenance: backups, updates and service availability become the server owner’s responsibility.
The web client will open. Sign in or create an account to start chatting.
Your own server
Prepare a space for your team
First confirm access to the server build and its usage terms. An administrator sets up a test environment, configures addresses and checks sign-in, messages and files. Invite the team after reviewing security and testing backup recovery. Add the address of your own server in the client.
Keep deployments separate
Your installation uses its own database and file storage. The project’s public and local server configuration uses different databases. Connecting to a custom server does not merge them into one conversation history.
Manage the infrastructure
Components are built through Docker Compose. The stack includes PostgreSQL, Redis, MinIO, Centrifugo and LiveKit. Plan resources according to actual traffic, stored files and use of calls.
Understand security boundaries
Your server gives control over hosting and permissions, but does not by itself provide end-to-end encryption. The current server processes message content; administrators’ infrastructure access must be considered.
GoMsg
How to get started
- 1
Prepare the environment
After obtaining project access, install Docker with Compose. Configure domains, client and server addresses, and your own passwords and keys instead of development defaults.
- 2
Check a test deployment
Start the stack, register an account on your server and test messages, files and permissions. The first registered user becomes the owner. The commands below describe a test environment, not a secured production configuration.
- 3
Prepare for operation
Configure HTTPS, network access, backups and monitoring. Test recovery and updates in a test environment before connecting the entire team.
Your own server
What you can configure
What an administrator needs
Operating the server requires skills in Docker, networking and databases. We do not state untested minimum hardware requirements: begin with a test group and measure its workload.
- Docker Engine and Docker Compose
- A domain, HTTPS and appropriate network ports
- Disk space for the database and files
Evaluate services and integrations separately
Notifications, maps and AI have separate settings and keys. Choosing your own server does not automatically disable every external service. Decide which functions your team needs and configure their dependencies.
- Calls: networking and LiveKit
- Notifications: Web Push or FCM
- Maps and AI: provider availability and keys
docker compose build --no-cache server server-global client
docker compose up -d postgres redis minio centrifugo livekit server server-global clientFAQ
Questions and answers
Where can I find a server release and usage terms?
This site has no public server-release download button. The commands describe the source project when you have access to its source code and are for a test environment. Confirm usage terms before deploying; access to source code does not itself establish a licence.
Can I launch production with one command?
No. Compose helps build and start components. Operating them needs your own secrets, HTTPS, network configuration, backups and tested recovery.
Are messages encrypted so the server cannot read them?
That guarantee is not made. The current server processes message content. Account for this when choosing administrator access and retention policies.
Can I use GoMsg without running a server?
Yes. Start with public GoMsg in a browser or app. Your own server makes sense when you have hosting requirements and someone to maintain it.
GoMsg
Let your team get to know GoMsg first
Try your workflows in the public client. Plan a custom deployment with your administrator.