Automation · Software, AI and embedded

Automation, made to measure.

I build software that takes over recurring work, tailored to how you actually work: in software and with AI when the work lives in data and documents, or together with sensors, controllers and robots when something has to move. Always cleanly built, tested and documented, so the solution stays maintainable for years to come.

Software · AI · Hardware
One contact, from the document to the machine
iSAQB CPSA-F
Certified software architect
1 working day
Until you get a personal reply to your inquiry

Services

What runs by hand today should run by itself.

Every automation starts with a task a person does today. I look at how that task actually runs in your business and build the solution for exactly that. You don't adapt to off-the-shelf software; the software adapts to you.

  1. 01

    Automation in software and with AI

    For businesses in any industry

    What people say

    • Invoices and delivery notes arrive as PDFs, and we type them in by hand.
    • Every month someone spends two days copying figures from one system into another.
    • There is off-the-shelf software, but none of it fits the way we work.

    What I build

    I connect your systems, have AI read your documents, and generate results straight from your data.

    • Reading invoices, delivery notes and forms with AI and passing them on as checked data.
    • Keeping inventory, accounting and web shop in sync, and generating reports and statements from them.
    • Internal tools that model exactly your workflow, instead of one spreadsheet for everything.
    AI you can check
    The AI proposes, your software checks: every answer has to match a fixed data format or it is rejected. Where it matters, a person confirms. If you prefer, the models run on your own server.
    • AI / LLM
    • Document extraction
    • Integrations
    • Python
  2. 02

    Automation with hardware

    For machine, device and robot builders

    What people say

    • Everything runs on one industrial PC. Every new sensor means a rebuild.
    • The prototype has become a fleet. The software is still the prototype.
    • Before every release we test by hand on the device, and things still slip through.

    What I build

    I write the software that reads sensors, controls processes and stops cleanly when something fails: on embedded Linux, on an industrial PC, or distributed across several computers and robots.

    • Control software in C++ with state machines, sensors and I/O modules connected, measurement data shown in 3D.
    • System architecture for robots and fleets on ROS 2, tested on the target, built with reproducible Yocto builds.
    • Signed updates, SBOMs and vulnerability monitoring for the Cyber Resilience Act and the Machinery Regulation.
    Where my role ends
    The legal assessment and declaration of conformity stay with you. I develop safety-related components within your safety process (experience with ISO 26262), as a developer, not as a safety manager or assessor.
    • C++
    • Embedded Linux
    • ROS 2
    • Functional safety

Also

Getting existing software back under control.

Often there is a system standing in the way of automation that nobody wants to touch. I help with that too, with or without a new project.

  • Review

    Written, at a fixed price: what holds up, what doesn’t, how much work lies ahead.

  • Architecture and refactoring

    Modernised step by step while the system keeps running.

  • Takeover

    Stabilising, documenting and developing orphaned code further.

  • AI-generated code

    Pinned down with tests and restructured until your team is in control again.

How review and takeover work →

Work

What I have built.

One client project and one product of my own: one automation with hardware, one in software and with AI. Below them, the places where I gained the rest of my experience.

Eleven Dynamics GmbH Client 2023 – 2025

3D engine and distributed platform for industrial metrology

The project Fiiso was founded for.

Starting point

Every component of the metrology platform had to run on a single machine. On top of that, a digital twin needed to show technical 3D objects together with the measurement data.

Solution

  • Aliz: a custom OpenGL-based 3D engine for technical objects and measurement data.
  • Plugin framework: hardware drivers and data processing run as nodes on any computer in the network and are wired into pipelines through a configuration file.
  • Nodes declare which messages they produce and consume. The framework checks the wiring at load time and the types at runtime.
  • A node manager monitors every node by heartbeat, shuts the system down cleanly when one fails, and allows every computer involved to be reconfigured remotely.

Outcome

The platform is no longer tied to a single machine. New sensors and processing steps are added as nodes and wired in through configuration. Wiring errors show up at load time rather than during a measurement, and a failed node brings the system to a clean stop instead of passing on incomplete data.

Stack

  • C++
  • OpenGL
  • C# / .NET
  • ZeroMQ
  • Siemens I/O integration

Sivon Own product since 2025

Utility bills, automated: SaaS for private landlords in Germany

Starting point

Every year, private landlords have to turn a pile of receipts into a legally sound utility bill. Mistakes are easy to make, and few landlords are accountants.

