Skip to main content
A company’s Archetype is one host that is only that company’s: its members, roles, conversations, work and agent. People keep their own app and agent on their computers and join the company’s host from there. Archetype for Teams has the short version; this page goes further.

Hosted by us

Your company gets its own host at <company>.archetype.ing, kept and updated for you.
  • Make it. Sign in to the console with Google and name your company. The name becomes its address. You are its first admin.
  • Apart from other companies. Each company has its own host, its own database and its own runners, where the agent’s commands run. Nothing is shared but the machines underneath.
  • Models are yours. Admins sign in to ChatGPT, connect Claude, or give API keys in the company’s Manage. We sell the host and its compute, not tokens.
  • Slack connects through archetype.ing, with no token to keep.

Plans

  • Each extra seat is $12 a month, on any plan.
  • A seat is a member who signs in to the company’s host. People who only talk to the agent in Slack or another channel are not seats.
  • “At work at once” is how many conversations can run at the same moment, each in its own runner. Nothing is metered.
  • 14 days of Team, free, with no card. We write three days before it ends; pick a plan in the console to go on.
  • For now, payment is by invoice: write to help@archetype.ing.
  • After a missed payment the host keeps running for 7 days, then stops. Removing a company keeps an export of it for 30 days.
Prices in other currencies are on the pricing page.

On your own server

Running the company’s host yourself is free, with everything the hosted plans have. The ready setup runs three containers with Docker Compose: the host, Postgres and Caddy (HTTPS). You need a server with ports 80 and 443 open, a domain pointing at it, and a Google OAuth client (a Web application, redirect address https://<your domain>/api/auth/callback).
1

Fill in the settings

In deploy/company of the Archetype repository, copy env.example to .env and set DOMAIN, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, ADMINS (the first admins’ emails), POSTGRES_PASSWORD and ARCHETYPE_HOST_KEY.
2

Start it

The first start writes the company’s setup and prints the sign-in’s redirect address: check it matches the OAuth client’s.
3

Sign in

Open your domain and sign in with Google. In Manage, add a model’s key, name the company, invite people, and connect where the work is kept.
Elsewhere (Kubernetes, behind your own load balancer) it is the same two steps: archetype-server corp init writes the setup, then archetype-server daemon --cwd DIR --listen --port 8787 serves it behind HTTPS. GET /healthz and GET /readyz answer without sign-in.
In this setup the agent’s commands would run in the host’s own container, beside its secrets, so they do not run at all, even for admins, until you set a separate place for them (a Docker container, a pod per session, or a runner) with environment in the user config.
Keep the host key apart from your database backups: without it, the sign-ins and keys sealed in the database cannot be read.

Members

Signing in is joining, and only people the company lets in become members.
  • Invite an email, of any domain, with a role. It lets that person in at their first sign-in. Copy how to join gives them the company’s join link.
  • Invite a whole domain (@example.com) to let in anyone whose Google Workspace manages that domain, as one role.
  • Someone who signs in uninvited leaves a request. Admins are told once a day per person, and Let in or Turn down each.
  • A removed member stays out unless invited again.
Members join from the app: sidebar → Join a team…, then the company’s name or address.

Roles

Every company has admin, who can do everything and manages members and roles, and member. Admins make other roles from permissions in Manage → Roles: Run commands and Change files reach the whole host and everyone’s workspace: give them as you would admin. The built-in member role starts with their conversations, their automations, Projects, Discussions, Knowledge and Claim expenses.

The company’s plugins

Projects, Knowledge, Discuss and Finance come with the company’s host, on by default. In the company’s Manage → Plugins, an admin turns a plugin on or off and chooses which roles see its page, act on it and get its tools; with none chosen, every role has all three. Meals can be turned on the same way. A company’s own private plugin needs an admin to accept that it runs with the host’s reach. A member’s changes through a plugin, its tools’ calls in conversations, and changes to the plugins are kept in the company’s audit log. See Team plugins. Company accounts (Linear, Notion, Google…) are connected once by an admin in Manage → Connections → Company accounts, for every member’s agent, under the company’s rules.