MKON Console
Sign in Get started

MKON Cloud Architecture

Comprehensive documentation on container orchestration, deployment workflows, and automated application scaling[cite: 43].

System Architecture

MKON Cloud eliminates the heavy lifting of traditional infrastructure management[cite: 43]. Our cloud-native orchestration engine dynamically provisions, isolates, and scales your applications using enterprise-grade containerization capable of handling massive workloads.

Rather than managing bare-metal servers, OS dependencies, or complex load balancers, developers simply select a runtime stack[cite: 43]. The platform automatically handles multi-tenant isolation, elastic scaling, unified edge routing, automated SSL termination, and dedicated database clustering across a robust distributed architecture.

[Client Traffic] → [Global Edge Proxy] → [Isolated Tenant Container]

Deployment Lifecycle: How to Host

Deploying an application on MKON Cloud is designed to be frictionless. Follow this standard lifecycle to take your code from local development to production scale seamlessly.

1. Provision Workspace

From the console dashboard, select your desired framework (e.g., Node.js, Laravel) and choose a database engine[cite: 43]. The platform will instantly allocate an isolated environment and generate secure database credentials.

2. Upload Source Code

Access the integrated File System tool from your project dashboard. Upload your application files via the secure web interface[cite: 43]. Note: Do not upload heavy dependency folders (like vendor/ or node_modules/) — the build engine handles these automatically to save bandwidth and ensure cross-platform compatibility[cite: 43].

3. Configure Environment

Inject your environment variables. Open the Database tab to view your automatically generated internal credentials, and add them to your project's configuration (e.g., your .env file)[cite: 43].

4. Build & Deploy

Click the Build & Deploy button on your dashboard. The orchestrator will safely mount your storage, resolve your framework's dependencies, apply security permissions, and map the container to the global edge network with zero downtime[cite: 43].

Edge Routing & TLS

Network traffic is securely managed via a unified, scalable edge proxy[cite: 43]. The system listens for internal container state changes and automatically updates routing tables dynamically. You never need to configure manual port bindings or expose internal services[cite: 43].

  • Level-1 Subdomains: Tenants are immediately mapped to RFC-compliant subdomains upon creation (e.g., app.mkonnetworks.com)[cite: 43].
  • Custom Domains (BYOD): Custom domain routing is handled dynamically via internal logical rules. Simply point your CNAME or A records to the platform, and Let's Encrypt TLS certificates are resolved and provisioned on the fly[cite: 43].

Runtime Stacks Operation

Each framework is powered by a customized, optimized Docker image designed to entirely abstract away server configuration[cite: 43]. Below are the internal execution flows for each supported stack.

Laravel / PHP Framework

Execution Flow:

  1. The engine maps the storage volume and automatically rewrites the document root to the /public directory[cite: 43].
  2. URL rewriting is enabled natively to support Laravel's routing architecture[cite: 43].
  3. PHP OPcache is enabled and optimized for production to ensure instant code reflections without memory leaks[cite: 43].
  4. Post-boot, the orchestrator detects composer.json and automatically executes dependency installation[cite: 43].
  5. Storage symlinks are fired, and strict ownership limits are applied to secure the filesystem[cite: 43].

Pure PHP (Vanilla)

Execution Flow:

  • The document root remains at the base folder level, functioning seamlessly without complex directory routing[cite: 43].
  • A default index.php file is scaffolded automatically to prevent generic directory listing errors[cite: 43].
  • Directory permissions are synchronized to allow seamless web-based file management and script execution[cite: 43].

n8n Workflow Automation

Execution Flow:

  • A dedicated automation engine is spun up with explicit RAM allocation guarantees to prevent workflow termination under heavy data loads[cite: 43].
  • Webhook URLs are dynamically generated and injected based on the workspace's assigned domain or custom domain[cite: 43].
  • Internal user IDs are mapped seamlessly to ensure the workflow database is persisted securely to your isolated storage volume[cite: 43].

Python 3.11 Runtime

Execution Flow:

  • The system scans for requirements.txt and resolves dependencies automatically via pip[cite: 43].
  • The container looks for an app.py entrypoint to initiate the runtime[cite: 43].
  • If the application code is missing, the container enters a safe idle state, preventing crash-loops while you upload your files[cite: 43].

Node.js Application

Execution Flow:

  • The orchestrator scans for package.json upon build[cite: 43].
  • Dependencies are resolved, and the application is booted using your defined start script[cite: 43].
  • Traffic is dynamically routed directly to your application without any manual port-binding or reverse proxy configuration required from the developer.