The best software solutions in Switzerland were celebrated at the Zurich Convention Centre on 19 November 2024. Particularly radiant: the start-up Apriko was a double winner with a gold medal in the Business Solutions category and a silver medal in the Cloud Native Solutions category.
Have you ever wondered what payrolling or payroll actually involves? And do you already know Try & Hire? The answer is not so simple because the term “payrolling” is used for 2 different services.
Already working with an AI tool? Through Apriko’s MCP interface, it accesses your Apriko data directly, with the same permissions and checks as in Apriko itself. You work where you already work, and Apriko makes sure the rules apply.
A language model can talk, but it can’t do anything on its own. Apriko’s interface gives it what it needs: resources to look things up, such as candidate profiles, assignments and documents; tools to act, such as creating assignments or paying wages; and instructions on how to use these tools correctly. Your AI can never do more than you are allowed to do yourself. If you are not allowed to pay wages, neither is your AI.
Technically, this is called MCP (Model Context Protocol), the open standard through which AI tools work with software. Unlike a classic interface, not every connection needs its own code: the AI tool works out for itself which tools, resources and instructions it needs for your task.
✓ Open standard (MCP)
✓ Only allowed what you are allowed
✓ One connection for every AI
You ask your Apriko questions directly in Claude or ChatGPT, without switching between programs. You build an agent for a process that only exists at your company. Or you reconcile data from other tools with your assignments, timesheets and invoices in Apriko.
✓ Ask in your AI tool
✓ Automate your own processes
✓ Connect systems
Permissions, checks and logging live in Apriko, not in the AI tool. That is why they apply equally to every connection. If you are not allowed to pay wages, neither is your AI tool. Every suggestion is checked against the business rules, and every action is logged just like your own entries.
How Apriko checks every suggestion before anything happens.
At Apriko, we strive for a high degree of automation of customer processes, a fast market launch, and continuous improvement of our software. To ensure this in a demanding domain and complex software architecture, precise planning and consistent implementation from the outset are essential.
Apriko was developed as a microservice application to meet the increasing requirements of modern enterprise applications. This architecture approach provides the agility, scalability, and maintainability required by today’s software systems. It has proven its worth with major software companies such as LinkedIn, Spotify, and Netflix.
The development of modern software requires agile methods in order to be able to react quickly to market changes and ensure quality at the same time. DevOps offers the ideal solution here thanks to the close integration of development and operation.
A central design principle of Apriko’s software architecture is to automatically generate as much boilerplate code as possible or to derive logic. This allows the development team to focus more on the “what” and less on the “how” (the time-consuming detail work).
Complexity is high in modern software development, especially in microservices architectures. But what do you do to avoid errors in simple and repetitive tasks?
Share interesting content and useful information.
