Overview

What Tractorbeam is, and the concepts these docs build on.

Tractorbeam gives agents and Apps one place to read and change a business’s data. You describe that data and the work around it in TypeScript, and Tractorbeam keeps it, versions it, and decides who can reach it.

How the parts fit

• A Workspace holds a customer’s data, sign-in, and access rules, and records every change as a Commit on a Branch.
• A Project is the TypeScript source of a Workspace’s definitions. Applying it to a Branch commits the definitions that changed.
• Resources are the named parts a Project defines, such as Objects, Tables, and Markings.
• The Ontology is the set of Resources that agents and Apps use: Objects, and the Queries, Mutations, and Actions that read and change them.
• Apps, web Apps and MCP Servers, are how people and agents reach the Ontology.
• Connectors let Actions reach outside systems without holding their credentials.

Where these docs are going

The Concepts tab defines each term these docs use. Guides arrive as each workflow becomes available end to end, and the API Reference documents the HTTP API.