Bukan Systems

Bukan Systems

Bukan Systems

Decentralized System Engineering

[ 'BUKAN' // INDONESIAN FOR 'NOT' ]
REJECTION OF SOFTWARE BLOAT.

A decentralized collective of systems engineers — no HQ, no hierarchy, operating from Bali to the global edge. We build close-to-the-metal software that is resilient, minimal, and correct by construction.

bukan /buːkan/ Indonesian, adverb

"Not." — The name is a constraint. Every decision we make is filtered through what we refuse to be: bloated, over-engineered, unnecessarily complex. We follow the physics of computing, not the trends of the industry.

NOT BLOATED // NOT OVER-ENGINEERED // NOT UNNECESSARILY COMPLEX
01 // ETHOS
01

Not Bloated.

Every clock cycle is accounted for. Every byte must justify its presence. We cut through layers of abstraction to expose raw computational truth — then build precisely on top of it.

02

Not Over-Engineered.

Simplicity is not a constraint — it is a discipline. We architect systems that are exactly as complex as the problem demands, and no more. Minimal by design. Industrial by execution.

03

Close to the Metal.

We operate at the hardware boundary — where every abstraction layer has a cost and every cost must be justified. The closer to silicon, the fewer places for failure to hide.

04

Highly Usable.

Interfaces that get out of the way. We believe great UX and systems-level rigor are not opposites — the best tools are invisible, precise, and built to be operated under pressure.

02 // OPERATIONAL DOMAINS

Kernel Engineering

Purpose-built kernels for industrial-grade automation — strict execution boundaries, deterministic scheduling, and hardware-level fault isolation. No general-purpose OS assumptions.

Bare-Metal Runtimes

Firmware and runtime environments for constrained hardware. Written in Zig and C, built to run without an OS, a heap allocator, or a network stack — only what the hardware demands.

Hardened Systems

Memory-safe drivers and high-throughput pipelines for resource-critical environments. Correctness enforced at the type system and architecture level, not patched in after the fact.

Infrastructure Nodes

Low-latency mesh protocols and decentralized coordination layers that form the reliable backbone of distributed networks — engineered to operate in degraded and adversarial conditions.

03 // APPROACH

Engineered for the Edge

We build for environments where connectivity is unreliable, compute is constrained, and failure is not an option. Hardened by necessity. Minimal by discipline.

RESILIENT AUTONOMOUS MINIMAL