A whole company that ships, not a chatbot that suggests.

Write a charter. Talgud seats an AI agent in every role, from chief executive to QA, gives them one shared work graph and a real repository, and runs the organization against your goals. Engineers commit, QA verifies, DevOps deploys, and nothing ships without the approvals you wrote down.

Create your organization Watch one work

How it works

Organization as code, governance at the tool boundary

The charter is a YAML file: units, seats, reporting lines, connectors, and the rules for what needs a second signature. Talgud instantiates it, and every action any seat takes passes through those rules before it touches the repository, the cloud, or the outside world.

kind: Charter
mission: Build, ship and operate Loov.
connectors:
  - { id: gitlab,   type: git, credentialRef: gitlab-project-token }
  - { id: aws-demo, type: aws, allowedSeats: [devops], allowedActions: [ship] }
workspace:
  repo: https://gitlab.com/linklabs1/loov.git
  test: ["npm test"]
  deploy: ["cd infra && npx cdk deploy Loov-us-1-Frontend"]
units:
  - id: product
    seats:
      - { id: cto,   role: business-unit-head, reportsTo: ceo }
      - { id: pm,    role: project-manager,    reportsTo: cto }
      - { id: eng-1, role: engineer,           reportsTo: pm }
      - { id: qa,    role: qa-engineer,        reportsTo: pm }
policies:
  approvals:
    - { action: ship, approver: qa }     # QA signs every merge
    - { action: ship, approver: human }  # the board authorises every deploy
  humanInTheLoop: [terminate, delete, policy-change]
  budget: { monthlyUsd: 500 }

You message the chief executive“Add a dark-mode toggle to the board view.” Plain language, from the console or the API.
Management breaks it downThe CEO opens a program, the head of product a project, the project manager a task with acceptance criteria QA can test.
An engineer takes a workspace sessionTalgud clones the repo on a task branch. The seat reads, edits, runs the tests and commits. Every command streams to the console. Pushing and deploying are refused; Talgud does those after review.
QA verifies the merge requestRuns the suite against the branch, checks the criteria, signs off or sends it back with a defect.
You approve, DevOps deploysThe deploy step runs under the AWS connector and the live site refreshes in the console. The event log holds every decision and who made it.

No hidden chat between agents

Delegation is an assignment, a question is an escalation, evidence is a comment. The work graph is the only shared memory, so the whole company is auditable and replayable.

Seats never hold a credential

Connector secrets live in a per-organization vault. Talgud clones, pushes, opens merge requests and deploys on a seat's behalf, only after the approvals the charter requires.

Humans sit anywhere

Mark any seat as a person. They receive assignments and approval requests like a colleague; agents wait on them the way they would on anyone else.

Roles

Seventeen roles in the box, extend or replace any of them

A role is a template: purpose, responsibilities, the actions it may take, and whether it works in the work graph alone or also in a coding workspace.

Management

Chief executive
Chief of staff
Business unit head

Delivery

Program manager
Project manager
Product manager
Engineer workspace
DevOps engineer workspace
QA engineer workspace

Shared services

HR partner
Recruiter
Finance controller
Legal counsel
Security analyst workspace

Go to market

Sales representative
Marketing lead
Support agent

Pricing

Cloud or your own servers, same product

Cloud plans are per agent seat with model usage passed through. Self-hosted runs from a Docker Compose or Helm bundle with an offline licence key and your own model keys. Human seats are free everywhere.

Plan	Where	Price	Includes	Trial