Solution

  • A domain model instead of a form: properties, rental units, tenancies, allocation keys. The bill is derived from the data, never written by hand, with money as exact amounts in cents.
  • AI document reading: landlords upload invoices and owners’ association statements as PDFs, a language model reads them and proposes the bookings. Every answer has to match a declared schema, and the landlord reviews the proposals before applying them.
  • Modules with OpenAPI as the single contract; CI blocks any drift between specification and code. PDF generation and AI jobs run through job queues in PostgreSQL.
  • Runs on NixOS with backups, point-in-time recovery and monitoring. Architecture documented with arc42, decisions recorded as ADRs.

Outcome

Sivon is in production, and I am responsible for both development and operations. That is why, in client projects too, I plan for operations, backups and monitoring from the start.

Stack

  • Python
  • FastAPI
  • PostgreSQL
  • LLM workflows
  • TypeScript
  • Next.js
  • Typst
  • NixOS

Background

Experience that goes into every project.

Before and alongside Fiiso, I built software for these organisations, as an employee and on project assignments:

  • Miele

    since 2025

    Embedded C++ for cooking appliance control: process logic as state machines, Yocto-based embedded Linux, on-target and integration tests.

  • Carl Zeiss

    2025 – 2026

    Licence management platform in C#/.NET and C++: activation of software features, Windows services, Docker-based integration tests.

  • Bosch

    2018 – 2023

    Automated parking and autonomous driving (Level 4): functional safety to ISO 26262, a distributed platform on ROS 2, integration with the fleet backend.

  • Fraunhofer IOSB-AST

    2013 – 2015

    Helped develop several autonomous underwater vehicles: design, build, programming and testing, from the electronics to the software.

These organisations are not clients of Fiiso GmbH. I bring the experience I gained there.

Working together

Four formats, five steps.

The smallest way in is a review at a fixed price agreed in advance, of a workflow you want to automate or of software you already have. Afterwards both sides know where they stand, and you have a written result, even if it ends there.

  • Review

    Recommended first step
    Fits when
    You want to know whether and how a workflow can be automated, or you need an independent assessment of your existing software.
    You get
    I look at the workflow or the code, talk to the people involved and deliver a written assessment: what is worth doing, with what, and the effort for each step.
    Contract and billing
    Fixed price, agreed before the start. Fixed-deliverable contract (Werkvertrag): you pay for the finished assessment.
  • Project

    Fits when
    You need an automation with a clearly defined scope, such as document extraction, an interface between two systems or a device controller.
    You get
    Delivered in milestones, each ending in a working version, plus tests and documentation. Code and access stay with you from the start.
    Contract and billing
    Fixed price under a fixed-deliverable contract (Werkvertrag) if the scope is clearly described. Otherwise time and materials under a service contract (Dienstvertrag).
  • Team support

    Fits when
    Your team needs an experienced developer or architect for a while, for example in C++, embedded Linux, AI integration or system architecture.
    You get
    I work with your team on clearly defined tasks, remotely or on site in the Stuttgart–Ulm region.
    Contract and billing
    Service contract (Dienstvertrag), billed at a day rate.
  • Takeover

    Fits when
    A project has stalled, or the code is orphaned because its developer has left.
    You get
    I stabilise what is there, document it, and either continue development or hand it over cleanly to your team.
    Contract and billing
    Starts with a fixed-price review. After that, as a project or on time and materials, depending on the situation.

How it works

  1. 01

    Inquiry

    Two sentences by email are enough: which task costs you time today, or what goes wrong with your software. You get a personal reply within one working day.

  2. 02

    First call

    30 minutes, free and without obligation. If you want, I sign a non-disclosure agreement (NDA) beforehand.

  3. 03

    Quote

    You get a written quote with scope, approach and price. If the scope is still unclear, the first step is usually a fixed-price review.

  4. 04

    Delivery

    Short iterations with working interim versions you can check yourself. I record decisions in writing.

  5. 05

    Handover

    Documentation, tests and an introduction for your team. The goal: you do not depend on me.

About me

One engineer, one company, no overhead.

I’m Jonas Wallmeier. I founded Fiiso GmbH when a contract for a 3D engine turned into a company. The name stands for “finest in software”.

