01
Agent asks
A typed MCP request names the project, environment, action, and resource.
No raw credentialmacOS preview · first release in development
Connect your tools.
Keep credentials
out of the conversation.
Vaultage keeps development credentials with your local broker and lets agents ask for one approved action at a time.
Built for macOS · local stdio MCP · provider billing stays direct
coding agenttyped request
local brokerapproved action
provider APIresult + receipt
provider keys bypass Vaultage cloud
01 / The useful boundary
One request.
One decision.
Agents can be great at knowing what to do next. Vaultage keeps the authority to do it in a place you can inspect: your local broker, your project, your environment.
02
You approve
The local broker shows the exact action before it reaches a provider.
Human in the loop03
Receipt returns
The provider result and a redacted local receipt close the loop.
Auditable by defaultA smaller surface area
Keep your credentials
close to the work.
Vaultage is a development credential broker for projects that ship. General-purpose password management stays out of scope; each agent action has its own approval.
Read the local MCP notes02 / Services
Choose a capability,
not a credential.
The catalog publishes the adapters and actions Vaultage has actually checked. Status comes from the service catalog; planned services never get a connect button.
Missing a service?Tell us what your project needs.
03 / Pricing
Connect more services.
Keep control.
One plan for your provider connections. Provider accounts, usage, and their charges stay yours.
FreeStart here
$0to start
A focused way to try local approvals with the projects you already have.
- 3 managed provider connections
- Unlimited projects and environments
- Local activity and receipts
ProMost room
$2.99/ month
Connect more services and keep the same clear approval flow across your builds.
- Unlimited managed connections
- Everything in Free
- Monthly or annual billing
Annual: $25.12 / year ≈ 30% less
Subscription billing is Vaultage’s charge and checkout is hosted by Stripe for card payments; eligible browsers may also show Apple Pay. Provider API and usage charges are paid directly to each provider under their terms.
04 / Documentation
Understand the
trust boundary.
Every surface tells you where an action happens and what it can expose. Start with the small set of ideas that makes Vaultage useful.
01
How local MCP works
See the path from a typed request to a provider result.
02Catalog status
Learn how Available, In development, Requested, and Not supported differ.
03Account and billing
Manage your account, plan, and billing with Google or a verified email.
Desktop companion · In development
First Mac release in development.
The download will appear here when the Mac app is ready.
05 / Your account
A clear view of
your plan.
Sign in to see your hosted account, connection allowance, and billing status. Local vault contents never appear here.
Account access will be available with the first release.
Sign-in setup is in progress.
Policy drafts
Plain language,
before promises.
Privacy (draft)
The hosted service currently stores account and billing records, device authorization records, the published service catalog, and provider request records. Local provider connection metadata, project files, and receipts stay with the local product. Final retention, support, and contact details will be published before launch.
Terms (draft)
Vaultage pricing covers your account: Free includes three managed provider connections and Pro is $2.99 monthly or $25.12 annually. Provider accounts and usage charges remain subject to each provider’s terms. These drafts are product notes, not final legal terms.