Security & Compliance

SOC 2 Type II audited test automation, built for security reviews

Your tests touch credentials, test data and production-like systems. Robonito keeps that work governed, logged and audit-ready, and runs in the cloud, in a private cloud, on-premise or hybrid.

SOC 2 Type II badge

SOC 2 Type II audited

Controls tested by an independent auditor over an observation period. Report shared under NDA.

Isometric illustration of a Robonito AI agent running tests inside a walled secure platform, with a SOC 2 Type II shield, an audit log, a secret approval step, a role-based access gate and encrypted links to cloud, private cloud, on-premise and hybrid deployments
  • SOC 2 Type II

    Independently audited controls

  • Encrypted in transit

    Between you and the platform

  • Role-based access

    Least privilege by default

  • 4 deployment models

    Cloud, private, on-prem, hybrid

01Why it matters

Test automation is part of your attack surface

A testing platform holds the keys to your environments. Without strong controls, automation becomes an unmonitored path into your systems and a gap in your compliance story.

Credentials and environments

Automated tests log in, call APIs and reach staging systems. Who can use those credentials, and where, has to be controlled.

Sensitive test data

Test runs often touch production-like records. That data needs the same protection and access rules as the systems it came from.

Unsupervised execution

AI agents that act without boundaries become an attack surface. Every automated action should run inside a scope a person defined.

Proof for auditors

When an auditor asks what was tested, by whom and with what result, the answer should be a log, not a reconstruction.

02SOC 2 Type II

Audited over time, not just on paper

A SOC 2 Type II report shows that an independent auditor tested our controls and found them operating over an observation period. For your team, that means less vendor risk and a faster security review.

  • Reduce third-party vendor risk
  • Shorten security and procurement reviews
  • Meet enterprise and regulatory expectations

What the audit covers

01

Secure operations

How the platform is run, maintained and protected day to day.

02

Access governance

Who can reach systems and customer data, and how that access is granted and reviewed.

03

Monitoring and incident response

How issues are detected, escalated and resolved.

04

Change management

How changes to the platform are reviewed, approved and recorded.

03Platform controls

Layered security at the platform and execution level

Controls apply to the people using Robonito and to every automated run, so tests stay safe and predictable.

Role-based access control

Give each person only the projects, environments and actions their role needs.

  • RBAC
  • Least privilege

Secure authentication

Authentication and authorization protect platform access at every layer, for people and for automation.

  • AuthN
  • AuthZ

Encryption in transit

Data moving between your team, your test runs and the platform is encrypted on the wire.

  • Encrypted
  • In transit

Environment-level execution controls

Decide which environments tests may run against, so automation stays predictable and contained.

  • Environments
  • Boundaries

Human approval for secrets

Robonito's AI agent pauses and asks a person before it saves a secret, such as a password, during a run.

  • Approval
  • Secrets

Execution and access logs

Every run and every access is recorded, so you can trace what happened and who triggered it.

  • Traceability
  • Logs
Isometric illustration of Robonito AI agents working inside a person-defined scope with rules, pausing for a person to approve a secret, with every step streamed to a visibility screen

04Agentic AI governance

AI agents that work inside your rules

Robonito's agents speed up testing without running free. They act within boundaries your team sets, and they stop to ask before anything sensitive.

  • People define the scope each agent may work in
  • Deterministic execution rules, not open-ended autonomy
  • Controlled permissions for every AI agent
  • Approval before sensitive actions, such as saving secrets
  • Full visibility into every step and outcome
Isometric illustration of an execution history of test runs with pass and fail evidence, an access log, separated author, approver and runner roles, and an auditor reviewing them

05Audit-ready

Visibility, not black boxes

Security and compliance teams can review what ran, who ran it and what happened, without asking engineering to rebuild the story.

Execution traceability
A history of every test run, with steps, timing and results.
Clear outcomes
Unambiguous pass and fail results with the evidence behind them.
Access logging
A record of who accessed what, and when.
Role separation
Distinct responsibilities for authoring, approving and running tests.

06Deployment

Run Robonito where your policies require

Choose the model that keeps control of data residency and infrastructure where your security team wants it.

Cloud

Fully managed by Robonito, with the fastest setup and nothing to operate.

Best for: Teams that want to start quickly

Private cloud

A dedicated, isolated deployment for stronger separation and control.

Best for: Organizations that need isolation

On-premise

Self-hosted inside your own infrastructure and network.

Best for: Regulated industries and strict data residency

Hybrid

A mix of cloud and on-premise environments, matched to your policies.

Best for: Mixed estates and phased migrations

07Security review

A vendor review that doesn't stall your rollout

  1. 1

    Request the documentation

    We share the SOC 2 Type II report under NDA, along with details of our security controls.

  2. 2

    Review with our team

    Your security and compliance teams walk through architecture, access and data handling with ours, and we work through your vendor questionnaire.

  3. 3

    Pilot in your chosen model

    Run a proof of concept in the deployment model that meets your policies, on your own applications.

08FAQ

Security questions, answered

Is Robonito SOC 2 compliant?

Yes. Robonito has a SOC 2 Type II report, which means an independent auditor tested how our security controls operated over a period of time, not just how they were designed. You can request the report under NDA.

What is the difference between SOC 2 Type I and Type II?

A Type I report checks that controls are designed correctly at a single point in time. A Type II report tests whether those controls actually worked over an observation period, which gives your vendor review stronger evidence.

How do I get Robonito's SOC 2 report?

Request it from this page. Our team shares the report under NDA and can join a call with your security and compliance teams to answer follow-up questions.

What makes Robonito a secure test automation platform?

Robonito combines role-based access control, secure authentication, encryption in transit, environment-level execution controls and full execution and access logs, all covered by SOC 2 Type II audited processes.

How does Robonito keep agentic AI testing under control?

AI agents in Robonito run inside scopes and permissions people define, follow deterministic execution rules, and pause for human approval before sensitive actions such as saving a secret. Every step is logged and reviewable.

Can Robonito run on-premise?

Yes. Robonito is available as a managed cloud service, a private cloud deployment, on-premise inside your own network, or a hybrid of cloud and on-premise environments.

Bring your security team. We'll bring the evidence.

Get the SOC 2 Type II report and a walkthrough of how Robonito handles access, data and AI agents in your environment.

  • SOC 2 Type II
  • Report under NDA
  • Cloud, private, on-prem or hybrid