What draws me is software that does work on its own: autonomous underwater vehicles, automated parking, home appliances, metrology, and with Sivon even utility bills. When it is wrong, you notice, which is why it has to be right. Outside work I stay close to the hardware too: I designed the PCB for my split keyboard and set up its ZMK firmware, and I built my 3D printer myself.

You work directly with the person who writes the code: no sales layer, no hand-off to another team. The person on your first call is the same person who hands over the result at the end.

I’m based in Geislingen an der Steige, between Stuttgart and Ulm. In that region I also work on site with you, otherwise remotely, in German or English. Your contracting party is Fiiso GmbH.

Portrait of Jonas Wallmeier

Managing director

Jonas Wallmeier

  • MSc Embedded Systems, TU Eindhoven and KTH Stockholm (EIT Digital double degree)
  • BSc Computer Engineering, TU Ilmenau
  • iSAQB Certified Professional for Software Architecture, Foundation Level
  • German (native), English (business fluent)

FAQ

Before you get in touch.

The obvious questions about automation, AI and a one-person company, with straight answers.

Does it have to be a big project?

No. Often the best way in is a single task that eats a lot of time, such as typing in incoming invoices. Once that runs reliably, the next one follows. That way you see early whether the automation pays off.

Doesn’t AI make mistakes?

It does, which is why I don’t trust it blindly. Every answer has to match a fixed data format and is checked against the data you already have; anything that doesn’t fit goes to a person instead of into the system. Where it matters, a person always confirms. And where fixed rules are enough, no AI is needed at all.

Where does our data go when AI is involved?

Where you decide. The language model can run on your own server, so documents never leave the building. Or it runs as a cloud service under a data processing agreement, if your data allows that. I agree the right option with you before the start.

Much of our code was written with AI. Is that a problem?

Not in itself. It becomes one when nobody can explain why it is the way it is. Then I read it, pin its behaviour down with tests and restructure it until your team understands it again. Like any takeover, that starts with a review. I have continued development of existing codebases in appliance control, licence management and vehicle middleware, among others.

You work alone. What happens if you’re out of action?

Then nothing is stuck in a black box. Documentation, tests and recorded architecture decisions (ADRs) are written from day one, and the code stays with you. Your team or another developer can carry on from there.

Do you work on site or remotely?

On site in the Stuttgart–Ulm region, for example for workshops or tests on the hardware; otherwise remotely. I work in German or English.

What does it cost?

A review has a fixed price, agreed before it starts. I offer projects at a fixed price or on time and materials, and team support at a day rate. You get a concrete quote in writing after the first call.

Which contract type: Werkvertrag or Dienstvertrag?

Both, depending on the task. A fixed-deliverable contract (Werkvertrag) is for a result and suits a review or a clearly bounded component; a service contract (Dienstvertrag) is for the work itself and suits clearly defined tasks alongside your team. Fiiso GmbH is the contracting party and issues the invoices.

Who owns the code?

By contract, you get exclusive, unrestricted rights of use to the code I write for you. Under German law that is the most extensive form possible, because copyright itself cannot be transferred. Open-source components keep their own licences. The code stays with you from day one.

How do you handle confidential information?

If you want, I sign a non-disclosure agreement before the first call, your own if you prefer. I work in your infrastructure, repositories and tools, so code and data stay with you.

Does the GmbH rule out false self-employment (Scheinselbstständigkeit)?

Not on its own. According to a ruling by Germany’s Federal Social Court (BSG) of 20 July 2023 (B 12 BA 1/23 R), an intermediary one-person GmbH does not rule out dependent employment; what matters is how the work is actually carried out. So I clarify this with you before the start and, if you wish, support a status determination procedure with the German pension insurance (Deutsche Rentenversicherung). This is not legal advice.

What are you not the right person for?

The legal assessment and CE conformity assessment of your product, the role of safety manager or assessor, web design and marketing sites, and a large team on call. In those cases I tell you directly rather than taking the job anyway.

Contact

What should run by itself?

Two sentences are enough: which task costs you time today, or what goes wrong with your software. Within one working day you get a personal reply, straight from me.

What happens next

  1. You email me or call.
  2. I reply within one working day with questions or suggested times.
  3. A 30-minute call, free of charge, with a non-disclosure agreement beforehand if you want one.
Send an email
Email
info@fiiso.de
Phone
+49 1520 6981974
Address
Fiiso GmbH
Georg-Preßmar-Straße 18
73312 Geislingen an der Steige
Germany