Kitwork — Sovereign Logic Engine

01

Core Philosophy

Kitwork is built on the principle of Sovereign Logic. Direct control over the execution flow with sub-millisecond overhead.

Efficiency

Optimized Radix-tree routing and CGO-based database drivers for industrial scale.

Isolation

Each request runs in a clean, isolated virtual machine environment for maximum safety.

02

Quick Start

Get your first server running in seconds. Define your routes in app.kitwork.js.

app.kitwork.js

                    // Your first Kitwork Server

                    import { router } from 'kitwork';

                    router.get("/").handle((req, res) => {

                        return res.text("Kitwork is ready.");

                    });

03

Installation & Setup

Kitwork runs as a natively compiled single binary. Setup your development workspace using standard Go module configurations.

shell

                    # Initialize a new Go module

                    go mod init myapp

                    # Add the sovereign engine dependency

                    go get github.com/kitwork/engine

04

CLI Reference

Boot the local server in developer hot-reload mode or generate production artifacts using Go command parameters.

shell

                    # Run local server with hot reloading enabled

                    go run .

                    # Compile optimized production server binary

                    go build -o kitapp .

05

Standalone Binary Execution

Run the Kitwork engine without installing Go, NodeJS, or any dependencies. Simply execute the precompiled standalone executable file for your OS directly.

terminal

                    # On Windows: Put config.kitwork.yaml in the same folder and run

                    .\kitwork.exe

                    # On macOS / Linux: Make binary executable and run

                    chmod +x ./kitwork

                    ./kitwork

06

Multi-Tenant Architecture

Kitwork supports dynamic hosting environments out of the box. Organize your app instances under the tenants/ folder. Each tenant workspace runs inside an isolated virtual machine, binding automatically to its assigned domain.

tenants-tree

                    tenants/

                    ├── 029w8decto4uabhpsmfjlxgknzqy7356riv1/    # Tenant ID A

                    │   └── kitwork.vn/                        # Bound to kitwork.vn

                    │       ├── app.kitwork.js

                    │       └── views/

                    └── 1a2b3c4d5e6f7g8h9i0j/                  # Tenant ID B

                        └── myshop.io/                         # Bound to myshop.io

                            ├── app.kitwork.js

                            └── views/