Skip to main content
Environment Config

Dynamic runtime configuration

Manage application settings that change across environments

Centralize runtime config like API endpoints, feature flags, and rate limits. Update settings instantly without deployments.

The Problem & Solution

Before & after Replane

See how teams transform their workflow

Without Replane

  • Hardcoded settings

    Timeouts, limits, and URLs baked into code. Changes need deploys.

  • Environment drift

    Dev and prod configs diverge. Bugs from config mismatches.

  • No visibility

    What config is running where? No central view or history.

  • Slow changes

    Tuning a rate limit means a new release. Too slow for operations.

With Replane

  • Centralized dashboard

    All environments visible in one place. Clear and organized.

  • Instant updates

    Change config values in seconds. No restart or deploy needed.

  • Full audit trail

    Every change logged with author and timestamp.

  • Environment isolation

    Per-environment values with separate access controls.

Key Features

One codebase, many environments

Manage runtime settings across all environments

Live Updates

Config changes apply in seconds

Full History

Complete audit trail for every change

Multi-Environment

Dev, staging, prod with one config

Access Control

Role-based permissions per environment

How It Works

Three simple steps

Get up and running in minutes, not hours

1

Identify runtime configs

Find settings that vary by environment: API URLs, timeouts, rate limits, feature flags, log levels.

2

Create configs per environment

Define base values with environment-specific overrides. Each environment gets its own SDK key.

3

Deploy once, tune anywhere

Same code runs everywhere. Adjust operational parameters from the dashboard.

Benefits

Why teams choose Replane

Built for developers who value speed, reliability, and control

Operational agility

Tune rate limits, timeouts, and thresholds without code changes or deploys.

Clear visibility

See exactly what config each environment is running. Compare across envs.

Safe and audited

Role-based access control. Full history of who changed what and when.

Code Examples

Works with your stack

Official SDKs for all major languages and frameworks

1import { Replane } from '@replanejs/sdk'
2
3interface Configs {
4 'api-base-url': string
5 'request-timeout-ms': number
6 'max-retries': number
7 'rate-limit-per-minute': number
8 'log-level': 'debug' | 'info' | 'warn' | 'error'
9 'cache-ttl-seconds': number
10}
11
12const replane = new Replane<Configs>()
13
14// SDK key determines which environment config to load
15await replane.connect({
16 baseUrl: process.env.REPLANE_BASE_URL,
17 sdkKey: process.env.REPLANE_SDK_KEY // Different key per env
18})
19
20// Runtime config that can be tuned without deploys
21const apiClient = new ApiClient({
22 baseUrl: replane.get('api-base-url'),
23 timeout: replane.get('request-timeout-ms'),
24 maxRetries: replane.get('max-retries')
25})
26
27const rateLimiter = new RateLimiter({
28 maxRequests: replane.get('rate-limit-per-minute'),
29 window: 60_000
30})
31
32// React to config changes in real-time
33replane.subscribe('log-level', (c) => {
34 logger.setLevel(c.value)
35 logger.info('Log level changed to:', c.value)
36})
37
38replane.subscribe('rate-limit-per-minute', (c) => {
39 rateLimiter.setLimit(c.value)
40})
FAQ

Questions about Environment Config

Common questions and answers

Runtime configuration that varies by environment: API endpoints, feature flags, rate limits, cache TTLs, log levels, retry counts, timeout values, UI settings, and operational parameters. Things you want to change without redeploying.

Don't store secrets in Replane. Use a dedicated secrets manager (AWS Secrets Manager, HashiCorp Vault, etc.) for sensitive credentials. Replane is for configuration, not secrets management.

Yes! Define a base config with environment-specific overrides. Common values are shared, only differences are per-environment. This prevents config drift while allowing flexibility.

Use role-based access control. Each environment has its own SDK key and access controls. Enable approval workflows for production changes to require review before applying.

Changes propagate in real-time via Server-Sent Events. Your application receives updates within seconds. Use the subscribe API to react to changes immediately.

Get Started with Environment Config

Ready to ship faster?

Start using Replane in minutes. Free forever for self-hosted, or let us manage everything for you.

No credit card required. MIT licensed. Deploy anywhere.