Skip to content
Varity Docs

Managed Credentials

Varity Team Core Contributors Updated May 2026

Varity automatically provides all the credentials your app needs. You never need to create third-party accounts or manually configure API keys.

How It Works

Section titled “How It Works”

When you deploy with Varity, credentials are handled automatically at every stage:

  1. Development: Shared development credentials are available so you can start building without any .env setup.

  2. Production: When you run varitykit app deploy, the CLI fetches production credentials from Varity’s credential proxy and injects them into your deployed app’s environment.

  3. Runtime: Your deployed app reads its credentials from injected environment variables. Users never see API keys or configuration prompts.

Developer runs: varitykit app deploy
    |
CLI fetches credentials from Varity's credential proxy
    |
Credentials injected into build automatically
    |
App deployed with everything configured

What’s Managed

Section titled “What’s Managed”

Varity provides credentials for:

ServiceWhat It CoversDeveloper Action
DatabaseConnection details for detected databases (Postgres, Redis, MongoDB, MySQL)None required
File StorageUploads, CDN deliveryNone required
InfrastructureNetwork access, operationsNone required

Development Mode

Section titled “Development Mode”

During local development, shared development credentials are available automatically, so your app can connect to a database without any setup. When Varity detects that your app needs a service (for example, a database client in your dependencies), it provisions that service on deploy and injects the connection details into your app’s environment.

Production Deployment

Section titled “Production Deployment”

When you deploy, the CLI handles everything:

Terminal window
varitykit app deploy

Output:

✓ Credentials: Auto-provided
✓ Build complete
✓ Deployed successfully
✓ URL: https://your-app.varity.app

No manual credential setup required.

Security

Section titled “Security”
  • Rate-limited: Credential proxy enforces per-app rate limits
  • API key authenticated: CLI uses embedded API keys to authenticate with the proxy
  • Credentials never stored on disk: Injected at build time only
  • Isolated per app: Each app receives its own credential scope

Verifying Credentials

Section titled “Verifying Credentials”

Run the doctor command to verify your credential status:

Terminal window
varitykit doctor
Checking environment variables...
  ✓ Credentials: Auto-provided
  ✓ Storage API: Accessible

Next Steps

Section titled “Next Steps”