Install
One command installs 3AM on a Linux server or into a Kubernetes cluster. Sites without internet install from a signed bundle.
One command installs 3AM. Run it on a Linux server as your normal user:
curl -fsSL https://get.3am.si/install | shIt asks where 3AM should run, sets up whatever is missing (with your say-so), downloads 3AM, checks every file's signature and starts it.
| You have | Read |
|---|---|
| A Linux server or VM | Linux |
| A Kubernetes or OpenShift cluster | Kubernetes |
| No internet where 3AM will run | Air-gapped sites |
Add -s -- --trial to the command to start a free trial as part of the install. Before you start, it helps to decide
where the models run.
After it's installed
3AM starts in setup mode. You open the console, create the first owner, and connect your tools. Nothing runs against your systems until a licence or trial is active and you've connected something.
To upgrade later, run the same command again. Your data and settings are kept, and if the new version doesn't start, the old one comes back. Upgrade
Common questions
A shell script that downloads one release of 3AM, checks its size, checksum and signature against what 3am.si says,
and runs the installer inside it. You can read it first: curl -fsSL https://get.3am.si/install | less. To download
without installing, use curl -fsSL https://get.3am.si | sh.
Yes. curl -fsSL https://get.3am.si/k8s | sh goes straight to Kubernetes. For a server, run the downloaded
./install.sh yourself.
3AM runs on Linux only. Use a Linux VM in your cloud or on your hypervisor.
Yes. Each release has a compose/ folder with the same containers and hardening. The installer is easier, and it
handles upgrades for you. See Linux → Compose.
Architecture and security
What runs where, what connects to what, where 3AM keeps its data, and how access, secrets and the audit log are protected.
Linux
Install 3AM on a Linux server or VM with one command. What the installer asks, how to open the console, the options worth knowing, RHEL, and Compose.