We build it end to end
A defined scope, delivered in releases you can test. We own delivery from discovery to go-live.
Best for a new system or a rebuild
ServicesAudit and advice
We audit the applications and ERP your business runs on, and tell you what is sound and what is at risk.
A technical audit with a fixed scope. We look at the architecture, the security basics, the performance, the upgrade and end-of-life risk, the health of the integrations and what the systems really cost to run. You get a report with the risks ranked and a roadmap in order of priority. Both are yours to keep, whoever you hire to act on them.
Request a quoteWhat you get
What we hand over
- 01
A map of your systems
One document that shows every application, server, database and integration in scope: what each one does, what it runs on, which version it is and who holds the access.
- 02
A findings report with the risks ranked
What is sound and what is at risk in the code, the data and the hosting. Each finding is written in plain words with its evidence and marked as high, medium or low risk, so a manager can read it without a developer beside him.
- 03
The real cost of running it
What you pay each year for hosting, licences, support and the people who keep the systems alive, set next to what each system does for the business. Cloud resources that are paid for and not used are listed.
- 04
A roadmap in order of priority
What to fix first, what can wait and what to leave alone. Each item names the risk it removes. You can give the roadmap to your own team, to your current vendor or to us.
How it works
What the audit looks at
The audit is done by engineers who build these systems and take over ones that other teams have left. One audit can cover ERP, web applications, mobile apps and the integrations between them.
- 1Code and architecture. How the system is put together, how hard it is to change, and what a code checking tool such as SonarQube reports. We also look at what is documented and what is known to only one person.
- 2Security basics and hosting. Who has access, how servers are patched, whether backups exist and can be restored, and how the system would be recovered after a failure. This is a review of good practice, not a penetration test.
- 3Performance. Where the system slows down as users and data grow, and what the servers and the database show under load.
- 4Upgrade and end-of-life risk, and integrations. Which versions are no longer supported by their makers, how far the system is from the current release, and whether the links to other systems fail without anyone noticing.
Your options
Your options, compared honestly
- Alternative
Waiting until something fails
Costs nothing today, and many systems do run for years untouched. When an outage or a data loss comes, the review happens anyway, under pressure and at a much higher cost.
- Alternative
Asking the vendor who built it
They know the system best and can answer fastest. It is hard for any team to judge its own work, so the weak points are the least likely to be reported.
- Alternative
A penetration test only
A penetration test, a controlled attack that looks for security holes, is worth doing and is sometimes required. It covers security only. It says nothing about cost, upgrades, performance or how hard the code is to change.
- With KTree
A full audit with KTree
From the architecture to the invoices, by a team that builds, supports and takes over these systems. The report and the roadmap are yours, whoever does the work afterwards.
Technology
What we build it with
- SonarQube (code checks)
- Load testing (JMeter)
- AWS
- Linux servers
- Odoo
- Web and mobile applications
Ways to work with us
A project, a team, or support for what you already run
Our engineers, your roadmap
Odoo, React, Node, React Native, AWS and PHP engineers who work as part of your team, month by month.
Best for a product that keeps growing
Keep it running
Maintenance, upgrades and urgent fixes for ERP, web and cloud systems, including ones we did not build.
Best for a system already live
Related reading
From our engineers
- ArticleNginx Performance Optimization
- ArticleMagento Load testing using Jmeter
- ArticleServer Exploitations what need to be done after it?
- ArticleLiferay Upgrade - Missing Steps in Liferay Documentation
- ArticleSecuring Your Node.js API Backend Services with Helmet
- ArticleDo I really need To Increase WordPress Security & Protect Blog From Hackers
Before you ask
Questions about Application and systems audit
Short, straight answers. Anything else, ask in the form below and an engineer will reply.
What access do you need for the audit?
Read access to the source code, the hosting account, the database and the monitoring, and an hour or two with the people who run the system. We do not need to change anything on the live system.
Is this a security penetration test?
No. We review the security basics: access, patching, backups and settings. A penetration test is a separate exercise by a specialist security firm. The audit will tell you if you need one.
Can you audit a system another vendor built?
Yes, and that is the usual case. We audit the code, the data and the hosting, and tell you what is sound and what is at risk. If you then want us to take on support or the next phase, we can.
Do we have to hire KTree to fix what the audit finds?
No. The report and the roadmap are yours to keep, whoever you hire to act on them.
How long does it take, and what does it cost?
Both depend on how many systems are in scope. The scope is fixed before we start, and the price and the report date are given to you in writing.
Request a quote
Tell us what you are building.
A senior engineer replies within one working day.
- 1An engineer reads it. Not a sales desk.
- 2A short call. To understand the scope and what you run today.
- 3A written estimate. Scope, team and timeline on paper.
- Sales
- +91 77025 00973
- Office
- +91 40 6674 7261
- info@ktree.com
- Address
- Sanali Info Park, Road No. 2, Banjara Hills, Hyderabad 500034