Skip to content

Your server, your media, your data

Run it all on your own server

One Docker Compose stack brings up the app, the PostgreSQL database and your own LiveKit media server, and database migrations run when it starts. Audio and video go between your people and your machine, with no vendor in the path.

The flow
  1. Meet
  2. Capture
  3. Act

Media

Calls that never leave your network path

The media server is yours. A LiveKit SFU forwards streams rather than transcoding them, so a modest machine goes a long way, and the traffic goes from your people to your server and back rather than through anyone else's cloud.

  • Your own LiveKit SFU, not a shared media cloud
  • Forwarding rather than transcoding keeps CPU cost modest
  • Reverse-proxy guides for nginx or Caddy

Data

Nothing to request, because nothing left

Uploads, documents, whiteboards, chat history and recordings live in your database and on your storage. Data residency stops being a contract clause and becomes a fact about where the server is.

  • One PostgreSQL database holds the workspace
  • Uploads and recordings on storage you choose
  • Your own AI provider keys, encrypted at rest

Scale

One deployment, several organisations

A single instance can host more than one organisation, each with its own members, roles, floors and enabled modules. Useful for an agency running client workspaces, or a group of companies sharing one operations team.

  • Organisations kept apart by permission checks
  • Each one chooses which modules are switched on
  • One login can belong to several and switch between them
Read the security model

FAQ

Questions about self-hosting

Something else on your mind? Write to hello@remotedesk.space.

What do we need to run it?

A Linux host with Docker, a domain and a certificate. The media ports must be reachable from the internet directly rather than through a proxy, which is the one networking detail worth reading the deployment guide for.

Is the self-hosted build missing features?

No. It is the same application. The difference is where it runs and who holds the database.

Can we use our own AI provider keys?

Yes, and on a self-hosted deployment that is the normal arrangement. Keys are entered by an admin in the app and stored encrypted at rest.

Is there a hosted option as well?

Yes. You can start hosted and move to your own infrastructure later, or never. The application is the same either way.

Bring up the stack and take a seat

Talk to us about running Remote Desk on your own infrastructure.