Software support and maintenance
Your developer left, the agency moved on, or the in-house team got smaller, and the product still has to work tomorrow. We take the whole product over: the mobile apps, the website or web application, the servers and the release process. One team answers for all of it, with a technical lead who talks to you about priorities.
Who this is for
Most products are several systems that fail together: an app, its backend, a website, a server. Support works when one team can see all of them and has the authority to act.
- Your developer or agency has left, and nobody knows how the product is built and deployed
- App, backend and servers are maintained by different contractors who blame each other
- You need a technical owner for the product, not another person waiting for tasks in a tracker
- You have no in-house engineers and need someone responsible for the technical side
- Updates keep being postponed and the product is falling behind
- Customers notice problems before your team does
Choose the support you need
Mobile app support
One team for a live mobile product: iOS, Android, backend, infrastructure and both store reviews. Abuk has been with us since 2018, MemoWord since 2019.
Website support
Fixes, updates, performance and security for websites and web apps, including projects taken over from other developers.
Server support
Linux server administration: web servers, databases, tested backups, updates, monitoring, SSL, mail and moves between hosting providers.
DevOps
CI/CD pipelines, containers, cloud and VPS infrastructure, separate environments and monitoring, set up so that releases become routine.
Server migrations
Moving live sites, databases, mail and DNS to a new server or host while visitors keep buying and email keeps arriving.
Taking over a product when the team has left
When a developer or an agency leaves, the product rarely comes with instructions. Before we promise anything, we look at everything it quietly depends on: the code and how it is built, store and hosting accounts, domains, signing keys, payment and email services, and who each of them is registered to. You get a written description of each part and what the first months will involve. Then we take over the role the previous team had, including a technical lead who sets priorities with you instead of waiting for tickets. Sometimes the honest conclusion is that rebuilding a part costs less than supporting it, and it is better to hear that at the start than after a year of patching.
- Inventory of code, accounts, keys, domains, servers and third-party services
- Report on the condition of each part and the main risks
- A plan for the first months, in order of priority
- A technical lead on our side who owns priorities and talks to the business
- Access and ownership moved to your company
One team for the whole product
When the app, the backend and the servers are supported by different people, every incident starts with an argument about whose problem it is. We take responsibility for the whole chain, from the app on the user’s phone to the database on the server. A failed payment, a missing push notification or a slow page is traced through every layer by the same engineers, and you get one explanation of the cause instead of three partial ones.
- One contract and one point of contact for all systems
- Incidents traced across app, backend and infrastructure
- A written cause for every incident, not just "fixed"
- App releases and server changes planned together, so they do not collide
Support and development together
Support and development are usually the same team: one part keeps the current version healthy, another builds the next one. Small improvements that never justify a separate project are done within support, and larger features are estimated separately. Engineers who fix incidents know the code they are extending, which makes both jobs faster.
- Small changes done inside the support scope
- New features estimated and planned alongside support
- Regular reports on what was done and what is coming next
- Response time agreed per product, depending on what it does
How support starts
Introductory call
You tell us what the product consists of, who built it and what worries you now. We tell you which parts we would look at first.
Audit
We review the code, accounts, hosting and deployment. You get a report on the condition of each system and the risks we found.
Scope and terms
We agree what is covered, the response time for each type of issue and the monthly scope. You get a proposal with a price for that scope.
Handover
Access, keys and documentation are collected in one place, monitoring is set up and the urgent problems from the audit are fixed first.
Ongoing support
Monitoring, fixes, updates and releases within the agreed scope, with regular reports on what was done.
What we support
Mobile
- Swift
- Objective-C
- Kotlin
- Java
- React Native
Web and backend
- PHP
- Laravel
- Yii2
- WordPress
- Ruby on Rails
- Node.js
- Python
- Vue.js
- React
Infrastructure
- Linux
- nginx
- Apache
- MySQL
- PostgreSQL
- Docker
How you can pay for support
Monthly support plan
A fixed monthly scope agreed after the audit: monitoring, updates, fixes and a set volume of small changes.
Dedicated team
Engineers assigned to your product who handle both support and the development of new features.
Hourly, on request
For products that need occasional help: individual fixes, updates or consultations, billed by the time spent.
Reviews
We treat each client and his project with love.
Revol team continues to streamline the client’s development capabilities through their high-quality work and reliable support. They communicate effectively and exhibit a strong understanding of the client’s needs and business.
Tomas
The work from Revol, have fully met expectations and satisfied the client. Their fresh approach and ability to remain available for support have been valuable assets. Customers can bring them on for a communicative, client-oriented team to achieve their goals with.
Andrey
Frequently asked questions
Can we order support for only part of the product?
Yes. Each kind of support works on its own: only the mobile apps, only the servers, and so on. Combining them makes sense when the parts depend on each other and incidents cross the boundaries between them.
What response time do you offer?
It is agreed per product and depends on what the product does. A service that processes payments and an internal tool do not need the same guarantees, and paying for the stricter one without needing it is wasted money.
Do you support products built by other teams?
Yes, most support projects start that way. We begin with an audit and tell you honestly what condition the product is in before committing to a scope.
Can you replace our development agency on a live product?
Yes. We agree a handover period with the outgoing team if they are still reachable, collect access, keys and documentation, and ship the first release ourselves to prove the build and deploy chain works. After that we carry on with support and development as the team responsible for the product.
Who owns the accounts and access?
You do. Store accounts, domains, hosting and repositories should be registered to your company, and we work with access you grant. If they are still held by a former contractor, we help move them to you.
What do we see each month?
A report on incidents and their causes, updates applied and changes made, plus the risks coming up, such as a store deadline or a framework version reaching end of life.
What happens if we decide to stop?
Everything stays yours: code, access, documentation and the notes made during support. We hand the product over to the next team in an orderly way.
Tell us about your project
Describe the task in a few lines. Within one working day we reply with questions or a first view on scope and cost.
Prefer email or a call?
welcome@revolsource.com
+38 097 662 23 20
Revol Software OÜ, Tallinn, Estonia. Our team is distributed around the world.
Join our team
Send your CV to career@revolsource.com