CKN/Technology/CKN Server
CKN Server

Business servers, secure from the first line

CKN Server is a framework for building APIs, WebSockets and server-rendered pages, built directly on Node.js with no Express or third-party HTTP stack. It gives your back-end a fast, secure foundation that you own end to end.

1runtime dependency only (CKN Core)
73automated test files covering security, WebSocket, cluster and API
10,000idle WebSockets opened in 0.5 s on a single process
88krequests per second (small JSON) with 4 workers
Capabilities

What CKN Server does

01

HTTP, HTTP/2 and WebSocket built in

The whole network layer is written on the Node.js standard library, so the protocols real business systems need work without extra libraries.

  • HTTP/1.1, HTTPS and HTTP/2 on one port
  • RFC 6455 WebSocket with rooms and broadcast
  • NDJSON and SSE streaming
  • Multipart file upload with file validation
02

Modules, controllers and Features

Every endpoint is one Feature that keeps its route, permissions, schema and documentation in one place, so new team members read the code and understand it quickly.

  • Modules and controllers discovered from folders
  • Each Feature has a project-wide unique code
  • Scopes, tags and idempotency set per Feature
  • Full Feature manifest from a single command
03

Security ready to use

One call to useSecureDefaults gives you the standard protections, and the authentication middleware enterprise systems need is included.

  • Security headers, CORS, HPP and rate limiting
  • JWT (HS/RS/PS/ES and JWKS) and API keys
  • CSRF protection and persisted sessions
  • Idempotency-Key to stop duplicate writes on retry
04

Validation and automatic API docs

Define a JSON Schema once. Input is checked before your logic runs and OpenAPI documentation is generated for you, so the docs never drift.

  • Bad input answered with 400 and details before your code runs
  • OpenAPI 3.1 documentation at /api-docs
  • One error format everywhere (RFC 9457)
05

Built to run and to operate

It ships what operations teams need, from health checks to using every CPU core.

  • /healthz, /readyz and /metrics endpoints
  • Multi-worker cluster with rolling restart
  • Graceful shutdown on SIGTERM
  • Test server that runs without a real network
06

Screens, AI agents and shared editing

Beyond APIs, the server delivers web pages, exposes your features to AI agents and supports real-time shared document editing.

  • Server-rendered pages with built-in themes and view engine
  • UI bundling with SPA fallback and service worker
  • MCP server so AI agents can call your Features
  • Real-time collaboration rooms
Performance

Measured, not promised

Figures come from our internal benchmarks on an Apple M1 Pro (Node.js 24), with the load generator on the same machine and no database, so they measure the framework's own cost. Results on your hardware and workload will differ.

Secured GET (security stack + JWT + validation) vs Express 5
1.16x to 1.57x
At 64 connections: 15,773 vs 13,544 req/s on macOS and 17,889 vs 11,391 req/s on Linux (Docker). CPU per request is lower too. The Express side uses an equivalent stack (CORS, rate limit, JWT, ajv).
Plain GET vs Express 5
32.8k req/s
At 64 connections it matches Express (32,756 vs 31,206 req/s), so the Feature pipeline, hooks and telemetry add no measurable cost.
WebSocket echo
62.9k msg/s
p50 1.00 ms and 16 µs CPU per message, against 59.4k msg/s with the earlier ws library (6% higher).
10,000 idle WebSocket connections
200 MB
Whole-process RSS, about 10.4 KB per connection against 19.7 KB with the earlier ws library. Idle CPU 2%.
4-worker cluster (small JSON)
88.0k req/s
Against 35.8k req/s on a single process. A 100-row JSON response goes from 15.1k to 50.9k req/s.
HTTP/2 vs HTTP/1.1 (small JSON)
46.1k req/s
Against 36.7k req/s on HTTP/1.1 and 34.8k req/s on HTTPS (HTTP/2 with 8 streams per connection).

Figures come from CKN's own test suites and benchmarks. Real results depend on each system's hardware and data volume.

Business value

What your business gets

Own the whole stack

The HTTP layer, router, WebSocket and security middleware are written on Node.js, and the only runtime dependency is CKN Core. That shrinks your supply-chain exposure, and when a fix or a behaviour change is needed, we can make it ourselves without waiting on an outside maintainer.

Lower security risk

The standard protections, authentication, CSRF and idempotency ship with the framework and are exercised by attack tests such as path traversal and malformed headers. Every service starts from the same security baseline instead of each team assembling its own.

Faster delivery, predictable cost

Validation, OpenAPI docs, health checks and clustering are configuration, not new code. Teams spend more of their time on business logic, and when load grows you can use all the cores you already have before buying more machines.

For developers

One Feature: route, permissions and validation together

In use across the CKN stack

  • The runtime for every CKN business service (inventory, transportation and more)
  • Platform services such as identity, integration and portal
  • Operations services such as console and engine, serving both API and screens
  • Apps scaffolded with ckn init start on this framework
class OrderController extends Controller {
    constructor() { super(); this.url = "orders"; }

    create = {
        code: "SALES.ORDER.CREATE", name: "Create order", method: Controller.Method.POST, url: "",
        inputSchema: {
            type: "object", additionalProperties: false, required: ["sku", "qty"],
            properties: { sku: { type: "string", minLength: 1 }, qty: { type: "integer", minimum: 1 } }
        },
        scopes: ["orders:write"], sideEffects: "write", idempotent: true,
        process: async (session: Session) => { session.send({ success: true, data: session.input }); }
    };
}
CKN Technology

Explore the other packages

See CKN Server working on your systems

Contact us →