Technologies
We Build With
Proven Technologies Behind Every Platform We Build.
The technology you choose today can shape how your platform performs, scales and evolves over time. It also affects your operating costs, access to skilled engineers and flexibility to change development partners in the future.
For this reason, we use technologies that are widely adopted, well supported and backed by a strong pool of skilled engineers. This approach provides a reliable technical foundation while helping ensure the platform remains maintainable, extensible and adaptable as your business and technical requirements evolve.
Every technology listed below is used in production by our in-house team. Development is managed internally, with no outsourcing or subcontracting.
Web & Mobile
Applications
Web and mobile applications provide the primary interface between your business, customers and staff. Their usability and performance directly influence the user experience, making the underlying technology an important part of the development decision. We focus on responsive, reliable experiences that work across devices and suit real-world usage. The technology is selected based on the application’s requirements, expected lifespan and the skills needed to maintain it over time.
Our preferred choice for large, long-term business applications. Its structured architecture promotes consistency and makes the application easier to maintain as development teams evolve.
Used where greater flexibility is required in the user interface or where React expertise is already available within the client’s team. Major technology companies back both Angular and React and provide long-term support, giving confidence in their continued implementation.
Adopted when the application needs to support both iOS and Android without building two separate codebases. This helps reduce development time and cost while maintaining a consistent experience across both platforms.
Used when applications require deeper hardware integration or platform-specific functionality. This provides the control required for applications where a cross-platform approach is not appropriate.
Backend & Integration
The backend manages the core business logic behind an application, including its rules, calculations, permissions and integrations. As these functions directly affect how a system operates, we choose backend technologies for their ability to support long-term performance, security, integration and scalability.
For backend and integration development, we use:
Our primary choice for Australian mid-market and enterprise applications, particularly where performance, security, long-term support and integration with the Microsoft ecosystem are important. Our Microsoft-certified developers and Azure architects provide strong in-house expertise across this stack.
Used when a system needs flexible integrations and the ability to scale different parts independently. REST APIs make it easier to connect with ERP, accounting, CRM and customer systems, while microservices and Docker support independent scaling and consistent deployment across environments.
Selected according to the type of application and the client’s existing environment. Python is well suited to data processing, automation and AI, while PHP and Laravel are practical for lighter web applications or projects that already use a PHP environment.
We also favour the simplest technology stack that meets the project’s needs, rather than introducing unnecessary complexity.
Data & Reporting
Most businesses have plenty of data but still struggle to get clear answers from it. When information is spread across multiple systems or does not align, even simple reporting can take significant time to produce. We therefore choose data technologies based on the existing environment, the reporting needs and how the data needs to be managed as the system grows.
For data and reporting, we use:
Our primary choice where .NET and Azure are part of the technology environment, particularly for Australian enterprise applications where SQL Server skills are already widely available.
We use these when the project requirements or hosting environment make them a better fit than SQL Server. Regardless of the database selected, how the data is structured has a greater impact on long-term performance.
Used when operational and executive teams need access to operational reporting and dashboards without relying on developers to answer every new business question.
Used when data from multiple systems needs to be brought together before it can be analysed and reported on effectively.
Cloud & Infrastructure
Where a system runs can affect its uptime, operating costs, security and data residency. For many Australian businesses, keeping data within Australia is a requirement, so cloud infrastructure needs to be selected with this in mind.
For cloud hosting and infrastructure, we use:
Our primary cloud platform, particularly for clients that require data to remain in Australia. We use Australian Azure regions for data residency and managed services to reduce ongoing server maintenance. This is supported by our Microsoft Certified Partner status and in-house Azure expertise.
We use AWS when a client already has its systems and infrastructure invested in AWS or when a particular AWS service is better suited to the workload. This allows us to work within an existing environment or select AWS where it provides a better fit for the project.
We use these for lighter solutions and mobile-focused applications where their capabilities are better suited to the scale and nature of the project. We are a Microsoft Certified Partner and an AWS Partner, so both platforms are supported as established capabilities rather than offered as token options.
It is built into how we deliver, rather than offered as a separate service. Automated build and release pipelines ensure changes are tested and deployed consistently, while infrastructure as code allows environments to be rebuilt reliably. Clients can also access Azure DevOps boards to track progress in real time, rather than relying solely on periodic status reports.
We also provide the supporting cloud services required to run an application in production:
- Storage: Azure Blob Storage and Amazon S3
- Transactional email: Amazon SES and SendGrid
- SMS: ClickSend
- Workflow automation: Microsoft Power Platform, where a fully custom solution is not necessary
Content Management
Not every website needs to be fully built from scratch. When your team needs to add or update content themselves, a content management system (CMS) makes this much easier. The right CMS depends on your business needs, from design flexibility and ease of use to more advanced content and permission requirements.
For content management, we build on these CMS platforms:
Our primary choice for most websites, as it is flexible, easy for teams to learn and supported by a broad ecosystem that suits a wide range of requirements.
Used when design flexibility is important, and the website needs to launch sooner, without complex functionality.
Chosen when marketing and CRM need to work together.
Used for organisations already working with these platforms, particularly in government and education, where accessibility and permission requirements are stricter.
Used when content needs to support web, mobile and third-party applications from one place, without tying the front end to the CMS.
eCommerce
The right eCommerce platform depends on how a business sells and what it needs from its online store. A business selling directly to consumers has different requirements from a B2B business managing contracted prices and customer-specific orders. The platform choice matters because changing platforms later can be costly and disruptive.
For online stores, we build on these eCommerce platforms:
Used by retailers that need to launch quickly while keeping operational overhead low.
A practical choice for businesses already on WordPress that want content and eCommerce managed in the same environment.
Used for larger catalogues and more complex requirements, such as customer-specific pricing, customer groups and business integrations.
Considered when a bespoke .NET-based platform suits an existing Microsoft environment, particularly for B2B and wholesale businesses already operating on .NET.
Beyond the storefront, we connect eCommerce platforms with ERP, inventory, POS and accounting systems, so stock and pricing stay accurate without teams maintaining the same information in several places.
AI Solutions
AI is a powerful tool, but we use it where it provides a clear business benefit.
It can help speed up development and testing, helping you bring products to market faster, while our engineers remain responsible for reviewing, testing and governing the code against your business requirements, application architecture and security standards.
When AI is part of a client solution, we focus on problems where it can make a measurable difference. This can include reducing manual data entry through document processing, finding information across large content sets, providing assistants that work with your own business content, or supporting predictive reporting. We also assess whether AI is the most appropriate approach for each requirement, rather than introducing it where a simpler and more reliable solution is available.
Design &
User Experience
Designpluz started as a design business in 2008, and that experience continues to shape how we approach software development. Design is not simply a stage before development; it helps us understand how a product should work and whether the proposed solution is worth building before development begins.
We use Figma and Adobe XD to create wireframes and interactive prototypes that allow you to experience and refine the product before development starts. Changes are far easier to make at this stage than after the system has been built, helping reduce rework and avoid costly changes later.
How we choose
Our technology choices are guided by what will keep your platform scalable,
maintainable and flexible over the long term. We focus on four principles:
1. Built for change
We architect new builds around the MACH principle:
- Microservices for independent scaling;
- API-first architecture for easier integration;
- Cloud-native infrastructure for scalability and availability, with Australian data residency; and
- Headless architecture to keep the front end independent from the back end.
The goal is not to follow a technology ideology, but to keep the platform adaptable as your business changes.
2. Reuse what already works
We reuse proven components rather than rebuilding them for every project. CoreKit is our component library for common enterprise requirements such as SSO, MFA, role-based access, audit logging, dynamic forms, document management, notifications, API gateway and deployment automation. It comes with no licensing cost, allowing more of the development budget to go towards functionality that is specific to your business.
3. You own the technology
All custom-developed source code and intellectual property will be transferred to you once the final invoice is settled. The technologies we use are open source or globally supported, so you can engage another team to maintain the platform if you choose. Any paid third-party tools and their licensing costs are discussed with you before they are introduced.
4. The right solution may not always be custom
There are times when an existing software product can meet a requirement more effectively than a custom solution. When this is the case, we identify it early and recommend the most suitable approach. This keeps custom development focused on the areas where your business needs a solution tailored to its specific requirements.
