User and source control
Engineering task, repository context, ticket metadata, branch target, and review owner.
Architecture
The platform separates requests, policy, runtime, tools, data, hosting, and observability so agent work can be constrained, inspected, and operated.
Engineering task, repository context, ticket metadata, branch target, and review owner.
Role, workspace template, tool allowlist, network boundary, approval requirements, and cost limits.
Bounded workspace where the agent can read, edit, execute, test, inspect, and prepare evidence.
Controlled access to shell, browser, documentation, workflow engines, APIs, databases, and internal services.
Application runtimes, preview services, scheduled jobs, vector stores, media services, and supporting infrastructure.
Persistent volumes, cache, artefacts, logs, screenshots, test output, session history, and deployment records.
Preview routing, TLS, hosted applications, API endpoints, rollback targets, and environment promotion.
Run telemetry, service logs, health checks, alerts, incident review notes, and executive reporting.
Deployment models
Dedicated hosted workspace and deployment capacity operated by GTA for controlled enterprise pilots and managed services.
Private connectivity to customer systems where agents need bounded access to internal services or repositories.
For organisations that require stronger local control, a dedicated installation path can be designed around their operating constraints.