Maintenance & operations
Updates, dependencies, backups, monitoring. One monthly price, one person to call.
- · Security updates
- · Bug fixes with agreed response times
- · Monitoring & backups
- · Monthly report in plain words
What we do.
Five things. Bookable on their own. Calmer together.
Further development
New features in small steps. Every two weeks something you can actually click.
- · Roadmap in half-days
- · Two-week rhythm
- · Tested before every release
- · No ticket theatre
Taking over a project
The old developer is gone? We read up, write it down and take over.
- · Review code & infrastructure
- · Tidy up access and docs
- · Name the risks clearly
- · Handover in 2–4 weeks
Automated releases
One button instead of stomach ache: test, ship, roll back if needed.
- · Deploy at the push of a button
- · Automated tests
- · A way back, always
- · No Friday-night heroics
The check
Look first: what is on fire, what pays off, what can wait.
- · Three-day review
- · Risks & costs
- · Prioritised list
- · Fixed price afterwards
What it costs
Check
Fixed price, agreed before we start.
Maintenance
A fixed monthly amount with an agreed hour budget.
Development
Per two-week cycle, or a fixed price after the check.
No hidden items, no minimum term beyond twelve months.
What we work with
We do not get to pick the technology — we take over what is already there. This is what we see most often.
- Web & frontend
- TypeScript, React, Next.js, Vue
- Backend
- Node.js, PHP & Laravel, Python, Java, .NET
- Data
- PostgreSQL, MySQL, Redis, Elasticsearch
- Operations
- Docker, Kubernetes, Terraform, GitHub Actions
- Hosting
- Hetzner, AWS, Azure, your own data centre
- Also this
- WordPress, Shopware, old monoliths without a name
Your stack is not listed? Ask anyway. We will say honestly if we are not the right people.
Asked often
Do you take on code that nobody understands any more?
Yes, that is our everyday work. We start with the three-day check, write down what is there, and tell you honestly what can be repaired and what is better rebuilt.
How fast do you react when something goes down?
We answer enquiries within two working days at most. For ongoing maintenance we agree fixed response times — for outages that is four hours or one working day, depending on the package.
Do we have to move our hosting to you?
No. We work where your software runs today. If a move would help, we will show you what it costs and what it saves — the decision stays yours.
Who owns the code?
You do. Everything lands in your repository, under your accounts. We rely on common open-source technology so you can replace us at any time.
Can we cancel monthly?
Maintenance contracts continue monthly and end with three months' notice. There is no minimum term beyond twelve months.
Do you come to see us?
In the Rheintal, gladly in person. Anywhere in Austria and Germany by arrangement. Remote is the default — it saves you the travel and us the time.
How do you invoice?
Maintenance as a fixed monthly amount with an agreed hour budget. Development per two-week cycle or at a fixed price after the check. Invoiced from Austria, in euros.
We are not a software company. Does this still work?
That is exactly who we do this for. You will not get architecture diagrams — you get a monthly report in normal language and a number you can call.