Home · About

LL BERK — founded for sovereign software

"LL" = Low Level. We are a technology company working to replace the foreign middleware inside safety-critical systems with a sovereign domestic alternative designed to produce certification evidence.

Our story

It started as a language — and became a stack

It all began with the need for something solid, strong and masterfully built. In a safety-critical system, software being "mostly correct" is not enough; it must give the same answer to the same input — every time, on every machine. We chose to solve this at the root rather than with a framework: a systems programming language where determinism is not a property you test for afterwards, but a contract declared in the language and checked by the machine — BERK, with a fully bilingual (Turkish/English) syntax, readable in the engineer's native language and provable by the compiler.

As the language matured, one thing became clear: determinism needs a carrier. A provable program must run on a provable foundation. So the project first diversified into a hard real-time engine — the model-checked Hard RT Core, and on top of it a pure-Rust DDS/RTPS networking stack, wire-compatible with Eclipse CycloneDDS and eProsima Fast-DDS. The claim of "deterministic software" now rested on a single, unbroken chain of evidence from the language down to the wire.

The process continued in the same spirit: the same core gave rise to a real-time operating layer (BERK-RTOS) and a bit-identical deterministic digital twin (Berk DT); the safety mathematics of ten critical sectors was built onto one stack. Today, five products are layers of a single idea: do not trust software you cannot prove.

Mission

To replace the foreign middleware inside safety-critical systems with a sovereign, deterministic and evidence-producing stack — from the language to the network, from the operating layer to the digital twin.

Vision

A country that proves its critical infrastructure with its own software; systems that are not "seemingly working" but provably working — with that standard written here.

Five layers, one chain of evidence: BERK Language (deterministic, bilingual systems language) · BERK DDS (pure-Rust RTPS stack, wire-compatible with CycloneDDS/Fast-DDS) · Hard RT Core (model-checked hard real-time kernel) · BERK-RTOS (deterministic tick) · Berk DT (bit-identical digital twin).
The HİT-30 Partnership Model

You lead; we raise the technology score

BERK is a horizontal enabler (middleware), not a standalone product. In a HİT-30 application, the lead applicant is a domestic firm building a product in a priority area; LL BERK joins as the technology/software partner, raising the application's localization and technology-readiness score.

Joint R&D

Co-developing domain-specific safety math and deterministic modules.

Pilot integration

Low-risk, incremental pilot migration into your existing ROS 2 / DDS architecture.

Licensing

Commercial licensing of the core technology into your product.

Subcontracting

Taking on development responsibility for critical software components.

RoboticsADAS / MobilitySpace Telecom 5G/6GMedical
Reference Project

Live, browser-based proof

BERK — Deterministic Digital Twin: a live sample application demonstrating deterministic execution and the DDS data plane. A 12-demo gallery, hash reconciliation and the CPU ≡ GPU ≡ browser showcase.

Transparency principle: we state our technology maturity as it is — components are validated in a lab / representative environment (≈ TRL 4); this is not formal certification evidence. Our position: designed to produce certification evidence; not yet qualified. An evidence roadmap is in place.

Let's build together

Joint R&D, pilot integration, licensing or subcontracting — let's discuss the model that fits you.

Contact us