Glimmer subscription

Install Glimmer on your own server

After you subscribe, we email you a deploy token. This page shows how to set up Glimmer on a server you rent, using that token.

What you need

  • Your deploy token. It is in the email from [email protected] and starts with gdt_. That email is the only copy, so keep it safe.
  • A server with Ubuntu 24.04, rented from a cloud company such as DigitalOcean. We recommend 4 vCPUs and 16 GB of memory. On DigitalOcean, that is the Premium AMD plan s-4vcpu-16gb-amd. The smallest that works is 2 vCPUs and 8 GB. On a smaller server, fewer agents can answer at the same time.
  • A server that supports KVM. Glimmer runs each agent in its own small virtual machine, and that needs KVM. DigitalOcean servers support it. The setup page checks your server and tells you if it does not.
  • A way to log in to the server as root, with SSH.

You pay the cloud company for the server, and your AI company, such as Anthropic or OpenAI, for the AI. Their bills come to you directly.

Set up a plain Ubuntu server

On a plain Ubuntu 24.04 server, you run 5 short sets of commands, then finish in your web browser.

1. Rent the server and open its ports

Create the server with Ubuntu 24.04, at the size above. Write down its public IP address, such as 152.42.189.248.

In the cloud company's firewall settings, let in ports 80 and 443 from anywhere. These are the ports for web pages. Keep port 22 open for your own SSH login. Then log in to the server as root.

2. Add Docker's download source

Glimmer runs on Docker. These commands let the server download Docker from Docker's own site.

Commands to copy

apt-get update apt-get install -y ca-certificates curl install -m 0755 -d /etc/apt/keyrings curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc chmod a+r /etc/apt/keyrings/docker.asc echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu $(. /etc/os-release && echo "$VERSION_CODENAME") stable" > /etc/apt/sources.list.d/docker.list apt-get update

3. Sign in to the Glimmer download site

Glimmer downloads from dist.glimmer.glints.com, and your deploy token is the password. First, install oras, the small program that downloads from it:

Commands to copy

cd /root curl -fsSLO https://github.com/oras-project/oras/releases/download/v1.4.0/oras_1.4.0_linux_amd64.tar.gz tar -xzf oras_1.4.0_linux_amd64.tar.gz -C /usr/local/bin oras oras login dist.glimmer.glints.com -u glimmer

When it asks for a password, paste your deploy token and press Enter. The screen does not show what you paste. It says Login Succeeded when the token works.

4. Download and install Glimmer

These commands find the newest stable Glimmer, download it, and install it. The install also brings Docker and the parts that run the agents' virtual machines. The last command signs this download program out, so your token does not stay in its settings.

Commands to copy

oras pull dist.glimmer.glints.com/channel:stable VERSION=$(python3 -c 'import json; print(json.load(open("channel.json"))["version"].replace("~", "-"))') oras pull dist.glimmer.glints.com/release:$VERSION apt-get install -y ./glimmer_*_amd64.deb oras logout dist.glimmer.glints.com

5. Start the setup page

Command to copy

systemctl enable --now glimmer-setup

The server now shows a setup page on the web. Its address is your server's IP address with dashes in place of dots, then .sslip.io. For the server 152.42.189.248, open:

https://152-42-189-248.sslip.io

The first visit can take a minute, while the server gets its security certificate.

Finish on the setup page

The setup page first checks your server. If the server does not support KVM, the page says what is missing, and you cannot go on. Pick another server size or region, and the page checks again. If the server is smaller than the recommended size, the page says how many agents can answer at the same time. You can still go on.

Paste your deploy token in the box. The page then does these steps and shows each one as it goes:

  1. Checks your token. If the page says the token was not accepted, check that you copied all of it.
  2. Installs the newest Glimmer, if there is a newer one than you installed.
  3. Sets up Glimmer's settings and database.
  4. Starts Glimmer. This took about 4 minutes on our test server. It can take up to 30 minutes.
  5. Opens your Glimmer console, at the same address. You are signed in as the owner.

If a step fails, the page names the step and shows the error. Press Retry, and the setup goes on from that step. Keep the page open while it runs. If you reload it, paste the token again, and the setup goes on from where it stopped.

In your Glimmer console

The console opens on a Get started list. Each item takes you to the page that does the work:

  1. Add a model connection. Paste the key from your AI company's account.
  2. Create an agent.
  3. Connect its chat app, such as Lark, WhatsApp or Microsoft Teams.
  4. Sign in from chat. Send the code the console shows to your agent in your chat app. This makes your chat account the console's admin. After this, you sign in to the console through chat, and the deploy token no longer signs you in.
  5. Updates are on. Glimmer installs each new stable version by itself at night, while your subscription is active.

Before you sign in from chat, you can open the console again at /claim on the same address, such as https://152-42-189-248.sslip.io/claim, and paste the deploy token.

Other cases

If you lose your token, or think someone else has it, reply to the email that sent it, or write to [email protected]. We send a new token to the email address on your subscription. Paste it in your console's Settings, in the Updates section. The old token stops working 7 days later.

If your server sits behind a router and has no public IP address of its own, write the web address that reaches it in /etc/glimmer/setup.env, as GLIMMER_SETUP_HOSTNAME=glimmer.example.com, before step 5. The address must reach the server on ports 80 and 443.

When your subscription ends, Glimmer keeps running on your server, on the version it has. It stops getting updates. Subscribe again on the same payment page to get updates again.

Help from a person costs extra. The subscription includes this guide and the help pages in your console. A Glints engineer can help for a fee, by the block of hours. Write to [email protected].