Reinforcement for
your software team.
Experienced developers who work in your team: backend, frontend, platform and DevOps, remotely from Vienna or elsewhere in Austria. In your repository, with your tools and processes, for one project or for good. For IT service providers we deliver the development their clients are missing.
- In your tools and processes
- Frontend · backend · platform · DevOps
- Remote from Vienna / Austria
- White label for IT service providers
When it fits
Typical situations in which software teams and IT service providers bring us in.
The roadmap is fuller than the team
Features pile up, filling a position takes months. We work with you until the team has grown, or for good.
A specific kind of experience is missing
Event streaming with Kafka, workflows with Temporal, Kubernetes, infrastructure as code: knowledge you don't build up for a single project. We bring it and pass it on to your team.
The platform slows the team down
Builds take long, local environments differ from CI, deployments are manual. We rework monorepo, toolchain and pipelines so only what changed gets built and tested.
A legacy system has to be replaced
Alongside day-to-day work, nobody has time for the step-by-step replacement of a system that has grown over the years. We take on the rebuild, the team stays on the product.
Your client needs development
You advise on processes, ERP or security, and your client needs software and someone to run it. We deliver that part, under your name or as a named partner.
Someone has to run it
After launch you need monitoring, backups, updates and someone who responds. We take over operations or set them up with your team.
We work as part of your team, not as a black box next to it.
Part of your team
We work in your repository, with your tickets, reviews and processes. Decisions about product and architecture stay where they belong.
What stays with you
- Product, roadmap and priorities
- Architecture decisions — we make proposals
- Processes, tools and definition of done
- Code, repositories and access
- Project management and direction
- For IT service providers: the client and the contract with them
What we bring
- Development in backend and frontend
- Platform, CI/CD and infrastructure as code
- Event-driven architecture and workflows
- Code reviews and knowledge transfer in the team
- Documentation, so the knowledge stays
- Operations, monitoring and backups if you like
What we don't do
- Swap people without your agreement
- Knowledge that only we have
- Our own tools against the team's will
- Approach our partners' clients, even after the project ends
Good reinforcement shows in a team that keeps going on its own afterwards: with documented code, explained decisions and no dependency on us.
Two models
Depending on whether you need people in the team or want to hand over part of the project.
Working in your team
We work in your team, following your priorities and processes. That's how we have worked at xtype since 2023, and how we worked at Wiener Wohnen Kundenservice.
- Work in your repository and ticket system
- Planning, dailies and reviews as needed
- The same people, not rotating resources
- Scope as agreed, adjustable
- Remote from Vienna / Austria
One part under our responsibility
We take on a defined part — a service, an integration, the platform or operations — and deliver it finished. For IT service providers also under your name.
- Scope and interfaces firmly defined
- Fixed price for a clearly defined scope
- Automatically tested and documented
- White label or as a named partner
- With operations if you like
Mixed forms are common: first a defined part, then work in the team — or the other way round.
How we get started
You don't need a framework agreement to get going. We start with a concrete task and see whether it works for both sides.
- 01
Getting to know each other
A conversation about your team, your stack and where things are stuck.
- Free and without obligation
- Clarifying whether stack and way of working fit
- Honest feedback if we're not a fit
- 02
Agreeing on a starting point
We look at code, setup and backlog and propose a starting point: a task, a service or part of the platform.
- Access to repository and documentation
- A concrete first assignment
- A clear statement of what we don't cover
- 03
Working together
We work at your pace: tickets, reviews, releases.
- Fixed contacts, not rotating resources
- Work in your tools and processes
- Automatically tested and documented
- Knowledge transfer through reviews and pairing
- 04
Operations or handover
If you like, we take over operations for good — or hand over to your team.
- Monitoring, alerting, updates and backups
- On your infrastructure or on Exoscale
- Documented architecture and operating processes
- Complete handover possible, no lock-in
What we cover technically
Twenty years of software development and operations. We work with the stack your team has chosen — this is what we bring most often.
- backend =
- JavaKotlinSpring BootNode.js & NestJSPostgreSQL
- frontend =
- ReactTypeScriptNext.js
- integration =
- Kafka & AvroTemporalREST & APIsLegacy systems
- infrastructure =
- KubernetesPulumiAWSExoscale
- delivery =
- CI/CDGitOpsNxmise
We work with your stack
We adapt to the repository, conventions and tools your team uses instead of bringing our own.
We take over existing systems too
When a system is running and nobody is responsible any more, we get familiar with it and take over maintenance and further development.
We stay after launch
Operations are part of what we do. If you like, the people who built it also run it and are responsible for keeping it running.
In xtype's team since 2023
xtype builds a SaaS platform for ServiceNow governance. Since November 2023 we have been working in the development team: event-driven microservices, Temporal workflows, Kubernetes on AWS, plus Nx and mise for build and toolchain.
- kafka · avro
- temporal
- kubernetes · aws
- nx · mise
What teams ask first
Do you need to know our stack already?
Java, Kotlin and TypeScript are our everyday work, which covers most teams. If a stack doesn't suit us, we say so before we commit.
Do you work remotely?
Usually remotely from Vienna or elsewhere in Austria. Whether and how often we're on site is agreed per project.
How is billing handled?
Work in your team is billed according to the agreed scope; defined sub-projects preferably at a fixed price. For IT service providers we invoice you, not your client.
Why not just freelancers?
If that works well, you don't need us. The difference shows once holiday cover, responsibility for operations or several topics in parallel come into play — that's where individuals are at a structural disadvantage.
For IT service providers: will you take my client?
No. The contract is between you and us, the client relationship stays yours, and we don't approach your clients — not even after the project. If you like, we put that in writing.
Who is responsible for what?
We are responsible for the code we write and, where agreed, for operations. For sub-projects the scope is firmly defined, so it's clear who is responsible for what if something goes wrong.
How quickly can you start?
That depends on our workload, and we tell you honestly instead of promising a date we can't keep. To assess things we usually need just one conversation and access to code and documentation.
Is there a framework agreement?
Not as a prerequisite. We start with a concrete task. If the collaboration works, it can later move to a framework agreement with fixed terms and a confidentiality agreement.
Let's talk about your team
No sales pitch, no framework agreement. A conversation about where your team is stuck — and an honest answer on whether we can help or not.
Alexander J. Gassner, MScmanagement · your contact