Citizen developers ship software you can’t see. Valet puts it behind your walls.

  1. AI-built tools hold company data and pasted credentials, and they run on laptops.
  2. Someone still has to govern, ship, run, and secure what citizen developers build.
  3. Valet does that work inside your cloud, so your platform team has one system to operate.

Valet for CISOs

Get the forwardable evaluation package

Govern. Ship. Run. Secure.

  1. Enforcement the model cannot skip

    Policies run on the release, so the agent can’t skip them. A failed release is stopped and the previous one keeps running.

  2. You hold the keys and control the access

    Valet runs in your AWS account. You hold the credentials, you decide who has access, and no telemetry leaves.

  3. Every app and agent runs in its own VM

    Each one runs without cloud credentials and can’t reach your private network.

  4. Connector credentials never reach an agent or a laptop

    Agents reach your systems through connectors. The proxy adds the credential on the way out, so the agent never holds it.

  5. Every change is on the record

    Valet records every commit, policy result, and change to access, and streams it to your SIEM.

> publish the renewals tracker

no-secrets blocked

high source/key.pem:1 Possible private key

high source/settings.js:1 Possible GitHub token

high source/settings.js:4 Possible API key

Fix: remove it from the source and rotate it

✕ Nothing was deployed · the last release is still live

Your AWS account · behind your VPN

  • Valet platform
  • Your identity provider
  • Your keys
  • Your models
  • ✕ credentials
  • ✕ telemetry
  • ✓ access you control
Valetthe company, outside

probe app · asked to break out

its own VM

  • Read cloud credentialsnone present
  • Reach the metadata serviceunreachable
  • Call a private addressblocked
  • Open an app without signing in401

renewals-tracker · connectors

4 connected

  • Salesforceread · opportunities
  • HubSpotread · contacts
  • Slackpost · #finance-ops
  • BigQueryread · finance dataset

Keys kept in your account

acme · audit trail

today

  • 09:14priya@acme set renewals-tracker access to finance-ops
  • 11:02dana@acme release blocked: secret in sourceblocked
  • 13:40jo@acme added the Salesforce connector
  • 16:05sam@acme tried to make vendor-risk publicblocked

Security in layers, and you hold every key

You hold the credentials and control who has access, and no telemetry leaves your account.

Air-gapped in your cloud

Every layer enforced

On the record, and kept running

valet.acme.internal/apps/access-review-tracker

Access review tracker

Running in your VPC
  • Mon 09:13Priya shipped v1 from Claude Codea3f9c1e
  • Mon 09:14Access limited to people who sign in through Okta
  • Mon 09:15Snowflake connected, credential kept in your account
  • Tue 11:02Release blocked, secret found in source
  • Tue 11:02Audit event sent to your SIEM
  • Tue 16:27App’s call to 10.0.4.12 blocked: no route to your network
  • Wed 03:12Vulnerable package flagged; Sam upgraded it, v127be2d04
  • Thu 09:00Access review: every grant here was made by your admins
  • Thu 14:40App crashed, restarted in 6s
  • Fri 10:21Dana added a CSV export, v13c41a88f

You hold the keys.

Get the forwardable evaluation package

Or have your agent try Valet Cloud free