Frankfurt am Main, Germany

Made in Germany.
Built like Silicon Valley.

Digital products & scalable infrastructure

reproducible, documented and ready for handover

German contracting partner
Frankfurt
Defined scope & acceptance criteria
Fixed price
Reproducible & ready for handover
IaC + GitOps
Maintainer for FluxCD and other packages
nixpkgs

Scaled Platform Delivery

A Kubernetes platform your team can operate independently.

We build and stabilise production-ready AWS and Kubernetes platforms – with a fixed scope, verifiable acceptance criteria and a complete handover.

Available now

From cloud foundation and networking to GitOps, observability and runbooks: reproducibly built from code, documented and handed over to your team.

Designed for

  • New AWS and Kubernetes platforms
  • Unstable or manually operated clusters
  • Platforms without a clear handover

The outcome

  • Reproducible cloud foundation
  • Kubernetes with DNS, TLS and gateway
  • IAM, secrets, storage and break glass
  • GitOps operations with Flux
  • Observability and operational foundations
  • Documentation, runbooks and handover

Three clear starting points

  1. 01

    Platform Assessment

    Create clarity

    On request

    Current-state review, target architecture, risks, delivery plan and a binding fixed-price proposal.

    1–2 weeks

  2. 03

    Platform Hardening

    Stabilise an existing platform

    Priced by scope

    Analyse, secure and automate an existing platform, then hand it over to your team in a controlled way.

    After initial review

All engagements are delivered at a fixed price. The binding scope follows the assessment.

More products

Infrastructure for documents and builds.

Explore all products

Scaled Documents

Seeking pilot partners

Self-hosted document and e-invoicing infrastructure for software vendors.

  • ZUGFeRD / Factur-X
  • HTTP API
  • CLI
  • Self-hosted
Discuss a pilot

Scaled Builds

Seeking design partners

Remote cache and distributed builds for large monorepos – entirely in your infrastructure.

  • Remote Execution API
  • Rust
  • Bazel
  • Self-hosted
Discuss a benchmark

Evidence

Built, tested and ready to demonstrate.

Every service is based on a real system. Inspect the architecture, source code and measurable results – or experience the platform in a live demo.

Reproducible Kubernetes platform

Verifiable

A complete AWS stack that can be restored from code at any time.

The reference platform covers the path from networking and IAM to Kubernetes, storage, secrets and GitOps. The same desired state can be reproduced locally on Kind and in AWS.

  • VPC, IAM, EKS and storage with OpenTofu
  • Automated DNS, TLS, gateway and secrets
  • Applications and platform services via Flux
  • Break-glass access and documented handover
< 15 min
AWS rebuild in the reference run
100% IaC
Cloud foundation and cluster
GitOps
Handover from Flux onwards

Reproducible delivery path

  1. 01 Cloud foundation
  2. 02 Kubernetes
  3. 03 Flux
  4. 04 Platform stack
AWS EKSOpenTofuCiliumFluxVaultAirflow

Document engine

Deterministic documents without cloud dependency.

Structured data is transformed into reproducible PDF and e-invoicing formats by a self-hostable Rust engine.

Same input → same output

  • ZUGFeRD / Factur-X and XRechnung
  • HTTP API and CLI
  • Static Linux builds and OCI image
RustTypstZUGFeRDFactur-XXRechnung
View source code

Remote build infrastructure

Remote cache and execution in your own infrastructure.

Worker, scheduler and cache speak the Remote Execution API and run without handing source code to an external SaaS provider.

≈ 50% faster

in our cold and warm benchmark

  • Remote Execution API
  • Cold and warm cache measured
  • Benchmark available on your workload

Reference setup: three worker nodes with 8 vCPU and 8 GB RAM each. This result describes that test setup and is not a general performance guarantee.

RustREAPIBazelgRPCEnvoy
Request a benchmark

Engineering

We do not just operate the stack. We contribute to it.

We maintain packages in nixpkgs, contribute to remote-build infrastructure and fix issues where they originate. This means fewer project-specific workarounds and systems that remain maintainable over time.

Active ecosystem work

Public projects and traceable contributions

  • Package maintenance

    nixpkgs

    Ongoing maintenance and updates for production-relevant tools in the Nix ecosystem.

    FluxCD Biome flyctl
  • Remote-build infrastructure

    NativeLink

    Contributions to components for distributed builds, scheduling and Kubernetes operations.

    Rust Scheduler Helm
  • Bug fixes and integration work arising directly from our own product development.

    Bugfixes Adapter Integration

What this changes for your project

  1. 01

    Root causes over permanent workarounds

    Issues are resolved where they originate whenever possible, rather than preserved as special cases in your platform.

  2. 02

    Evaluate changes earlier

    Ongoing involvement helps us assess relevant updates and breaking changes more thoroughly before rollout.

  3. 03

    Handover without vendor lock-in

    Open standards, public tools and documented decisions keep operations understandable for your team.

The goal is not to become indispensable. The goal is a platform that keeps running without us.
Explore the technology stack

About us

Direct accountability. No handover into the unknown.

We are an independent software engineering company based in Frankfurt, Germany. We build digital products and reproducible infrastructure – from the first architecture decision to documented handover.

Founded and technically led by Schahin Rouhanizadeh. Architecture, implementation and communication stay closely connected. Decisions do not disappear between sales, project management and rotating delivery teams.

More about us

How we work

  1. 01

    Direct technical accountability

    You work with the person making the architecture decisions and taking responsibility for their implementation.

  2. 02

    Independent and open

    We favour open standards and portable systems over unnecessary vendor dependencies.

  3. 03

    Handover is part of delivery

    Documentation, runbooks and understandable code are part of the result – not a separate project later on.

Location
Frankfurt am Main, Germany
Contracting entity
German limited company
Delivery model
Defined scope · fixed price
Engineering
TypeScript · Go · Rust · Nix

Work with us

Let’s talk about your platform.

Whether you are building from scratch, hardening an existing platform or looking for a second technical perspective: an initial conversation establishes your current state, target and the most useful next step.

New assessments by arrangement Direct access to technical accountability

Or email us directly: contact@scaliir.digital

WhatsApp Telegram Mail