Set up VaultProof

Move a provider key out of your app’s ordinary runtime.

VaultProof protects provider credentials while your application keeps its familiar SDK and environment-variable workflow. Choose a starting path, understand the boundary, then protect a key. Takes about two minutes.

Your applicationSends the provider request

VaultProof runtimeApplies policy and authenticates upstream

Your providerReceives the authorized request

By the end, you will know:

where protected keys and request metadata appear;
what VaultProof changes in your application;
the safest next step for your environment.

Read the setup guide

Tell us where you want to start.

These three answers tailor your next action. They never grant VaultProof access to a provider account.

What do you want to accomplish first?

Protect an existing applicationMove a key out of a project that already makes provider calls Secure a new projectStart with protected credentials before deployment Evaluate VaultProofReview the model and try a low-risk setup path Standardize a small teamEstablish a repeatable key-protection workflow

First provider Provider category only—never enter a key here.

Primary environment Used to order the setup instructions.

Know what changes—and what does not.

Your app still makes a familiar provider request. VaultProof changes where the complete upstream credential persists and applies controls within the protected request path.

A

Protect the credential

VaultProof splits the provider key before storage. Stored shares are authenticated ciphertexts and remain separate.

B

Route the request

Your application uses VaultProof-managed values and, where required, a provider-compatible base URL.

C

Verify the result

Activity Logs show safe request metadata such as provider, route, status, timestamp, and latency—not the raw provider key.

What you will see in the app

Protected Keys: Add, rotate, revoke, and set limits for provider credentials.
Activity Logs: Confirm protected calls and investigate operational metadata.
Security Alerts: Review conditions that need attention without exposing secret values.
Plans & Billing: Start or manage a plan separately. This onboarding does not start billing.

Keep provider-side controls.

VaultProof complements provider permissions, spend limits, rotation, revocation, monitoring, and application security. It does not replace them.

Your starting path is ready.

Your answers are saved. Take the first real action now; you can explore everything else afterward.

Goal: —
Provider: —
Environment: —

1

Add or initialize a protected key. Do this from Protected Keys or the VaultProof CLI.

2

Make one real provider request. Keep the familiar SDK flow while routing through VaultProof where required.

3

Confirm it in Activity Logs. That visible protected request is the first-value checkpoint.

Your onboarding is already complete.

Continue to your workspace or open Protected Keys to take the next security action.

Open Protected Keys Open dashboard