Unified capability layers.
One runtime binary.
Each capability is a service in its own right — yet they ship as one process, share one philosophy, and run with zero infrastructure to operate.
Kitwork Compute
Serverless functions, APIs, scheduled jobs and background workers — each in its own sandboxed runtime with a strict energy budget. Deploy by pushing a folder. No containers, no Kubernetes.
- → 9.8ms cold start, bounded by design — no workload runs forever
- → Familiar JavaScript dialect compiled to bytecode
- → Per-tenant isolation with CPU & memory guards
continuous replication · survives node loss
Kitwork Data
Persistent state that outlives machines. A zero-allocation query layer over PostgreSQL with ACID transactions, automatic rollback, and continuous multi-node replication.
- → Fluent queries compiled in ~230ns — 20× faster than reflection ORMs
- → Node RAM holds nothing precious; the database is the source of truth
- → ACID boundaries with deferred rollback on any error
Kitwork Edge
A built-in gateway with automatic TLS via Let's Encrypt, multi-tier caching, and a zero-copy trie router resolved natively in Go — before any code runs.
- → Static & cached responses streamed from disk, bypassing the VM entirely
- → Automatic HTTPS for every domain, zero config
- → Sub-millisecond routing, independent of endpoint count
Worker
Worker
Worker
peer absorbs the load — service continues
Kitwork Cluster
Every node runs the same binary; only responsibility differs. When a node fails, its peers absorb the load in milliseconds. Performance may shrink — the runtime never dies.
- → No special servers — Gateway, Coordinator, Worker are roles, not machines
- → Lose efficiency before availability — degrade, never collapse
- → Correctness lives in the database, never on the wire
Kitwork Auth
JWT-based identity and access control built into the runtime — issue, verify and scope tokens without a separate auth service. Guards run before your handler, on the fast path.
- → Sign & verify JWTs natively, no external dependency
- → Route guards and middleware run before any handler
- → Scoped, per-tenant credentials with strict isolation
One platform. Every layer covered.
Start free, scale to a self-healing cluster — without ever changing your stack.
