Skip to main content

Architecture and data flow

Jaah has four parts: the control plane Jaah runs, the nodes your tasks run on, the model provider that answers the AI agent, and the forge that hosts your code (GitHub, GitLab, Bitbucket or Azure DevOps). This page says where each runs, what it stores, in which region, and how data moves between them. It's written so you can answer a security questionnaire from it.

For the controls behind it — encryption, access, backups, logging and testing — see Jaah's security page. Live availability is on the status page.

Control plane​

Runs where. On Amazon Web Services (AWS), in Jaah's own account, in the United States (the AWS us-east-1 region). It's the console you open in the browser, the Jaah API behind it, and the database that holds your organization.

Stores what.

  • In its database: your organization's accounts (names, email addresses, roles), groups and settings; projects; tasks with their comments, questions and answers; node and session records; the audit trail; and the secrets you add, such as forge, cloud and model-account credentials.
  • In object storage: agent session transcripts, the files tasks produce (artifacts) and the files people attach to tasks.

Which region. The control-plane region, unless an org admin picks another data region under Data residency in Settings (when your plan includes it). Which data that setting moves, and which always stays in the control-plane region, is stated on the security page. Backups of the database and file storage are copied daily to a second region in the United States.

How it's encrypted. The database, file storage and object storage are encrypted at rest. Credentials get a second layer inside Jaah, with AES-256-GCM. Each secret field, such as a password, token or key, is sealed in your browser before it leaves the page, so the Jaah API never receives it in plain text. Its key can only be unwrapped through AWS's managed key service, so a copy of the database alone can't reveal it.

What crosses the network. Your browser reaches the console and the Jaah API over HTTPS, TLS 1.2 or later. The control plane reaches its database over verified TLS. It also sends some content to AI model providers itself, for Jaah's own features, such as the Help assistant, task titles and tags, and summaries and reviews of finished tasks. Which provider handles each, and where, is on the subprocessors page.

Nodes​

Runs where. A node is a machine your tasks run on (see How nodes work). It runs in one of three places, chosen when you add it:

KindWhere it runsRegion
Jaah-hosted (a Shared or Dedicated node)A machine in Jaah's AWS account.Your organization's data region.
Launch in your cloudA machine in your own AWS, Google Cloud or Azure account.The region of the cloud connection you launch it through.
Your machineA computer or server you run yourself.Wherever that machine is.

Stores what. Working copies of your projects (worktrees, see How worktrees work), the runners' working files, a model account's subscription sign-in on that node, and each session transcript until it's uploaded. A node fetches the credentials a run needs from the control plane when the run needs them. Shared folders your nodes mount (NodeLink) live in the cloud account and region of the connection they were created through.

What crosses the network. A node always connects out to the control plane; the control plane never opens a connection into a node. A node joins its own private network for its environment, and its control-plane connection runs over that network with TLS on top. The node signs in with its own token, issued for that node alone. Over this link the node reports its status, worktrees and runners, and receives work. Session transcripts are uploaded straight to object storage over HTTPS, after known secret patterns are removed on the node. For some kinds of agent, the session's events are also sent to the control plane as they happen, so the console can show the run live. The node's own service logs go to the control plane over the same link, with known secret patterns removed first. Opening a terminal on a node in the console relays it through the control plane over the same kind of connection.

How it's encrypted. In transit, as above. At rest, a node's disk is that machine's own: on Your machine and Launch in your cloud, your settings and your provider's apply.

Model provider​

Runs where. Outside Jaah, at the AI provider of the model account the run uses. A Jaah AI account runs on Amazon Bedrock in AWS, in the United States.

Stores what. Jaah sends the provider what the agent works on: task text, source code it reads and the output of the tools it runs. What the provider keeps, and for how long, is set by your agreement with it, or by Jaah's for a Jaah AI account.

What crosses the network. For a task run, the agent on the node calls the provider directly over HTTPS; the prompts and code don't pass through the control plane. Jaah's own features call providers from the control plane (see Control plane). A subscription account uses that node's sign-in; an API-key account uses a key the node fetches from the control plane for the run.

Which region. The provider's. Each provider Jaah uses, and where it processes data, is on the subprocessors page.

Forge​

Runs where. At your forge: GitHub, GitLab, Bitbucket or Azure DevOps, hosted or your own server. You contract with it directly; it isn't a Jaah subprocessor.

Stores what. Your repositories, branches and pull requests stay at the forge. Jaah keeps the forge credential you connected (encrypted, as above) and each project's repository address. Outside the nodes, code reaches the control plane only where it appears in a task, a transcript or an artifact.

What crosses the network. The node clones, fetches and pushes over HTTPS straight to the forge, with a credential the control plane serves for that run; the node's forge tool never sends that credential to any other host. The control plane calls the forge's API over HTTPS to connect your account, check what it may access, create and set up a new repository when you ask it to, and read CI runs and a project's docs for the console. The forge can also send events to Jaah over HTTPS, through a webhook you set up for an automation.

Which region. The forge's own.

Summary for a questionnaire​

PartRuns whereStoresRegionAt restIn transit
Control planeJaah's AWS accountAccounts, tasks, settings, audit trail, credentials; transcripts, artifacts, attachmentsUnited States; your data region where the security page says soEncrypted; credentials also sealed with AES-256-GCMHTTPS, TLS 1.2 or later
NodeJaah's AWS, your cloud, or your machineWorktrees, sign-ins, transcripts until uploadedData region, your connection's region, or your machine's locationThe machine's own disk settingsPrivate network plus TLS to the control plane; HTTPS to storage, provider and forge
Model providerThe provider's servicePrompts: task text, code, tool outputThe provider's, per the subprocessors pageThe provider'sHTTPS, from the node; from the control plane for Jaah's own features
ForgeYour forgeYour codeThe forge'sThe forge'sHTTPS, from the node and the control plane; webhooks to the control plane
  • Settings — where an org admin picks the data region and sets how long data is kept.
  • Sessions — the agent sessions and transcripts this page refers to.
  • How credentials work — the secrets Jaah stores and who can use them.