Sautner Studio ← Back to home

HOW WE BUILD

A climb up
the stack.

Every product we ship runs on one shared Kotlin codebase — from the silicon at the edge to the intelligence at the top. Here's the journey up through each layer: what we build, how we test and instrument it, and the tools we reach for at every altitude.

  1. GROUND · THE METAL

    The metal — Edge & hardware

    Where software meets the physical world. Raspberry Pi GPIO, PWM and I²C are driven straight from Kotlin through Pi4J on the JVM's Foreign Function & Memory API — sensors, actuators, and a sandboxed executor for user-defined automation, linked to the server over gRPC.

    TOOLS

    • Pi4J v4
    • gRPC
    • Protobuf
    • JDK 25 · FFM

    A deliberate JDK 21 / 25 split — a stable client runtime, a bleeding-edge hardware daemon.

  2. CORE · SHARED LOGIC

    The shared core — Kotlin Multiplatform

    One codebase, every platform. Business logic lives once in Kotlin commonMain and compiles to JVM, Android, iOS (Kotlin/Native) and WebAssembly — plus a JVM server. Platform differences hide behind expect/actual seams, state moves through coroutines and Flow, and the domain is a sealed hierarchy the compiler checks exhaustively.

    TOOLS

    • Kotlin
    • Coroutines & Flow
    • kotlinx.serialization
    • KSP
    • KotlinPoet
    • Koin

    Tested with flake-free virtual-time coroutine tests, MockK, and golden-vector checks.

  3. SERVICES · THE BACKEND

    The backend — Servers & distributed systems

    A Ktor server on Netty streams live state to every client over Server-Sent Events, backed by an embedded H2 database through Exposed. Nodes discover each other on the local network as a peer-to-peer mesh — multicast beacons with rolling RFC 6238 tokens and self-pairing — and integrate over gRPC, MQTT and webhooks.

    TOOLS

    • Ktor
    • Exposed
    • H2
    • gRPC
    • MQTT
    • SSE

    Instrumented with structured call logging, status pages and request tracing.

  4. SURFACE · THE UI

    The surface — Compose Multiplatform

    The interface ships from that same Kotlin codebase to desktop, web, iOS and Android as native Compose Multiplatform. A Material 3 design system drives every colour and type choice from semantic tokens — no hardcoded values — over a reactive view/edit architecture and a live graph-and-node layout engine.

    TOOLS

    • Compose Multiplatform
    • Material 3
    • Coil
    • Koala Plot
    • Roborazzi

    Guarded by Roborazzi screenshot-regression tests, so the UI can't drift unnoticed.

  5. SUMMIT · THE INTELLIGENCE

    The intelligence — AI, agents & retrieval

    At the top of the stack, software that builds and reasons about itself. Production Model Context Protocol servers in Kotlin, a multi-agent CI fleet that hunts bugs and opens PRs under adversarial review, and retrieval pipelines over a Qdrant vector store with cross-encoder reranking — served by local models, fine-tuned in-house when the work calls for it.

    TOOLS

    • MCP
    • Qdrant
    • Ollama
    • RAG · reranking
    • QLoRA · CUDA

    Every agent finding is confirm/refute-gated and de-duplicated before it reaches a human.

SHIP IT

From commit to signed release.

→ Build

  • Gradle · Kotlin DSL
  • Version catalogs
  • shadowJar
  • ProGuard
  • Multi-JDK

→ Package & publish

  • jpackage · .msi / .dmg
  • Android AAB
  • Linux .deb
  • Maven Central · GPG

→ Deliver

  • GitHub Actions
  • Self-hosted runners
  • AWS S3
  • CloudFront
  • Lambda

WOVEN THROUGH EVERY LAYER

Tested, instrumented, secured.

Tested

Test-driven from the start — flake-free virtual-time coroutine tests, MockK and Ktor MockEngine, Roborazzi screenshot regression, and adversarial confirm/refute gates on every automated finding.

Instrumented

Real-time state over SSE, structured call and request logging, screenshot diffs on every UI change, nightly architectural analysis, and product-usage analytics — so nothing regresses in the dark.

Secured

HMAC-SHA256 auth that's byte-identical across JVM, Android, iOS, Wasm and openssl (golden-vector tested), self-signed TLS, GPG / Authenticode / Apple notarization signing, secret guards, and CVE-floor dependency pins.

YOUR TURN

Ready to build something?

Tell us what you're building and we'll come back with a rough scope, cost, and where it sits on the stack.

Start a project