Core concepts, architecture overview, real-world use cases, and problems Dimensigon solves.
Dimensigon (DM) is an open-source Python-based backend technology designed to bootstrap elastic services and enable continuous automation. It's a decentralized, mesh-networked orchestration platform that coordinates complex inter-server automation regardless of whether servers can directly reach each other.
Key principle: 100% Python and truly open source with no freemium or enterprise versions planned.
// Dimension
A logical group of all servers that can be managed with DM.
Think of it as a cluster or organization unit.
One Dimension = One unified management domain
// Continuous Automation
Most maintenance operations can be event-triggered
and automated to achieve higher maturity.
Retain control after automation + interconnect fully
to monitor, react, and adapt to your needs.
// Mesh Networking
P2P architecture where every node is equal.
No central coordinators, no masters.
Nodes discover each other automatically.
// Orchestration
Multi-step workflows across distributed nodes.
Supports Shell, Python, HTTP, and nested workflows.Dimensigon consists of four integrated components:
┌─────────────────────────────────┐
│ DShell (CLI) / Web Manager │
│ User Interface Layer │
└────────────────┬────────────────┘
│
┌────────────────▼────────────────┐
│ REST API (v1.0 & v2.0) │
│ HTTP / JSON │
└────────────────┬────────────────┘
│
┌────────────────▼────────────────┐
│ DM Core (Python Flask) │
│ Coordination & Communication │
└────────────────┬────────────────┘
│
┌────────────────▼────────────────┐
│ Mesh Networking │
│ Distributed Database (Catalog) │
│ Vault, Locking, Logs │
└─────────────────────────────────┘On-Premises (Private DC)
├── prod-db-1
├── prod-app-1
└── prod-cache-1
AWS Cloud (us-east-1)
├── web-1
├── web-2
└── web-3
Azure Cloud (eu-west-1)
├── backup-1
└── analytics-1
All coordinated through single Dimensigon cluster
with unified orchestration and automation.Problem solved: Organizations struggle with managing high-complexity hybrid multi-cloud environments across different vendors.
Manage infrastructure across multiple datacenters and regions:
Perfect for companies with offices/datacenters in different cities or countries.
New York DC London DC Tokyo DC
├── db-primary ├── db-replica ├── cache-1
├── app-1 ├── app-2 ├── app-3
└── app-2 └── app-3 └── monitor
│ │ │
└───────────────────┼───────────────────┘
Dimensigon Mesh Network
Unified orchestration for:
- Database failover
- Cache warming
- Log aggregation
- Cross-DC replicationApplication: E-commerce Platform
Traffic: Highly volatile (sales events)
Morning (low traffic)
├── api-1, api-2, cache-1
Afternoon (peak traffic - auto-scale triggered)
├── api-1, api-2, api-3, api-4, api-5
├── cache-1, cache-2, cache-3
└── db-replica-1, db-replica-2
Late night (shutdown non-essential)
├── api-1, api-2, cache-1
Dimensigon handles:
✓ Auto-scaling orchestrations
✓ Service health checks
✓ Configuration updates
✓ Log aggregation during peakDesigned specifically: For volatile environments and building elastic services.
Support different tenants with independent requirements:
SaaS Platform (Single Dimensigon Cluster)
Tenant A (Finance Company)
├── db-a-prod, app-a-1, app-a-2
└── Secrets: vault.tenant-a-*
Tenant B (E-commerce)
├── db-b-prod, app-b-1, app-b-2, app-b-3
└── Secrets: vault.tenant-b-*
Tenant C (Healthcare)
├── db-c-prod, app-c-1
└── Secrets: vault.tenant-c-*
Features:
✓ ACL-based data isolation
✓ Separate orchestrations per tenant
✓ Independent scaling
✓ Quick provisioning/de-provisioningDMZ (Public)
└── load-balancer-1
Internal Network A (Finance)
├── app-payment-1
├── app-banking-1
└── db-financial
Internal Network B (Operations)
├── app-inventory-1
├── app-fulfillment-1
└── db-operations
No direct connectivity between networks.
Dimensigon mesh routes through available paths.
Enables automation across firewalls:
✓ Secure distributed command execution
✓ Works across isolated network segments
✓ No port forwarding needed
✓ Zero-trust compatibleDeploy applications without direct connectivity requirements:
Source Network (HQ):
Build system uploads app v2.0.1
Internal Network (No internet):
├── Proxy node (has internet)
├── App server 1 (no internet)
└── App server 2 (no internet)
Distribution Flow:
1. Upload to network proxy
(Proxy can reach internet via VPN)
2. Proxy receives app binary
(One copy, stored centrally)
3. Route to destination nodes
(Through mesh, no direct internet)
Benefits:
✓ No direct internet requirement
✓ Complex provisioning workflows
✓ Works across disconnected environments
✓ Tracks transfer statusProblem 1: Complex Infrastructure
→ Unified standard for all automation
Problem 2: Loss of Control After Automation
→ Retain control + continuous improvement
Problem 3: Network Isolation Issues
→ Orchestrate without direct connectivity
Problem 4: Fragmented Logging
→ Log Federation across all nodes
Problem 5: High Administration Costs
→ Event-triggered automation reduces manual work
Problem 6: Multi-Tenant Complexity
→ Built-in support with independent lifecycle
Problem 7: Software Distribution Complexity
→ Distributed transfer through mesh networkingDimensigon vs Traditional Tools
Dimensigon:
✓ Decentralized (no master)
✓ Works across firewalls
✓ Log Federation built-in
✓ Distributed Vault
✓ Quorum consensus
✓ 100% open source
Traditional Tools:
✗ Centralized master
✗ Requires direct connectivity
✗ External log infrastructure
✗ Centralized secret storage
✗ Single point coordination
✗ Limited to freemium + enterpriseManage infrastructure anywhere - on-prem, cloud, hybrid, multi-cloud.
Multi-layer encryption, ACL-based access, and audit trails.
Designed for volatile environments and rapid scaling.
Python-based, open source, REST API, and interactive CLI.