Why Exostruction Exists
Why we founded Exostruction: custom software instead of off-the-shelf tools for small businesses, associations and freelancers.
Inhalt

We're now on LinkedIn too, as Exostruction GmbH i.G. from Regenstauf, Upper Palatinate. Time to explain properly why we exist at all.
Software that's "always been there"
In small and medium-sized businesses, associations and among freelancers, you often still find software that's always been there. Not up to date anymore, barely updatable, but still the central program running the business. The spreadsheet that should really be a database. The tool the last apprentice set up ten years ago that nobody wants to touch anymore.
And when something new does get bought, it's usually an off-the-shelf solution. You buy it because it exists, and it fits maybe 75%. The rest are compromises you learn to live with: a workaround here, a manual copy-paste step there, a process that bends itself around the software instead of the other way round.
That's exactly where we want to start. IT that actually fits what's needed, built individually instead of adapted out of necessity.
How we met
We met during our vocational training: Juljan as an application developer, Alexander as a systems integrator. Different focuses, but it quickly became clear that we like similar things. Cleanly built code. Servers that don't catch fire. And honest answers to technical questions instead of marketing talk. What started as shop talk over lunch grew into something more over time.
What kept striking us: hour-long meetings that end with "let's discuss this again". Spreadsheets nobody maintains but everyone trusts anyway. Consultant slides that claim 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.
Why we founded Exostruction
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 the client and the developers. No technology decisions nobody can explain. We wanted a company we'd want to be a customer of ourselves. That's why you get web applications, connections to your existing systems and server operations from a single source, without three more departments sitting between your request and the finished code.
What we actually do
From the first idea to ongoing operations: software, web apps, automation and IT infrastructure, mainly for small and medium-sized businesses, associations and freelancers in the Regensburg/Upper Palatinate area.
We're small enough that one of us writes code on every project ourselves, and big enough to handle complex systems too. Concretely, that means: no queue behind a junior developer who still has to understand your requirements. From day one, you talk to the person building the system and later maintaining it.
How we work
A few principles haven't changed since we founded the company, because they're the actual reason we do this.
Understand before building. We talk to you and your users before writing a single line of code. The problem needs to be clear, otherwise you solve the wrong one. Sometimes the best solution isn't software at all, but a process that just needs to be organized differently.
Start small, ship fast. First working version in weeks, not months. We iterate with real users instead of programming against a spec for months on end that's going to change anyway the moment someone actually gets their hands on the software.
Code that lasts. Clean, tested, documented, so others can work with it later, whether that's us, you, or whoever takes over in two years. That doesn't mean every small helper function needs a unit test. But the business logic, the critical flows, and every bug fix do, because we don't want to fix the same bug twice.
Our own infrastructure, where possible. We use Hetzner instead of AWS when the requirements allow it, and self-hosted tools instead of SaaS when maintenance is manageable. Cloud is great when you know exactly what you're getting and what you're paying for. For many small and medium-sized businesses, though, the fine print rarely works out in their favor.
Open source over lock-in. We prefer tools under open licenses, so you're never in a position where a single vendor corners you. If you decide you don't want to work with us anymore one day, that should be your call and not something we made technically hard.
Directly reachable. No ticket system with a 48-hour SLA in between. You talk to the people building your project, on Slack, by email, or on a call, and get a reply within one business day, usually much sooner.
Who's behind it
Two founders stand behind Exostruction. Juljan Blischke is a certified application developer and mainly writes backend code in C# and TypeScript, but also enjoys frontend work when requirements are clear. Alexander Kreitmair is a certified systems integration specialist and makes sure the infrastructure keeps running: servers, containers, networks, deployments and backups that actually come back when you need them.
In the next posts, we'll introduce ourselves in more depth. What drives us, what we're working on right now, and what we've learned from the projects we've built so far. We don't just want to show the wins, but also where we've failed and what we took away from it, honest instead of polished.
What's next
Follow us if you want to see how we make this happen. We write here regularly about the decisions behind our work, technical, honest, no marketing talk. If you have a concrete project in mind, just reach out via our contact page. We'll tell you honestly whether and how it can be built.
Frequently asked questions
Author of this article
This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.