freelang.BY DOSAYGO Discuss your system

FreelangOS Micro / Embedded systems

Build the small system that must not surprise you.

DOSAYGO builds focused native systems for hardware and operations where authority, resources, failure behavior, and deployment identity need clear answers.

Discuss a technical evaluation Explore Micro

From source to hardware.
Built with Freelang. Built by DOSAYGO.

FIG. 01 / THE ASSURANCE ISLAND
A bounded controller beside your existing system An existing Linux or RTOS system connects through a declared interface to Micro. The controller supervises, validates, recovers, and records. This is a conceptual architecture. YOUR EXISTING SYSTEMLINUX / RTOSPHYSICAL I/OEVIDENCE DECLARED INTERFACE Micro BOUNDED BY DESIGN SUPERVISE · VALIDATERECOVER · RECORD SMALL AUTHORITY. CLEAR BOUNDARIES.
Conceptual architecture / deployment-specific integration
Explicit authorityFinite resourcesControlled failureInspectable evidence

01 / The first wedge

FREELANGOS MICRO

An assurance island
beside your system.

Give a small controller one consequential job. Micro is designed to sit beside an existing Linux or RTOS system and own a narrow path: supervision, command validation, recovery, or bounded diagnostics.

01

Supervise

Watch a larger system and make its health and recovery path explicit.

02

Validate

Give commands, inputs, and peripheral access a declared boundary.

03

Recover

Keep restart, failure, and safe-state behavior visible and testable.

04

Record

Retain deployment identity, resource facts, and evidence for the named configuration.

Running on real silicon

A small machine.
A visible model.

The Micro desktop makes domains, constrained memory, storage, and lifecycle behavior inspectable. It is a working demonstration of the execution model.

STM32
NUCLEO-H563ZI
NXP
FRDM-MCXN947

Physical demonstrations establish the stated board and workload. An industrial deployment begins with its own evaluation.

MICRO / OPERATOR VIEWFRDM-MCXN947
Captured Micro desktop on FRDM-MCXN947, showing Notepad and Explorer's RAM allocation map.
Captured on silicon · RAM map and file operations · 03 OCT 2026

02 / How the claim travels

KNOW WHAT YOU DEPLOY

Source. Evidence.
Image. Machine.

The important claims travel with the exact source, compiler, configuration, board, image, and workload that produced them.

01

Declared authority

What the subsystem can touch, communicate with, and control.

02

Bounded resources

Flash, static RAM, stack, arena, and deployment costs for the case at hand.

03

Hostile cases

Fault injection, invalid inputs, controlled failure, reset, and recovery observations.

04

Exact identity

Image hashes, compiler provenance, configuration, and retained regression evidence.

Evidence is configuration-bound. Image identity and observed behavior do not establish certification, secure boot, worst-case timing, or field reliability for another deployment.

Discuss an evidence review

03 / The manufacturing stack

FREELANG / FREEDOMLANG

One language.
Several kinds of machine.

Freelang is the language, compiler, and assurance tooling beneath these systems. Its application capabilities and constrained execution profiles share a deliberate model: make important effects visible.

01 /

Native hosts

Direct ELF64, Mach-O, and PE32+ output for Linux, macOS, and Windows. No VM, JIT, or LLVM pipeline. Feature-selected runtime helpers.

LINUXMACOSWINDOWS
02 /

Embedded systems

Cortex-M execution with bounded domains, declared authority, resource accounting, and deployment identity for the selected configuration.

CORTEX-M33MICRO
03 /

The browser

WebAssembly through a finite declared host surface. External capability connects through explicit protocols and browser agents.

WASMBROWSER AGENTS

The language underneath

Conditions are data.

Missing files, timeouts, and permission failures are named world states.

Bugs fail loudly.

Broken bounds, corrupt layouts, and impossible states terminate.

Foreign code stays outside.

Native foreign capability lives in separate processes behind bounded protocols.

04 / Explore the work

All writing

Real software.
Open to inspection.

Native and browser applications make the stack tangible. Cross-platform suites, stress collection, differential backends, and release evidence support its continued development.

LIVE APPLICATION / WASM

Radio Globe

Aircraft and ships on a navigable Earth. Freelang decoders run in the browser, with a replay available without a receiver.

Open the globe APPLICATION / NATIVE + WASM

Doom in Freelang

A complete Doom-format engine with native and browser entries. Bring your own WAD; its bytes stay local.

Play the browser build TECHNICAL FIELD NOTES

No assembler.
No linker.

Follow source and IR to exact ELF bytes. A closer look at the compiler's direct executable output.

Read the deep dive

05 / Work with DOSAYGO

START WITH ONE CONSEQUENTIAL JOB

Start with the subsystem.
Earn the platform.

Send us the requirements for the subsystem that matters. We will assess whether Micro can satisfy them, and define the evidence needed to decide.

Discuss your system