Honest workers, writing software.
A software development practice based in Linz, Upper Austria, serving SMEs and startups across Austria. You see the work as it happens, you read the notes on the time we billed, and we explain the choices we made along the way.
Tools we know, ready for what you bring.
We usually start with the stack below. It's what we know best, what we've shipped most, and what we can troubleshoot at 2am if a customer calls. Every project ships dockerised behind Traefik on a Linux host, so dev, staging and prod look identical from the inside. None of it is required. If your project runs on Django, Next.js, .NET, Go, or something else, we learn the dialect and deliver in it. The default is a starting point, not a contract.
Blax Stack
What we reach for first on every new project. Battle-tested, end-to-end.
AI that earns its place in production.
We don't bolt on a chatbot widget and call it done. We integrate language models into the systems your team already uses, fine-tune on data you actually have, and automate the daily clicks that nobody enjoys. Same engineering discipline as the rest of the stack: versioned, monitored, billed by the minute.
Chatbots & conversational AI
Customer-facing assistants, internal support copilots, voice flows. Built on OpenAI or Anthropic, wired into your data so the bot answers from facts, not guesses.
Fine-tuned & custom AI services
Retrieval-augmented pipelines, fine-tunes on your corpus, prompt-engineered workflows that turn one good prompt into a reliable feature. Shipped behind your own API, not a third-party widget.
We don't build houses.
We grow trees.
A house is finished the day you move in. A tree keeps growing. We plan each season, adapt as conditions change, and grow around obstacles instead of pretending they aren't there. Efficient, professional, and visible to you at every step.
Agile development01
Plans for each season, adapted as conditions change.
Honest open dialogue02
We talk about what works and what doesn't. When production is on fire, we pick up the phone.
Read the perspectivePrecise billing03
Time tracked to the second, with a note on every minute so you can read what we did.
Read the perspectiveBe humane04
Trust and respect over hierarchy and bureaucracy.
End-user respect05
We optimise for the people who actually open the app every morning, not just the people who sign the contract.
Read the perspective
From first call to hand-over.
This is how a project unfolds with us, every time. The shape never changes, only the scope and timing. Nothing surprises you, because the iteration loop, the deploy mechanics and the billing rhythm are all visible from day one.
Step 01
First contact
Email, contact form, or a phone call. A real person reads it the same day. No chatbot triage, no sales script, no "we'll route you to the right department".
Step 02
Discovery call
A free 30 minutes. We listen, ask, and tell you honestly whether we are the right fit. If we are not, we usually know who is, and we say so.
Step 03
Scope & quote
Line by line, plain language, no "from €X" placeholders. The quote covers scope, deliverables, milestones and a clear price. Numbers we can stand behind.
Step 04
Sign-off
Contract and payment terms in writing. Both sides sign the scope before any code is written. No surprise scope changes mid-flight, only signed change-orders.
Step 05
Kick-off
Repository, project board, shared chat channel, time tracker, all set up on day one. You know who is doing what, and what is coming up next, before the first commit lands.
Step 06
Build & ship
Iterative cycles. We plan a slice, implement it, demo working code at the end, gather feedback, then plan the next slice. Time billed to the second with notes you can read on every minute.
IteratesPlanBuildDemoFeedbackrepeatsStep 07
Pre-launch QA
End-to-end tests on real data, performance under expected load, edge cases stressed. We catch the surprises in our staging environment, not in front of your users.
Step 08
Launch / Go-live
The boring deploy. Tests, then staging, then production on one click. Tuesday morning, calm coffee, deploy. The reverse-button is one click too.
Step 09
Maintain or hand-over
Stay with us on retainer for hosting, security updates and continued evolution. Or take a clean hand-over of the keys to your team. Documentation comes with either path.
Ready when you are
The pipeline every change goes through.
Boring on purpose. Every commit walks the same five steps before it reaches your users. That's how we keep deploys calm and reversible.
Commit
One concern per commit, descriptively named, signed off. A focused diff is a safer merge.
Tests
Unit and end-to-end, running on every push. If the suite is red, the merge waits.
Review
A second pair of eyes, always. Founder commits included; nothing flies through.
Staging
A copy of production with realistic data. We catch the surprises here, not in front of users.
Production
One click. Tuesday morning, calm coffee, deploy. The reverse-button is one click too.
What we believe about software.
Six beliefs that shape every quote, every commit and every contract.
01 / 06
Self-hosted by default
Our forge, our intranet, our project board, our tile server: all on our own racks. Customer data lives where we can answer for it, not on a third party's subpoena schedule.
02 / 06
Free and open source
Linux, Postgres, Nginx, the Composer and npm catalogues that built the modern web. We give back where we can, and we never ship a black box on top of someone else's shoulders.
03 / 06
Humane working process
No 70-hour sprints, no forced overtime, no panic releases. Predictable hours, real names, the same person on the call from kickoff to retirement.
04 / 06
Easy-going communication
Plain language, fewer slide decks, more shared screens. We answer the phone. We say "I do not know yet" when we do not know yet.
05 / 06
Quality first, scope second
A feature shipped poorly costs more than a feature shipped a week late. We choose right tools over familiar tools, and we name our trade-offs in writing.
06 / 06
Fairly priced, kulant by default
Quotes are line-itemised in plain language. If something is our fault, it does not end up on your invoice. Discounts that respect the customer are how a craftsman behaves.
When you're ready, we're here.
A paragraph about what you'd like to build is plenty. We'll read it, write back, and be honest about whether we're the right fit.