How It Works

📝 Define & Schema-Validate

Start by defining your configuration structure. App Config.json enforces JSON Schema validation to prevent typos, missing fields, or type mismatches before they ever reach production.

                                schema.json
                                App Config.json
                            

{
  "type": "object",
  "required": ["api_url", "feature_flags"],
  "properties": {
    "api_url": { "type": "string", "format": "uri" },
    "feature_flags": {
      "type": "object",
      "properties": {
        "enable_dark_mode": { "type": "boolean" },
        "max_concurrent_reqs": { "type": "integer" }
      }
    }
  }
}
                            

🔗 Connect via SDK or API

Drop our lightweight SDK into your application. It initializes in <10ms, fetches the latest validated config, and caches it locally for offline resilience.

                                index.js
                                JavaScript SDK
                            

// Initialize in milliseconds
const config = await AppConfig.init({
  projectId: "proj_8x92a",
  environment: "production"
});

// React to live changes without restarts
config.on("update", (newConfig) => {
  console.log(`Config updated: ${newConfig.version}`);
  applyFeatureFlags(newConfig.feature_flags);
});
                            

🚀 Sync, Audit & Rollback

Changes are instantly broadcasted to all connected instances via WebSockets. Every update is versioned, audited, and can be rolled back with a single click if something breaks.

                                audit-log.json
                                App Config.json
                            

[
  {
    "version": 14,
    "timestamp": "2025-06-14T09:23:11Z",
    "author": "alex@company.com",
    "diff": {
      "feature_flags.enable_dark_mode": { "from": false, "to": true }
    },
    "status": "deployed"
  }
]
                            

Live Sync Simulation

See how configuration changes propagate across your infrastructure in real-time.

Dashboard

Editor

→

API Gateway

Listening

→

App Instances

Synced

Frequently Asked Questions

How fast are configuration updates applied? ▼

Updates propagate via persistent WebSocket connections and typically reach all instances within 50-150ms. Our SDKs also implement automatic retry and local caching to ensure zero downtime even during network fluctuations.

Can I use App Config.json without rewriting my codebase? ▼

Yes. Our SDKs are designed to be drop-in replacements for standard config loaders. You can point your existing app to our endpoint, and all subsequent changes will be handled dynamically without code deployment.

What happens if a config update breaks my application? ▼

Every change is versioned. If a deployment causes issues, you can trigger an instant rollback from the dashboard or via API. The previous state is restored to all instances in under 200ms, with full audit logging of the incident.

Is sensitive data like API keys encrypted? ▼

Absolutely. All configurations are encrypted at rest using AES-256-GCM and in transit via TLS 1.3. We also support secret masking in logs and audit trails, and offer optional client-side encryption for zero-knowledge workflows.

How App Config.json Works