Coming Soon — Join the Waitlist

The Modern Workspace for Managing All Your Data & Operational Configuration

A clean, collaborative workspace where teams can store, version, and safely manage every piece of operational configuration in one place.

✨ See How It Works

pipeline.py

                        # Stop scattering config across sheets, YAML,
                                and env vars
                        from configmat import
                            ConfigMat
                        
                        # One line to access any
                                configuration
                        config = ConfigMat.load(
                         asset='data-pipeline',
                         env='production'
                        )
                        
                        # Type-safe, versioned, always
                                up-to-date
                        db_host = config.get('database.host')
                        retries = config.get_int('max_retries', default=3)
                        settings = config.get_json('pipeline_settings')
                    

Configuration Chaos is Killing Your Team's Productivity

Today, teams spread their most important settings across Google Sheets, YAML files, environment variables, wikis, and outdated configs hidden deep in code. This leads to broken pipelines, inconsistent environments, silent production issues, and hours of wasted time trying to find "where that one setting lives."

ConfigMat fixes this.

One unified workspace. Every configuration. Every team.

What You Can Store

A Single Place for All Your Configuration

Create organized "configuration assets" for anything your team relies on

🔑

API Keys

🚩

Feature Flags

⚙️

Pipeline Parameters

📋

Data Contracts

🌍

Environment Overrides

🔌

Integration Settings

🤖

AI Agent Config

📦

JSON, YAML, Files

For Everyone

Non-Technical Users Can Finally Contribute

Business analysts, PMs, and ops teams can safely update configuration—no code required

❌ Before ConfigMat

📋 Business Analyst: "Can we change the threshold?"

↓

💻 Developer: "Sure, let me find where that lives..."

↓

🔍 Code Review: "LGTM"

↓

🚀 Wait for next deploy

⏱️ 2-5 days

😤 High friction

✅ After ConfigMat

📋 Business Analyst opens ConfigMat

↓

🔍 Finds "model_parameters" asset

↓

✏️ Updates threshold: 0.80 → 0.85

↓

✅ Change is live instantly

⏱️ 2 minutes

😊 Self-service

ConfigMat Environment: staging

model_parameters

confidence_threshold

max_batch_size

model_version

No code. No terminal. No waiting for deploys. Just a form and a save button.

Developer Experience

💻 Local Development That Actually Works

One command to sync. Personal overrides. Works offline.

Consistent Environments

No more "works on my machine" bugs. Every developer pulls the same configuration baseline. New teammates onboard in minutes, not hours.

Terminal

$ configmat pull --env local

✓ Pulled 4 assets (23 values) from local environment

✓ Configuration cached at ~/.configmat/cache

$ npm run dev

# Your app automatically uses the synced config

😊 Everyone has the same config baseline
🚀 New devs onboard in minutes
🔌 Works offline with cached values

Personal Overrides

Testing a new feature? Debugging with different settings? Override values just for you—without affecting teammates.

Terminal

$ configmat override set feature_flags.new_checkout true

✓ Override set for local environment

# Your local app sees: new_checkout = true

# Your teammates see: new_checkout = false

$ configmat override clear

✓ All overrides cleared

🧪 Test features in isolation
👥 Never affect teammates' environments
🔄 SDK handles resolution automatically

Version Control

📜 Every Change is Tracked and Reversible

See who changed what, when, and why. Roll back with one click.

❌ Before ConfigMat: Detective Work

💬 Mike: "The model is behaving weird today"

💬 Sarah: "Did someone change the threshold?"

💬 Mike: "I don't know, let me check the repo..."

💬 Sarah: "It's not in the repo, it's an env var"

💬 DevOps: "Which env var? On which server?"

💬 Mike: "Can we roll back?"

💬 DevOps: "Roll back to what? I don't know the old value"

⏱️ 45+ minutes of detective work

🤷 No audit trail

✅ After ConfigMat: Full History

v12 • sarah.chen 2 hours ago

confidence_threshold: 0.80 → 0.75

"Testing lower threshold for edge cases"

v11 • mike.johnson 3 days ago

max_batch_size: 500 → 1000

⏱️ Found in seconds

🔄 One-click rollback

Terminal — Rollback

$ configmat rollback model_parameters --to v11

✓ Rolled back to v11

✓ Change live in production in 2 seconds

# Problem solved. Full audit trail preserved.

One click. Problem solved. Every change, every rollback—fully documented.

Discover Configs Instantly

🔍 Smart Descriptions & Semantic Search

Add rich descriptions to every config. Find anything using natural language—not just key names.

🔍

What's the retry limit for failed payments?

📊 payment_retry_max number

payment-service / settings

Maximum number of retry attempts for failed payment transactions before marking as permanently failed. Includes exponential backoff between attempts.

📍 production: 5 👤 Updated by sarah.chen 🕐 2 days ago

⏱️ payment_retry_delay_ms number

payment-service / settings

Base delay in milliseconds between payment retry attempts. Uses exponential backoff (delay × 2^attempt).

📍 production: 1000 👤 Updated by mike.johnson 🕐 1 week ago

🚨 failed_payment_alert_threshold number

alerting / thresholds

Number of consecutive failed payments before triggering a PagerDuty alert to the on-call engineer.

📍 production: 10 👤 Updated by ops-team 🕐 3 weeks ago

📝 Adding Descriptions is Easy

