Amalgame Lab

🟢 In production — this site runs on it

Mosaic — the web, served by Amalgame

amalgame.me · docs.amalgame.me · demo.amalgame.me · client sites

The page you're reading is served by a single native binary written in Amalgame. No Node, no nginx in front, no reverse proxy: the binary terminates TLS itself, picks the right site from the Host header (SNI), and serves everything on port 443. The HTTPS certificate is obtained and renewed by a pure-Amalgame ACME state machine (RFC 8555, Let's Encrypt) — no certbot, no subprocess.

One process, several domains, static and dynamic content (the Releases page is filled live from the GitHub API; the contact form verifies a reCAPTCHA server-side, then sends mail over SMTP/TLS). It's the ultimate dogfooding: if Mosaic didn't hold up, this site would be down.

The skeleton, as it runs here — one binary, many hosts. (Sensitive code — reCAPTCHA keys, SMTP credentials — lives outside the source, never in the repo.)

let server = SiteServer.New()

// One site = one folder. Several domains can point at it.
server.Register(["docs.amalgame.me"], "sites/docs.amalgame.me")
server.Register(["demo.amalgame.me"], "sites/demo.amalgame.me")
server.RegisterAmalgameWithContact(
    ["amalgame.me", "www.amalgame.me"], "sites/www.amalgame.me", releases,
    cfg)   // cfg = secrets loaded at runtime, not in the repo

// Native ACME per domain, then a single HTTPS listener + SNI.
server.EnsureCerts()
server.ListenHttps(443)   // :80 redirects 301 to https://

Web and distributed systems are software. What remained was to prove Amalgame goes all the way down to hardware. The test bench: a weather station built on a Raspberry Pi Zero W and its sensors (temperature, humidity, pressure), driven directly from Amalgame. The same .am you write on your machine compiles to a native ARM64 binary and runs on the Pi — no embedded interpreter, no Python layer.

The pins go through amalgame-hardware-gpio, the first package in the Amalgame.Hardware family: digital GPIO via libgpiod v2 (the kernel-blessed API, valid from Pi 1 to Pi 5), with an API shape mirroring the upcoming bare-metal MCU HAL. I2C, SPI, PWM and UART — and therefore the station's sensors — land in the next phases. The build is in progress; the ARM64 pipeline (CI + releases) is already green.

GPIO, HAL-style — the same API will read a sensor on the Pi today and a bare-metal MCU tomorrow.

import Amalgame.Hardware

let gpio = Gpio.New().AutoChip()      // detects RP1 (Pi 5) vs Pi 4-
gpio.PinMode(17, PinMode.Output)
gpio.DigitalWrite(17, Level.High)   // status LED: reading in progress

// I2C arrives in phase 2 → read a T°/humidity sensor directly.