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
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.
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
Checkpoint 2 · on deploy
example: a no-pii rule at check-in
- console.log(customer.ssn)
→ returned to the coding agent to fix
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
Maintainer: 3 upgrades ready. Checks pass and nothing on screen changed. One fixes a critical CVE. Approve?
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.
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.
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.
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 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
Keys held by Valet · the app sees none
Security sets the rules once. Every new app follows them.
Renewals tracker
Running in your VPC 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.
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.
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.
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.
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.
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. 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.
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.
A seat is anyone who is logged in on your team. Public and guest viewers are free.
VPC deployments are available. Email support@valet.dev.
Make the safe path the fast path
Try Valet free: