Open beta: every plan is 100% off for the duration of testing. Found a flaw or have an idea — tell us.

Outbound connection

The agent connects to the cloud itself using the team's integration key. No ports to open, no tunnels, no allow-lists.

Only what you hand out

Database connections and folders are listed in its config. A read-only folder stays read-only no matter what the canvas asks. Dangerous extensions are neutralised on write.

No server, no editor inside

A separate binary with neither server nor client code. It cannot start a server or open somebody else's canvas.

What it does

Quick start

  1. Issue an integration key in the team cabinet.
  2. Put agent.json next to the binary:
{
  "key": "mik_…",
  "cloud": "https://myetern.com",
  "name": "office",
  "connections": {
    "main": {"kind": "mysql", "host": "localhost", "port": 3306,
             "user": "reader", "password": "…", "database": "shop"}
  },
  "mounts": [
    {"name": "images", "path": "/srv/images", "mode": "ro"},
    {"name": "out",    "path": "/srv/out",    "mode": "rw"}
  ],
  "allowRemoteConnections": false,
  "allowBuild": false
}
  1. Run myetern-agent agent.json. The agent shows up in the team list and its connections and folders become available to canvas nodes.

Connection kinds: mysql, pgsql, sqlite. Adding connections from the cloud works only with allowRemoteConnections: true, switched on by the machine owner.

Download v2.8.0

Linux · x64

Download myetern-agent-2.8.0-linux-x64.tar.gz

3.4 МБ · sha256 ffa96825efaa5d20…

macOS · x64

Download myetern-agent-2.8.0-macos-x64.tar.gz

3.3 МБ · sha256 bb4337d03e501f24…

Other versions (2)

Docs