We know that choosing between external software developers can be difficult and that it is very much a question of confidence. Our clients have almost always similar queries which concern our approach, experience, work quality, competences, security, workflow and people.

Quality & Security

  • How do you assure software quality?


    Every small piece of system functionality developed by us is covered by automated tests. In addition to low-level tests, we maintain a set of high-level "acceptance" tests. The latter verify whether the product works properly from a client’s perspective - and are automated as well, in order to get rapid feedback that everything works as expected after changes in the code. We will have automated tests simulating “clicking” through your web application.

    Moreover, our developers review each other's code to maintain an optimal internal design, avoiding mistakes. Code reviews and emphasis on software craftsmanship is a continuous element of our work. This way we can reduce overhead costs, minimize project failures, and remove uncertainties, as well as grow as individual developers.

  • What forms of security do you use?


    We have cyber-insurance for more than 2M $. Our organizational model minimizes the occurrence of all kinds of risks associated with the process of software development:

    • Bottom-up organization structure - all problems are solved jointly by the project team, not by the managers above, reducing communication overhead
    • Up-to-date IT equipment and tools - with secured access on several levels (e.g. two-factor authentication)
    • Remote organization - localized power or Internet connectivity failure will never affect the entire project team
    • Infrastructure in the Cloud - we use systems which perform regular back-ups and provide professional support
    • Implementation of projects using agile methodologies - applications are developed in short iterations, each culminating in a demonstration of tangible results given to the customer.

  • What tools do you use in your development process?


    Our teams usually uses:

    • Git - a flexible source control system
    • IntelliJ IDEA - the best Scala/Java development environment
    • TeamCity, Jenkins - for continuous integration and testing
    • Trello, Jira - agile project management tools
    • Confluence - an enterprise wiki for documentation and knowledge sharing
    • GitHub, Stash, Codebrag - tools for code reviews and many others... The set of tools depends on the team. Self-organization of teams and years of (commercial) experience allow us to work efficiently, even in new fields. We often consult and advise our clients on the best-fit technology in their projects.

  • How do you handle intellectual property?


    First of all, we understand that our clients’ business is their business and we appreciate and value that they let us in to find out all the details on its processes. To get a better picture we might need some sensitive information. In such cases, we sign a Non-Disclosure Agreement (NDA). Moreover, our insurance for nearly 2 mln USD covers cyber and privacy liability.

    We have our Privacy Policy and we operate accordingly to GDPR rules. All Intellectual Property Rights are transferred to the client once an invoice is paid. We are very careful about the people who join our team. These are experienced engineers with a proven work record.

    We use new equipment and update software regularly. Wherever it is possible we use a 2-factor authentication.


  • Who is in the team?


    Asia Pacific Software Technologies provides experienced development teams (software engineers, quality analysts, designers, business analysts, DevOps) to its clients in order to understand, design, andimplement the clients’ needs.

    We hire senior developers from Australia, Sri Lanka and the United States and they are fully equipped with experience and knowledge to solve every challenge fully independently.


  • How can I track progress of my project


    We usually set up a Slack or Google chat with the team and the client, so it is usually just a matter of asking about progress.

    The client also has full access to our project management tools (or we use the client’s tools). There, the client can check out the progress on the iteration or project level.

    At least once every two or three weeks we demonstrate a working version of the product with fixes and/or improvements.

    Of course, we adjust our process to meet the particular needs of each client.