Para equipas de engenharia

A configuração da sua equipa, num só sítio.

Every developer rebuilds the same thing: the staging SSH host, the seed command, the read-only database connection. The Team plan lets one person set it up and everybody inherit it, without a wiki page and without sharing a single password.

What actually slows a team down

It is rarely the AI. It is the twenty minutes each new teammate spends re-adding the same dev commands, the connection string somebody pastes into a private message, and the prompt that works which lives on one laptop. Multiply that by every project and every joiner.

Git carries what belongs in the repository. It does not carry your connections, your saved commands, your accounts or your billing. That is the gap the Team plan closes.

What a team gets

Pro for every seat

Each member holds the full Pro tier with no card of their own and nothing to expense. Invite by email, they claim their seat in one click.

One invoice

A single bill in the company name, with its address and tax number, instead of one expense claim per developer. Seats are billed as a quantity, so adding one mid-cycle is prorated.

Shared library

Dev commands, SSH hosts, database connections, prompts and skills published once and inherited by the whole team, per project.

Seat administration

See who holds a seat and who has never used theirs, and revoke access the day somebody leaves. The gap between seats paid and seats used is visible before the renewal, not after.

The shared library, in detail

Anything you set up at project level can be published to your team in one action. A teammate imports it into their own project and it becomes theirs: editing their copy never touches yours.

Dev commands

The seed script, the migration runner, the local stack. Published once, run by everybody with the same arguments.

SSH hosts

Host, port and user for staging, production or a jump box. The key stays on each machine.

Database connections

Engine, host, port, database and user, including connections reached through an SSH tunnel. The password is never part of it.

Prompts

The review prompt, the release checklist, the incident triage brief. The wording that works stops living on one laptop.

Skills

The procedures your agents follow. Publish one and every teammate's agents can run it the same way.

Nunca se partilha uma palavra-passe

This is a design decision, not a setting you can get wrong. Credentials are stripped from every published resource before it is stored: passwords, passphrases, private keys and tokens simply cannot enter the library. A connection carries its host and its user, and each member authenticates with their own credential on first use, kept in their machine's vault. A password shared through a product is a password nobody can revoke.

How it works

  1. 1

    Buy the seats you need

    From the app, in Settings then Account. Pick a seat count and pay once for the whole team.

  2. 2

    Invite your team by email

    Each member claims their seat in one click and immediately holds the full Pro tier, with nothing to pay.

  3. 3

    Publish what everybody needs

    Share a command, an SSH host or a database connection from the open project. Your teammates see it in their team library and import it.

What never leaves your machines

AgentsRoom stays a local-first desktop app on the Team plan. Nothing about how it is billed changes where the work happens.

Para se aprofundar

Bring your team on board

€12.99/month per seat and month, from 3 seats. One payer, one invoice, and every member on the full Pro tier.