Step 01
Start with a project boundary
Create a clear grouping for resources that belong to the same project or operational responsibility. A platform vault can contain its application database, payment API key and gateway certificate. Keep unrelated internal tools in a separate vault.
Step 02
Separate the environments
Use distinct production and staging environments. A test billing key belongs alongside the test database, while production credentials remain in their own environment. Clear labels help a team select the right resource.
Step 03
Keep the resource context
Record the resource type, connection details and responsible team. Use versions to keep track of changes, and expiration dates with reminders for resources that need renewal. Consult the activity history when reviewing a change.
Try the interactive preview
The product preview uses fictional resources. Explore it without connecting a service or changing a real workspace.
Explore the product