DOCS/GETTING_STARTED

Quick Start & Core Workflow

Take a repository from your local environment to kr0n's global edge network in under 60 seconds using the automated build engine and live log stream.

ESTIMATED TIME: ~60 SECONDSDEPLOY ENGINE: V1.0.4EDGE COLD-START: < 15MS

#Platform Overview

kr0n is a next-generation edge deployment platform engineered for modern web applications, microservices, and WebAssembly runtimes. When you push a deployment, kr0n analyzes your project's Abstract Syntax Tree (AST), resolves dependencies in an isolated sandbox, and broadcasts immutable build outputs across our global network of edge PoPs.

IMMUTABLE EDGE ARCHITECTURE

Every deployment generates an isolated cryptographic hash (e.g. f2a991b) associated with your commit. Traffic can be routed instantaneously with zero downtime or rolled back without rebuild overhead.

#Prerequisites

Before initiating a deployment, ensure you have:

A Git repository containing a standard framework manifest (package.json, kron.config.json).
A verified kr0n account (authenticated via Login).
Optional: Node.js 18+ if deploying via the terminal CLI (kron).

#Step 1: Connect Repository

You can link repositories via the Web Dashboard or directly from the homepage hero:

Web Console

Navigate to Add Service Wizard. Select an authorized account (e.g. arpittripathi), browse available git branches, and click Import.

Terminal CLI

Run the local discovery command inside your project directory:

$ kron import --local

#Step 2: Configure Environment Variables

Define encrypted secrets and application configuration via the Environment Variables section at Service Settings.

.env.production

1234
# Production Configuration
DATABASE_URL="postgres://user:secret@edge-db.kron.internal:5432/production"
NEXT_PUBLIC_API_URL="https://engine.io/api/v1"
SESSION_SECRET="e9b28fa48c21e69b0f47e248b991"

ENVIRONMENT SCOPES

kr0n supports three distinct variable scopes: Production, Preview, and Development. Variables marked as sensitive are encrypted with AES-256 and never logged in the build stream.

#Step 3: Build & AST Pipeline Execution

Upon triggering deployment, the build stream (BUILD_LOG_STREAM_V1) executes sequentially:

[08:45:12] INITIALIZING ENGINE

[08:45:13] → FETCHING DEPENDENCIES

[08:45:15] → ANALYZING AST

[08:45:18] ✓ BUILD SUCCESSFUL (2.4s)

[08:45:18] → DEPLOYING TO GLOBAL EDGE

[08:45:19] OPTIMIZING ASSETS...

[08:45:20] COLD START CACHING...

You can monitor this live stream in your dashboard at Deployment History or in your terminal using kron logs --tail.

#Step 4: Global Edge Dispatch & Live URL

Once build synthesis is complete, your application is live on the kr0n global edge. Each project is allocated an immediate edge subdomain:

bash

123
https://engine.io/watch-wise
# Staging/Branch Previews:
https://engine.io/watch-wise-edge-v2.preview.kron.app

Inspect response times, edge requests, and bandwidth transfer metrics on the dedicated Usage Analytics dashboard.

#Spatial Canvas Workspace

The kr0n Projects interface (/projects) features an interactive spatial canvas workspace. You can drag and organize your deployed service cards (nucleus-engine, quantum-web,auth-service, legacy-dash) to map your multi-service microfrontend architecture.

AI & Engine Intelligence →