1.1 Platform Overview
App Config.json is a centralized, version-controlled configuration management platform engineered for modern development teams. It provides real-time synchronization, strict environment isolation, and enterprise-grade secret handling across distributed applications and microservices.
This documentation covers v1.1 of the App Config.json platform. Notable updates from v1.0 include improved webhook reliability, multi-tenant project support, and updated SDK initialization patterns for browser environments.
Core Concepts
The platform is structured around three foundational primitives that define how configurations are authored, stored, and delivered:
- Projects – The top-level container representing a distinct application or service within your organization.
- Environments – Isolated execution contexts (e.g.,
dev,staging,production) that maintain separate configuration snapshots. - Keys & Values – Schema-validated name-value pairs supporting primitives, structured JSON, and encrypted secrets.
Architecture & Data Flow
App Config.json operates on a publish-subscribe model optimized for sub-100ms propagation. The system decouples configuration authoring from delivery using an immutable version registry and edge-cached distribution nodes.
+------------------+ +---------------------+ +------------------+
| Control Plane | | Config Registry | | Edge Delivery |
| (Dashboard/REST) |---->| (Immutable VFS) |---->| (CDN/WebSocket) |
+------------------+ +---------------------+ +------------------+
| | |
+--[Auth/RBAC]----------+--[Event Stream]--------+
| |
+---> Client SDKs (Server, Web, Mobile, CLI)When a configuration update is committed:
- Changes are validated against the project's JSON schema
- A new immutable version is written to the Config Registry
- Edge nodes cache and propagate deltas via WebSocket or long-poll fallback
- Connected SDKs receive the update and trigger local
on('change')hooks
Key Features & Capabilities
| Feature | Description | Plan Availability |
|---|---|---|
| Real-Time Sync | Sub-100ms propagation to connected clients with automatic retry | Pro & Enterprise |
| Version History & Rollback | Full audit trail with one-click revert to any previous snapshot | All Plans |
| Environment Isolation | Strict separation between dev, staging, and production contexts | All Plans |
| Secret Encryption | AES-256-GCM at rest, TLS 1.3 in transit, zero-knowledge handling | Pro & Enterprise |
| Webhook Triggers | Event-driven notifications on config changes, rollbacks, and deployments | All Plans |
Supported SDKs & Integration Methods
App Config.json provides first-party SDKs for major ecosystems, plus a universal REST/GraphQL API and cross-platform CLI for custom automation workflows:
@appconfig/sdk– JavaScript/TypeScript (Node 16+ & Browser)appconfig-python– Python 3.8+ (async & sync support)appconfig-go– Go 1.20+ (gRPC & HTTP fallback)appconfig-cli– Cross-platform terminal tool for CI/CD pipelines- REST API & GraphQL Endpoint – Language-agnostic integration with OpenAPI specs
Quick Integration Example
To initialize a project in your application, install the SDK and configure the client with your project token:
import { AppConfig } from '@appconfig/sdk';
const client = new AppConfig({
projectId: 'proj_8x9k2m',
environment: 'production',
token: process.env.APP_CONFIG_TOKEN,
fallback: { default_timeout: 5000 }
});
// Subscribe to live configuration updates
client.on('change', (config) => {
console.log('Config updated:', config);
applyConfig(config);
});
// Initial load
const initial = await client.get();
applyConfig(initial);Never expose your APP_CONFIG_TOKEN in client-side bundles or public repositories. Use environment variables, a secrets manager, or server-side proxying for browser-based applications.
Next Steps
Continue exploring the platform documentation: