Manage application
configuration and secrets.

YAML, JSON, passwords and certificate files for each environment.
Read them through the Go SDK, mounted files or native Secret / ConfigMap objects.

Self-hostedYAML / JSONGo SDKTwo Kubernetes modes
CONFIGRA / VAULTValues by environment, with change history
Configra Vault workspace showing a database item, environment variants, field references and revision history.
Actual UI · Demo data · Sensitive values hidden by default

USE CASES

When is Configra useful?

INTEGRATIONS

Three ways to connect applications

Go applications can use the SDK.
Other applications can read files or environment variables.

GO SDK

Read directly from Go

Fetch complete YAML / JSON with the SDK. Enable polling when you need updates, then validate and apply the new settings in your program.

Use the Go SDK →
CSI PROVIDER

Mount files into a Pod

For programs in Kubernetes that read configuration files. Enable the CSI driver's periodic updates, and make sure the application reloads the files.

Set up the CSI provider →
KUBERNETES SYNC

Sync to a Secret or ConfigMap

Copy configuration into native Kubernetes objects at regular intervals. Programs using environment variables need a new Pod to adopt changed values.

Use native synchronization →

CONFIGS & VAULT

Store shared passwords once

Store shared values in Vault and refer to them in configuration. When an application reads, Configra fills in the values for that environment and returns the complete document.

  • Keep separate values for development, testing and production
  • Inspect history, compare changes and clone configuration
  • Keep passwords hidden until you choose to reveal them
  • Investigate reads and changes through access and audit logs
Read about Configs and Vault →
Configra dark workspace with Vault fields and revision navigation.
Administration lists managed client certificate authorities with issuance and revocation controls.

CLIENT CERTIFICATES

Create CAs and issue client certificates

Create a certificate authority (CA) in the workspace, then issue certificates for applications. Configra keeps its signing key encrypted for later issuance. A private-key backup is available only at creation.

Manage client certificates →
Before deployment

Check the access boundaries

A Token can read every configuration in a granted environment, not just one item. Before rollout, test capacity, backup recovery and API ingress in your own environment.

Read the security and release status →

QUICKSTART

Run Configra locally

Use the development stack to explore the UI, create configuration and test reads.

Open the quickstart →