Config Key: payment_retry_max Type: number Description: Maximum number of retry attempts for failed payment transactions before marking as permanently failed. Includes exponential backoff between attempts. Example: "For PCI compliance, keep this at 5 or lower. Higher values may trigger fraud detection on some payment processors."

Try searching for anything in natural language:

"How do I configure model confidence?" "Where's the Snowflake connection string?" "What controls the batch size?" "Show me all feature flags" "API rate limiting settings"

No more guessing key names. Search by what the config does, not what it's called.

Developer Experience

Built for How You Actually Work

ConfigMat fits naturally into any engineering workflow

dag.py — Airflow example

                        # Before: Config scattered
                                everywhere
                        # db_host =
                                Variable.get("DB_HOST")
                        # api_key =
                                os.environ["API_KEY"]
                        # settings =
                                yaml.load("config.yaml")
                        
                        # After: One source of truth
                        from configmat import
                            ConfigMat
                        
                        config = ConfigMat.load('etl-pipeline')
                        
                        # Everything in one place
                        conn = config.get('snowflake.connection')
                        schedule = config.get('dag.schedule')
                        alerts = config.get_json('alerting')
                    

app.ts — Node.js example

                        import { ConfigMat } from '@configmat/sdk'
                        
                        const config = await ConfigMat.load({
                         asset: 'payment-service',
                         env: process.env.NODE_ENV
                        })
                        
                        // Type-safe with full
                                intellisense
                        const stripeKey = config.getString('stripe.api_key')
                        const timeout = config.getNumber('timeout_ms')
                    

Programmatic Access via SDKs

Applications, pipelines, and AI agents can fetch configuration instantly. One stable endpoint, always up-to-date. Works with Python, Node.js, or call the API directly.

Multi-Environment Support

Local → Staging → Production. Promote values between environments with a single click. Preview changes before promoting. No more "it works on my machine."

Works With Your Stack

Native integrations for Airflow, dbt, and your favorite tools. CLI commands for pulling configs into local development. Environment variable generation for legacy systems.

Features

Built for Modern Data, ML & Engineering Teams

No more scattered configuration across tools that weren't designed to manage it

✏️

Easy Editing for Everyone

A clean UI where anyone—technical or not—can safely update values with guardrails. No YAML expertise required.

📜

Versioning & History

Every change is tracked. Roll back anytime. Never ask "who changed this?" again.

🔄

Environment Promotion

One-click promotion from local → stage → production. Preview changes before they go live.

🔌

Programmatic API Access

Applications and pipelines fetch configuration instantly. One stable endpoint, always up-to-date.

👥

Team & Organization

Invite teammates, assign roles, and collaborate in a structured workspace with proper access controls.

📦

All Config Formats

Full support for JSON, Key-Value, YAML, plain text, and file uploads. Store any shape of configuration.

Guardrails

Designed for Operational Safety

Everything is built with production reliability in mind

Available Now

✓ Environment ordering and locking
✓ Secret masking
✓ Change previews before promotion
✓ Audit logs
✓ Role-based access control

Coming Soon

Soon Approvals & workflows
Soon Validation rules
Soon Scheduled promotions
Soon Snapshots and backups
Soon Git/GitHub sync
Soon Breaking change detection

At a Glance

📊 The Before & After

See how ConfigMat transforms your configuration management

Aspect	Before ConfigMat	After ConfigMat
Where is config?	Scattered across repos, sheets, env vars	One searchable workspace
Who can change it?	Only developers	Anyone with permission
How long to change?	Hours to days (code + deploy)	Seconds (UI or CLI)
Can we roll back?	Maybe... if we remember the old value	One-click rollback with history
Local dev setup	Manual, inconsistent, painful	`configmat pull` and done
Audit trail	"Who changed this?" 🤷	Full history: who, what, when, why
Environment sync	Copy-paste, hope it's right	Preview diff, promote with confidence

Pricing

Simple, Transparent Pricing

Choose the plan that works best for your team. No hidden fees, no surprises.

🏠

Open Source

Self-host ConfigMat on your own infrastructure. Perfect for teams who want full control.

Free

Deploy anywhere.

✓ Full source code access
✓ Access to Docker image
✓ Unlimited users & configs
✓ All core features included
✓ Community support
✓ Self-managed updates

View Repo (Coming Soon)

🚀

Free Tier

Perfect for small teams getting started. Fully managed cloud hosting with no credit card required.

Free

Up to 3 users

✓ Fully managed cloud hosting
✓ Up to 3 team members
✓ Unlimited configs & environments
✓ All core features included
✓ Email support
✓ 99.9% uptime SLA
✓ Automatic backups

Get Started Free

☁️

Team Plan

For growing teams that need more seats. Scale as you grow with simple per-user pricing.

$ 10 /month

+ $5/month per user after 3 users

✓ Everything in Free Tier
✓ Unlimited team members
✓ Priority support
✓ Advanced audit logs

Start Free Trial

Need enterprise features? Contact us for custom pricing, dedicated infrastructure, and SLA guarantees.

⭐ Be the First to Try ConfigMat

We're opening early access to a limited group of teams. Join the waitlist for launch invites and exclusive onboarding help.

✅ You're on the list! We'll be in touch soon.

🔒 No spam, ever. Unsubscribe anytime.

ConfigMat is the future of configuration management—
simple to use, safe to trust, and built for teams that take their data seriously.