contents · For teams

start

For teams

GLAD is multiplayer by design: your whole team and every agent work from one source of truth, and conflicting decisions are caught in real time.

Join your team

Your admin invites you by email. Then:

Open the invite link in the email.
Sign up with that email, or log in if you already have a GLAD account.
Connect GitHub on the same page.

Install as in getting started, then, in your checkout:

terminal

$ glad login .
$ glad arm .

Both find your team’s service through your GLAD account, so there is no address to type. At a terminal, GLAD asks once for your GLAD account’s email and password (Enter skips, and GLAD then uses a service on this laptop alone). If the service uses a self-signed certificate, GLAD checks it against the one the service registered with your team and trusts it for GLAD’s calls there alone.

What your team gets

One record of every decision, shared by every agent and every person on the team.
Conflicts between teammates posted to Slack, each one ready to raise as a Linear issue.
A graph of every decision, open to everyone from their own laptop.
Code that heals itself with Misha: when a decision changes, dependent code is automatically updated or removed in the background, with minimum disruption to your work.

Deployment

Single-tenant: one service per team.

private cloud

Your cloud account

runs on: Your cloud account, private endpoint.
judge: Your model endpoint, or GLAD’s judge if egress is allowed.
egress to us: If you use GLAD’s judge, the prompts and code changes it reviews also go to our external model provider, which never stores them.
seats: True-up for seats added during the term.

on-premise

Your hardware

runs on: Your own hardware, fully offline.
judge: Your own model.
egress to us: None.
seats: Set in your licence.

Your data stays yours

Your team’s graph lives on your own infrastructure, nowhere else. We retain nothing: no code, no decisions, no prompts.

Licensing

Per seat: one seat per person, unlimited agents.
GLAD's judge: $1,000 of it a year for each person on the team who has signed in, renewing on the day the team was made.

Launch in your AWS account

One CloudFormation stack builds your team’s service in your own AWS account: a server running GLAD over https, a fixed address, and a data disk backed up every day. The link always opens the newest GLAD release.

Your team’s own service

opens your AWS console

launch in your AWS account

Set up your team

First, sign up with your work email: your team’s install key is on the page once you have.

Your team is made for one repository, with you as its first admin. Until abloh IDE ships, book a call and we set your team up with you. Once it does, you set it up from inside abloh IDE: Set up a team (from the command palette, the pill's menu or the Team page) makes the team and shows its one-time Team token for the stack below, with a link that opens this stack with the template and repository filled in. Paste the token into the stack yourself; AWS does not take it from a link. Once your service registers, abloh IDE opens the Team page, where you invite each teammate by their email. See Set up a team.

Open the link

Fill in the fields

Address: the name the service answers on, e.g. glad.example.com, on a domain whose DNS you can change.
Repository: the repository’s origin url, exactly as git remote get-url origin prints it.
Admin’s GitHub login: the GitHub login of your team’s first admin.
Install key: the key from your sign-up.
Team token: your team’s one-time token. The service registers itself with your team once it is up, which is how your teammates find it. It works once and runs out 24 hours after it was made.

Set Hosted zone to the id of your Route53 hosted zone only when your address's DNS is already in Route53 in this AWS account: the stack then makes the DNS record itself. Leave it empty otherwise.

Leave Permissions boundary, under Optional, empty unless your AWS account requires one for the roles a stack makes.

Tick that the stack creates IAM resources, and press Create stack.

Add the DNS record

Once the stack is made, its Outputs tab shows DnsRecord, an A record for your address. If you gave a hosted zone it is already made; otherwise add it at your DNS provider: the service waits for it, takes its certificate and starts, and https://glad.example.com/health answers.

Connect Slack

The admin, on their laptop, in a checkout of the repository, logs in to the service by its address and connects Slack.

Bring in every developer

Each teammate opens their invite and runs glad login . and glad arm ., as in join your team.

To launch a known release rather than the newest, put its version in place of latest in the link’s address, e.g. .../0.1.3/launch.yaml.

A service not registered with a team

The team’s first admin logs in to a newly launched service by its address, then connects Slack:

terminal

$ glad login --service https://glad.example.com
$ glad arm --service https://glad.example.com
$ glad slack connect

A service launched with no Team token, or one you run with glad serve, is not known to your team, so everyone names it by its address. Each teammate runs, in their own checkout:

terminal

$ glad login --service https://glad.example.com
$ glad arm --service https://glad.example.com

If this machine does not already trust the service’s certificate (a self-signed one), GLAD shows its fingerprint the first time and asks you to confirm it before trusting it.

The admin adds each teammate first with glad admin team add <github login>.

To register a launched service with your team later, update the stack with a new Team token: it registers itself with no shell.

Bring GLAD to your whole team

or we set up everything for you

book a demo