OpenBao vs Vault Playground

This playground lets you experiment with OpenBao and Vault in a single environment.

Compare how they work and explore their similarities and differences.

Dev mode

Both services are configured to run in dev mode by default, meaning:

• Initialized and unsealed - The server will be automatically initialized and unsealed.
• In-memory storage - All data is stored (encrypted) in-memory.
• KV engine enabled at secret/

If you'd prefer to run the services "normally", see the Setup without dev mode section.

For more feature demos, check out the Other playgrounds section.

You can read more about the properties of the dev server here:

• OpenBao
• Vault

Connecting

Connect to each service using the following commands:

bao status

vault status

The root token for connecting from other clients (e.g., the embedded UIs) is iximiuz.

If you're feeling adventurous, try connecting from one client to the other service:

bao status -address http://vault:8200

vault status -address http://openbao:8200

Configuration

To experiment with custom configurations, place your config files in the following location (ensure they're owned by the service user):

chown -R openbao:openbao /etc/openbao/config.d/

chown -R vault:vault /etc/vault.d/config.d/

Other playgrounds

Other playgrounds showcasing features not available here: coming soon!

Setup without dev mode

If you choose to run the service in "normal" mode (i.e. Dev mode disabled), a few extra steps are needed to replicate the dev mode setup.

These steps are outlined in this tutorial.

Details