Frontier Investigation Agents for enterprise

Agents your risk teamcan sign off on.

Agents investigate incidents, code changes and cloud cost. Your policy decides what they may change.

Agents reach your systems only through connections you add, with the permissions you grant. Writes go through Approvals, and user, agent and approval actions land in one audit log. Start read-only on your own past incidents, and widen what agents may do only when the record supports it.

  • Guardrails
  • Frontier models
  • Your model keys
  • Sandbox
  • Infrastructure
  • Observability
  • Code, CI/CD
  • ITSM, tickets
Your systemsCloudThinkerScoped access, read-only to start
Every write is checked.
Reads run. Writes go through Approvals, and a built-in blocked list never runs.
Least privilege, per connection.
Agents use only the connections you add, with the permissions you grant.
On the record.
User, agent and approval actions land in one audit log, exported as CSV.

Evidence

Judge agents on results.Then on your own incidents.

100%
Incidents resolved end to end on the public SREGym-Lite leaderboard, on GPT-6 Astra, checked October 11, 2026
736k
Tokens per run on GPT-6 Astra, the fewest of any agent at 100% on that model
~97%
Review precision on live merge requests at FPT Cloud
SOC 2
Type II report on the Security criteria. ISO/IEC 42001 audit in progress
Read the FPT Cloud case study

Governance

Nine controls, in the docs.Check each one before the first connection.

Every control below is described in our public docs, so your risk team can read exactly how it works.

Scoped connections
Agents reach your systems only through connections a workspace Admin adds, with the credentials and permissions you grant.
Read-only to start
Reads always run. A read-only credential can't write, and each connection has its own Allow writes switch.
Short-lived cloud credentials
AWS connections assume an IAM role through STS, so no long-lived key can leak. Stored secrets are encrypted at rest.
Always blocked
A built-in list of calls never runs, such as stopping CloudTrail logging or deleting kube-system. Nobody can override it.
Approvals
Writes go through Approvals. You decide what runs on its own and what waits for approval, per workspace and per run type.
Two-person rule
Turn it on and nobody approves their own run. Viewers can never approve.
Data masking
Secrets, emails, phone and card numbers are replaced with placeholders before the model sees them. Lock the rules for every workspace.
Audit log
One timeline of user, agent and system actions across every workspace, kept 90 days and exported as CSV.
Isolated workspaces
Each workspace keeps its own connections, credentials, agents and approvals. Commands run in CloudThinker's Sandbox.
Read the security and trust docs

Approvals

Every write passes four checks.The first one that answers decides.

  1. 01

    Always blocked

    A built-in list of calls that never run. No Rule and no person can change it.

    For example

    Stopping CloudTrail logging, closing an AWS account, deleting kube-system

  2. 02

    Rules

    Allow, ask first or deny a named kind of write. Rule enforcement is in preview, and we turn it on per workspace.

    For example

    Ask first on database deletes, deny IAM policy changes

  3. 03

    Approval mode

    You decide what runs on its own and what waits for approval, per workspace and per run type.

    For example

    Production waits for a person on every write, while staging restarts a pod on its own

  4. 04

    Approver

    A named person approves or declines. Viewers never can, and the two-person rule stops self-approval.

    For example

    Default approvers for most asks, a DBA group for database deletes

Reads always run. Each decision, by a person or by AI judgment, is recorded in the audit log.

Deployment and data

Hosted by default.Private deployments in early access.

CloudThinker Cloud
The hosted service, with nothing to install. With Environments (beta), file and shell work runs on a machine you control.
Early access
Dedicated
A single-tenant instance hosted by CloudThinker, in a region you choose.
Early access
Self-hosted
Inside your own cloud account or data center, with reference architectures for AWS, Azure, GCP and FPT Cloud.
Early access
Air-gapped
Self-hosted and offline, for environments where data can't leave your perimeter.
Masked before the model
Secrets and protected identifiers in tool output are replaced with placeholders before the model or the screen sees them.
Your own model account
With BYOK, model calls run through your own AWS Bedrock, Anthropic or FPT Cloud account. If your key fails, calls fall back to CloudThinker's models.
SSO, SCIM and roles
SAML or OIDC sign-in, SCIM group sync into workspaces, and Owner, Admin, Developer and Viewer roles.

Regulated industries

Fits the controls you already run.No parallel regime.

Change management
Approval decisions and agent writes sit in the audit log next to your people's actions, ready to export for change records.
Model risk
Replay your own incidents and score each verdict. Resolve tracks root-cause accuracy and false-positive rate from your team's marks.
Third-party risk
Our SOC 2 Type II report, public security docs and questionnaire answers, ready for your vendor review.
Data residency
Dedicated deployments run in a region you choose, and self-hosted ones stay in your perimeter. Both are in early access.

Frameworks we map these controls to, on request

  • EU DORA
  • EU AI Act
  • NIST AI RMF
  • ISO/IEC 42001
  • Vietnam PDPL
  • SBV Circular 09
  • MAS TRM

The first 90 days

Start on your own history.Delegate only what the record supports.

  1. First month

    Replay

    Establish fit.

    Agents replay 30 to 50 resolved incidents, read-only, without the postmortem. Your responders score every verdict.

    Exit criteria

    Measured precision and time to root cause on your own history.

  2. Second month

    Shadow

    Prove value live.

    Agents investigate live issues read-only for selected teams. Responders compare.

    Exit criteria

    An agent verdict is ready before human triage on most issues.

  3. Third month

    Operate

    Begin delegation.

    Agents start fixing two or three kinds of issue, each fix approved by a named person. Security and cost scopes are added, with weekly reporting.

    Exit criteria

    Scorecard movement on at least two outcomes. Zero unsafe actions.

FAQ

What enterprise teams ask first

Replay last quarter's incidents. Judge the verdicts yourself.

Read-only, with least privilege, compared against your own postmortems.