Skip to main content
t.Computer infrastructure
DocsSign inCreate account
Provider-neutral computer infrastructure

Give every agent the right computer.

Route work across browsers, desktops, sandboxes, and computer-use agents. Observe one normalized timeline. Take over when human judgment matters.

Create account Open console

Developer preview: account sign-in activates a Project and the secure hosted console automatically.

Incoming taskReview release candidatesurface: auto · trust: verified
Policy matchedLive
t.computer router

Capability · trust · region · cost

Browser
Computer
Sandbox
Observeevent 024Human takeover ready

One control plane

Route. Observe. Take over.

Keep product logic focused on the job to be done. t.computer owns runtime selection, normalized state, and the boundary between automation and people.

01

Route

Describe the capability, surface, region, budget, and trust level. The control plane selects an eligible runtime without coupling your product to one provider.

02

Observe

Follow tasks, ordered events, screenshots, artifacts, and usage through one normalized API—even when the underlying runtime changes.

03

Take over

Pause automation, review an approval, or enter a live computer when a person should make the next decision.

Surfaces

One request. The right environment.

Ask for the surface and capabilities you need. Keep the provider an implementation detail.

Browser

Navigation, screenshots, CDP access, and live-view handoff for web work.

  • Navigate
  • Inspect
  • Handoff

Computer

A graphical desktop with command execution and a clear human takeover path.

  • Desktop
  • Execute
  • Take over

Sandbox

Isolated command execution for code, builds, automation, and data workflows.

  • Isolate
  • Build
  • Persist
Trust is a routing constraint

Control where work runs—and when it stops.

Compute capability and infrastructure trust are separate decisions. t.computer evaluates both before placement, then keeps the supervision trail available to your application.

  • Trust-aware routing keeps sensitive workloads on eligible infrastructure.
  • Provider and hosted Account credentials stay encrypted or server-only; the browser console uses its exact web session.
  • Approvals, ordered events, and durable artifacts preserve an auditable trail.
Routing policyEligible
Surface
browser
Minimum trust
verified
Region
us-west
Approval mode
required

Policy boundary preservedProvider-specific credentials remain server-side.

Developer API

Build the workflow once.

Create tasks through versioned REST resources, recover state from ordered events, and keep runtime-specific details behind a stable contract.

Read the quickstart Browse API docs
task.create
curl https://api.t.computer/v1/tasks \
  --request POST \
  --header "Authorization: Bearer $T_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"task":"Check the release candidate","agent":"auto"}'
Start with one task

Your product asks. t.computer routes.

Open the developer console today, or start with the API documentation.

ConsoleDocs