After modernization the system is in your hands, not ours
Documented architecture, automated deployments and workshops for your team. Your people can take the system over or leave it with us, with no lock-in.
What we hand over at the end of every phase
Handover doesn't wait for the end of the project.
- 1Architecture docsModules, connections and data flows described in the repository next to the code, not in a separate document that goes stale.
- 2Working deploymentsAn automated pipeline that builds, tests and deploys the system. Anyone on the team can run it.
- 3WorkshopsSessions with your team where we walk through the code, deployments and common changes. We record them.
- 4Access and accountsRepositories, servers and third-party accounts are in your company's name, with a list of who has access.
Signs a handover went wrong
Knowledge leaves with the vendor
The docs are out of date
Accounts belong to the vendor
One person can deploy
Everything you need to develop it yourself
The same set whether we stay on or not.
Repository
Architecture docs
Deployment pipeline
Team guides
Recorded workshops
Access list
How you'll know the handover worked
We check it in practice, not on a checklist.
- 1A release done by your team
- 2A change made without our help
- 3Accounts in your company's name
- 4People who attended the workshops
Your team does the last release before handover while we just watch.
Common questions
Can you stay on for further development?
Yes, if you want. The handover looks the same either way, so you can change your mind at any time.
Our team is small. Can they cope?
We fit the workshops to the team. If needed, we stay on as backup for the harder changes.
What language are the docs in?
Polish or English, depending on the team taking over.
What if something breaks after handover?
You can use our maintenance hour package or ask for one-off help.
Tell us who will take it over
Let us know which system you're modernizing and who should develop it once the work is done. We reply within one business day.