The app platform enabling
citizen developers
Stop data from leaving and credentials from spreading. Valet runs the tools your business users build inside your cloud, behind your SSO.
Have your agent try it out for free
You didn’t build the apps, but now you have to host & maintain them.
Your business users in finance, ops, and sales are now citizen developers. They build their own tools with AI, with nothing lost in translation. Operating internal tools safely as the changes pile up requires an engineer’s mindset, but citizen developers don’t have time to become engineers. Valet runs the security and ops layer underneath every tool your citizen developers ship: access control, audit logging, and safe changes. What one person builds, the whole company can use, and you never inherit a mess.
With Valet, everyone wins.
Citizen developers follow no standards. Make them follow yours.
Write your security and engineering policies once. Coding agents fetch them while they write, so the code comes out right the first time. Your judgment, in every app your company builds.
> publish this following our guidance
Policies: services-in-go · house-design · no-pii
- app/page.tsx
+ main.go
✓ Published · meets 3 policies
Ship everything, whatever tool built it
New coding tools arrive every week, and each one produces something different. Valet runs every shape: static sites, sites with MCP, apps with Postgres, and cloud agents. When a tool outgrows a page it becomes an app, and nothing migrates.
Static site
Dashboards and reports
Site with MCP
Pages that read live company data
App with Postgres
Tools that keep their own state
Cloud agent
Work that runs on a schedule
A page that outgrows itself becomes an app at the same address. Nothing migrates.
Every change passes through Valet
Valet owns source control and deploys, so every app passes two checkpoints: check-in and deploy. Each could run the checks you choose: secrets, licenses, CVEs, or your own policies.
Checkpoint 1 · on check-in
- secrets
- lint
- licenses
- no-pii
Checkpoint 2 · on deploy
- policy
- CVE scan
- SSO only
- data access
example: a no-pii rule at check-in
- console.log(customer.ssn)
→ returned to the coding agent to fix
Software rots. Build the agents that keep it current.
Valet runs agents alongside your apps, with access to their source and deploy path. A maintainer agent, for example, watches dependencies, proposes upgrades, and explains them in plain language.
maintainer · renewals-tracker
example agent
- next14.1 → 14.2.25CVE
- axios1.6 → 1.7.9security
- chart.js4.3 → 4.4minor
Maintainer: 3 upgrades ready. Checks pass and nothing on screen changed. One fixes a critical CVE. Approve?
Access controls that keep your data secure
User access and app credential management in one place. You decide who can open each app and what each app can touch, with an audit log of everything that happens.
Sign in to view this app
Your directory decides who that is.
One front door for every app
Your own internal app store, hosted under your organization’s domain. Every app has an owner, an address, and a list of who can open it, and every agent can ship to it through our CLI or MCP server.
Your apps look like you.
Write your design system once, and every agent reads it before publishing. A report from ops and a report from finance look like the same company made them.
Easy to share
Every app gets a link that opens behind your company login. Share it with a team, or with one outside person by email, and take it back when you’re done.
q3-board.acme.valet.run
Copy link- Finance teamcan view
- Maya Chenowner
- dana@auditor.comguest · revoke
Hundreds of integrations, built in
Apps read from Salesforce, HubSpot, Slack, and your data warehouse through connectors Valet governs. Valet holds the keys, so no app ever carries one.
renewals-tracker · connectors
4 connected
- Salesforceread · opportunities
- HubSpotread · contacts
- Slackpost · #finance-ops
- BigQueryread · finance dataset
Keys held by Valet · the app sees none
Built for enterprises where everyone builds
Security sets the rules once. Every new app follows them.
It runs on your terms
You can see all of it
Nobody on your team maintains it
Renewals tracker
Running in your VPC- Mon 09:13Priya shipped v1 from Claude Codea3f9c1e
- Mon 09:14Access set to Okta group finance-ops
- Mon 09:15Salesforce connected with OAuth, held by Valet
- Tue 11:02Output blocked, patient ID pattern found
- Tue 11:02Event sent to your SIEM
- Wed 03:12Upgraded 4 dependencies, checks passed, v127be2d04
- Thu 14:40Health check failed, restarted in 6s
- Fri 10:21Users keep exporting to CSV. Added export button, v13c41a88f
Valet covers the full lifecycle of the apps your citizen developers build.
In your AWS account
Your tools on Valet
- Dashboards
- Apps
- Agents
platform
- Hosting & runtime
- Integrations
- SSO identity & access
- Governance instructions
- Source control
- Databases
- Schedules & triggers
- Observability & audit
- Security updates & reviews
Any coding agent
Claude Code · Cursor · Codex · Replit · Lovable · Grok
FAQ
What is Valet?
Valet is the app platform enabling citizen developers: the business users in your company who build their own tools with AI. We host those apps and run a robust SDLC underneath to keep them reliable, secure, and safe. Each app gets an owner, an address, access control, and safe changes, so what one person builds, the whole company can use.
What should I share on it?
Anything a coworker needs to see. Dashboards, research briefs, postmortems, runbooks, brand guides, internal tools. If it renders in a browser, it can live here. The usual fate of this stuff is one Slack message and then nothing, so six weeks later somebody builds the same thing again. Publishing gives it an address, and makes it part of your dashboard so the next person finds it instead of starting over.
What if it needs to stay current?
It can. What you publish stays connected to the agent that made it, so that agent can refresh it every morning, run a workflow, answer in Slack, or set the page up to serve fresh content directly from the source through an integration.
Do I need a particular agent?
No. Valet works with the tools your team already uses: Claude Code, Codex, Cursor, GitHub Copilot, ChatGPT, and any MCP client. It installs as a skill and an MCP server and adds a layer on top of those tools rather than replacing them. If your tool can run code, the CLI does more. None of it needs an account to get started.
Do I need an account to try it?
No. Share with no account and get a working public URL in seconds. Those apps are removed 36 hours later unless you claim one with a Valet account, which makes the URL permanent.
Who can see what we share?
New apps start private: only people in your org. You can configure Valet to work with your company's identity provider — Okta, Entra ID, Google Workspace, or any SAML or OIDC provider. Or you can set a password, or make an app public to anyone with the link.
We're already building this in-house. Why buy?
Teams that build their own end up with the same parts: SSO in front of every app, a secrets manager, scoped access to company data, isolation from production, and a list of apps with owners. Valet ships all of them today, so your team spends its time helping citizen developers build instead of maintaining a platform.
What does it cost?
Seats are $20 a month, and your first seat is free. Tokens, compute, bandwidth, and storage come out of prepaid credit, and new accounts start with $5 of it. Scale adds custom domains, SSO, and 24x7 support at $30 a seat.
Do end users cost money?
A seat is anyone who is logged in on your team. Public and guest viewers are free.
Does it run in our cloud?
VPC deployments are available. Email support@valet.dev.
Make the safe path the fast path
Try Valet free: