We build custom software in Java, Node.js and PHP. From the start we design it so that we, or another team, can maintain and run it for years.
- Commit
- Tests
- Deployment
- Monitoring
- tests passed
- deployed by runbook
- monitoring active
When nobody wants to touch the software after a few years
Many teams build software with the launch date in mind. Two years later the tests and documentation are missing, the dependencies are out of date, and the developer who knew everything works somewhere else. Every change becomes expensive, and nobody dares to update the runtime anymore.
PHP2Shell showed in October 2026 how quickly this gets serious: one day passed between the vulnerability becoming known and the first attacks. What counts then is whether someone can update, test and roll out your software quickly. That is the moment we build it for.
What we build
- Backends and web applications in Java, built with Maven and Jenkins and run on Tomcat
- Backends and APIs in Node.js with NestJS, frontends with Next.js, Qwik or Angular
- Web applications in PHP with Laravel or Symfony
- Websites and portals on Payload CMS or WordPress
- Component libraries that we build from your Figma designs
- Integrations with ERP and CRM systems over MuleSoft, with product feeds such as OpenImmo, with company directories such as Yext, and single sign on with Azure AD
- Interfaces between your systems, imports and exports
If you like, we work inside your own GitLab, and our merge requests go through your review like those of your team. The data sits in PostgreSQL, MySQL/MariaDB or MongoDB, and the backends run on Linux.
Move the mouse over a step or tap it. What happens before it and what comes after stays highlighted.
Maintainability from day one
This starts with the first commit:
- Automated tests run in the CI/CD pipeline before a deployment goes live.
- We write down architecture, interfaces and decisions while we build, not afterwards.
- Runbooks on how to deploy, back up and restore the application exist from the first deployment.
- We choose versions with long support and add their end of support to the EOL calendar. PHP 8.4, for example, gets security updates until 31 Dec 2028.
- From go live we monitor availability, errors and cron jobs.
Move the mouse over a step or tap it. What happens before it and what comes after stays highlighted.
We plan every change based on the ITIL® framework, with a rollback. More under How we work.
How a project runs
- Kick off
We clarify what the software should do, who uses it and which systems it talks to. At our office in Graz or online.
- Quote
We split the project into packages. Each has a fixed price, and the assumptions behind it are written into the quote.
- Build
You see the current state on a staging environment at all times. The tests run in the pipeline on every commit.
- Go live
After the rollout we monitor uptime and errors. You get the source code, documentation and runbooks from us.
- Operations
We take over maintenance and operations with Lobster Legacy Care, with response times in the contract.
In larger projects every package has its own fixed price. That way you decide after each package whether and how to continue.
Who builds your software
Our team is a senior backend developer, a senior full stack developer and a solutions architect, see about us. Between us we have over 15 years of experience with PHP, plus Java, Node.js and Python. You talk directly to the people who build your software and look after it later. There is no handover to a separate operations team.
What we learn about your software, we write into the runbooks and our knowledge base. That way it does not depend on one person, not even on our side.
Projects
- Online portal for company data
A new frontend and a data pipeline that merges company data from several sources.
- Healthcare company with locations in several countries
Three websites from one codebase, with appointment booking.
- Three radio stations in Austria
Websites, apps and radio players for all three stations from one monorepo.
Client names stay off the website. In a conversation we are glad to tell you more about these projects.
After go live
After launch we can take over maintenance and operations with Lobster Legacy Care. We then install the patches, handle incidents by the agreed service level and send you a regular report. The same team is responsible for code and server. If you would rather run the software yourself, that works too: we write the documentation for exactly that.
What we do not do
We do not build software for Windows desktops, applications on .NET Framework or anything that requires Windows Server.