What is Valet
On this page
People across your company now build their own tools with coding agents such as Claude Code, Codex, and Cursor. Someone in finance builds a spend dashboard, an operations lead builds an intake tracker, and a support manager builds an agent that answers questions in Slack. A sales lead writes down how the team qualifies a deal, so their coding agent does it the same way every time. They aren't software developers and don't want to become one; they build tools to solve their own problems.
Most of those tools live on one person's laptop and stop when it sleeps. They reach company data with a personal password pasted into the code. A useful skill sits in one person's folder, out of reach of every teammate's agent. Nobody else can find the tools, and nobody can tell which ones the business now depends on.
Valet is the home for those tools. You ask your coding agent to publish, and the tool moves off your laptop and into your organization. A skill reaches every teammate's coding agent. An artifact, app, or agent runs at its own address, open only to the people you choose. Your IT and platform teams decide what the tools can connect to and which engineering standards the agents follow while they build.
To try it now, give your coding agent these instructions. It sets up Valet, publishes what you're working on, and replies with the link:
Choose a path
What you publish
Choose the kind that fits the work. Your coding agent can help you decide: skills for repeatable instructions, artifacts for browser-only pages, apps for server code, and agents for work that runs on its own.
- Skills are written instructions a coding agent follows, such as how your team reviews a contract or writes the weekly report. A skill is a Markdown file. Once published, every teammate's coding agent can find it and follow it. Agents you publish can carry it too. See Skills.
- Artifacts are web sites built from files: a report, a dashboard, a prototype, a slide-like narrative. They need no server. See Artifacts.
- Apps are programs that run on a server, written in Node.js, Python, or Go. An app can have its own PostgreSQL database, access to an LLM, and other kinds of resources. See Apps.
- Agents are always-on assistants that keep working after your session ends. They answer in Slack, run on a schedule, receive webhooks, and serve other tools over MCP. See Agents.
Each one belongs to your organization, whoever built it, and Valet keeps every version.
What they use
- Connectors reach the services your company already uses, such as Google Workspace, Slack, or your own MCP server. An administrator adds a connector once, and tools use it without ever holding the credential. See Connectors.
- Resources give an app the services it needs to run, such as a PostgreSQL database or access to an LLM. Valet provisions each one and hands the app its connection details. In a dedicated installation, databases run inside its private network. See Resources.
- Standards are skills too. Valet ships skills for security, dependencies, and how to build each kind of tool, and coding agents read them before they build or publish. Your organization can replace any of them with its own, which is how your engineering standards reach the tools people build. See Governance and Skill library.
- Release policies are checks Valet runs on every release of an artifact, app or agent. They find credentials in the source and packages with known vulnerabilities, and a blocking policy refuses a release that fails. See Release policies.
Who uses Valet
Citizen developers build the tools. They work in Claude Code, Codex, claude.ai, ChatGPT, or any other agent that can run a command or call an MCP server. The agent does the publishing, and the builder never handles a credential. Start with Get started, or share what you know as a skill.
Administrators are the IT, security, and platform teams that support citizen developers and their tools. Start with Connectors and Governance.
Ways to run Valet
- In Valet's cloud. Valet runs a shared service at valet.dev. It's the fastest way to try Valet, and it needs nothing installed. See Cloud.
- A dedicated installation, run by Valet. Valet sets up a complete Valet in its own AWS account for your company, and operates it for you.
- A dedicated installation, run by your team. Valet ships releases, and your operations team runs them in your own AWS account.
Building works the same way in all three. Where a dedicated installation differs, the docs say so. See Dedicated.
How tools grow
A personal tool can become part of a team's business process and later pass to engineering. From laptop to production explains how hosting, data access, sharing and ownership change along the way.