Messaging

Matrix,in a session of your own

Element, on a Void Linux desktop of your own.Encrypted rooms, spaces and calls, with the device keys on the volume.

Element 1.12.102 cores · 4 GBOpens in a browser tab

hub://element

$ dxflow workflow create --identity element hub://element --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

One client,any homeserver

Point it at matrix.org or the server your own organisation runs.

End-to-end by default

Rooms are encrypted, and the device keys stay on the volume, not in a browser.

Spaces and rooms

Group the rooms a project needs, with threads and read receipts in each.

Calls and bridges

Voice and video in a room, and bridged networks beside the native ones.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that, which matters more here than most places.

PANEL and TASKBARBoth hidden, so the client has the whole screen. Show either one to get the desktop back.

AUDIOOff by default. Turn it on before you join a call, or you will be the one nobody can hear.

start it your way

$ dxflow workflow start element --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start element --override env.app.AUDIO=on --link

The session

The clientfills the screen

Streamed to your browser, with Element already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStorageyour files, kept between runs

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

The keys staywith the profile

A Matrix session owns its own encryption keys, and here they live on the volume with everything else.

Verified once

The profile persists, so the device stays verified and the history stays readable across restarts.

Keys on a disk you own

Anyone who reaches the volume or the tab reaches the encrypted rooms. The password is the protection.

amd64 only

Void packages Element for x86-64 alone, so this entry needs a machine of that architecture.

The image

Pulled once,then it stays

Element arrives as one image. This is what comes down the first time, and what the disk should have free for it.

439Mamd64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/element:latestPublished from the hub, pulled on the first start and kept for the ones after it.

amd64 onlyOne architecture is published, so pick a machine that matches it.

What it asks for

What it wants,and what it needs

The definition asks for 2 cores and 4 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

2 cores · 4 GBAsks forwhat the definition writes down

2 cores · 2 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

Element asks for 2 cores and 4 GB. Cheapest first.

E2 Medium

$0.042/ hour2 cores · 4 GBStart this machine

T3 Medium

$0.052/ hour2 cores · 4 GBStart this machine

B2s

$0.052/ hour2 cores · 4 GBStart this machine

Run Element on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start Element Browse workflows