Skip to main content

// ABOUT

Two engineerswho ship.

Exostruction is a small engineering studio. Not an agency. No PowerPoint. When you talk to us, you talk to the people writing your code.

SCROLL

// HOW WE GOT HERE

Four chapters. Our story.

  1. 01

    MET

    We met during our vocational training — Juljan as application developer, Alexander as system integrator. Different focuses, but it became clear quickly: we like the same things. Cleanly built code. Servers that don't catch fire. And honest answers to technical questions instead of marketing speak. The shop talk during lunch breaks gradually turned into something more.

  2. 02

    FRUSTRATED

    What we liked less, we saw often enough: hour-long meetings ending with 'let's discuss this again'. Excel sheets nobody maintains but everybody trusts anyway. Consultant slides claiming to explain 'innovation' without touching a single line of code. We were convinced IT services could work differently — more direct, more honest, closer to the actual problem.

  3. 03

    FOUNDED

    So we founded Exostruction. A small studio that does exactly what we think happens too rarely in IT: listen first, build well, then bill transparently. No account manager as a buffer between you and the engineers. No technology decisions nobody can explain. We wanted a company we'd want to be a customer of ourselves.

  4. 04

    TODAY

    Today we build web applications, APIs, and Linux servers for companies that want understandable rather than over-optimized software. We're small enough that one of us writes code on every project — and big enough to handle complex systems. On the side, we build our own open-source tools like ExoVote, because we like to use what we recommend.

// WHO WE ARE

The people behind it.

JBFOUNDER · 01

CO-FOUNDER & ENGINEERING

Juljan Blischke

"Readable code is a form of respect for the person who maintains it tomorrow."

Software engineer for application development, trained at a logistics company in Bavaria. Primarily writes backend code in C# and TypeScript, but also enjoys frontend when requirements are clear.

Interested in software architecture, honest APIs, and tools that are still maintainable in five years. Built ExoVote because nobody had an open-source voting platform that was GDPR-compliant.

Likes reading about distributed systems, investing, and bad refactoring. Thinks 'best practices' are overrated when nobody explains why.

C# / .NETTypeScriptReact / Next.jsPostgreSQLAPI-DesignSoftware-Architektur
AKFOUNDER · 02

CO-FOUNDER & INFRASTRUCTURE

Alexander Kreitmair

"A self-hosted box running for three years beats any SaaS promise."

Computer scientist for system integration. Takes care of infrastructure running — Linux servers, Docker setups, CI/CD pipelines, backups.

Thinks most companies spend way too much on cloud services they could operate themselves. Has a healthy distrust toward hosted services and a good relationship with ssh.

Interested in network security, monitoring, and everything related to 'is this still running?'. Prefers command lines over GUIs.

Linux (Ubuntu, Debian)Docker / ComposeNetworkingCI/CDMonitoringSecurity-Hardening

// HOW WE BUILD

Six things that shape our work.

  1. Code that stays readable

    We write code for the people who will maintain it in two years — even if that's us. Comments where needed, variable names that make sense, functions that do ONE thing.

  2. Test what matters

    Not every helper function needs a unit test. But business logic, critical flows, bug patches — yes. We hate fixing bugs twice.

  3. Own infrastructure where possible

    Hetzner instead of AWS when requirements allow. Self-hosted tools instead of SaaS when maintenance is feasible. Cloud is great — when you know what you get and what you pay.

  4. Open source over lock-in

    We prefer tools under open licenses. So you're never in the situation where a vendor corners you. Our own products (ExoVote) are open source too.

  5. Direct communication

    No ticket system with 48h SLA in between. Slack, Signal, email, call — we respond like real humans, usually within hours during business hours.

  6. Honest estimates

    We give time estimates in ranges, not as fixed points. Software has uncertainty. We say so openly, rather than suggesting false certainty.

// YOUR TURN

Sounds like you? Let's talk.