Overview

Keep secrets in Secretkeep and reference them by path. At deploy time the platform reads the current values and injects them as environment variables, so nothing sensitive is stored in your repository.

What you can do

  • Reference secrets by path in your service config
  • Values refreshed on every deploy
  • Access logged in your workspace audit log

Set up

  1. Create a read-only Secretkeep policy for the platform.
  2. Add the policy token in Integrations → Secretkeep.
  3. Replace plain values with secretkeep:// references.
Terminal
$ cloud env set DATABASE_URL=secretkeep://prod/db/url --service api

Free tier · No credit card

Push code today. Be live before your coffee cools.

Connect a repository, pick a region, and get a production URL with HTTPS, logs, and autoscaling already switched on.

$ git push origin main

  1. Build34 s
  2. Deploy12 s
  3. Health checks3 s

your-app.example.com

Buy NowTheme Details