Aranei is a business process information management system. It is specifically designed to facilitate an existing business process by serving information, instead of forcing a client to redesign a process to serve a system. ​Aranei is built on open-source components and open web standards, so your data is always under your control both now and in the future.


Why Aranei?

Many Small and Medium Sized businesses in the medical (IVF/ART) and pharma (GxP) domains have started with a small number of partners/employees yet have soon grown into a multi-department
During such growth sprints, IT systems are often introduced as part of an equipment procurement package.
Also the use of spreadsheets, in-house developed local databases (MS Access) or traditional client-server applications are very common in these circumstances.

This way of working can quickly reach a turning point where blocking or conflicting parallel actions by users start to increase the margin of error in operating the system. Client-server apps have a limited lifespan in terms of supplier support which is caused by the buildup of technical debt (outdated dependencies, network protocols being updated, etc.). Monolithic client-server applications especially offer very little functionality to other applications to tie into their business logic and
perform direct data operations or other forms of integrations. After a while workarounds and errors start to pile up (i.e. sorting on wrong columns, references no longer existing, changes in directory structure break links between sheets/exports, etc.).

Replace legacy applications without altering the process or the information structure

Solution: Aranei

Aranei is a web-based relational-database-driven system which has been in development and use for the past decade. Its precise goal is replacing the spreadsheet or legacy client-server applications but achieving this replacement without altering the process or the information structure. This improves the overall reliability and accountability of the data migration and operational use of the system.
Migrations are costly and complex. Keeping the same schema/structure between source system and archiving solution, or using the notion of a controlled copy, is a much less cumbersome approach, as a one-on-one data verification can be performed. This ensures full access to the data in its original context, using the existing metadata about the data model to define the UI elements like data tables, dashboards, reports, etc.
Client organizations can still use the information within the app in the structure and processes they are accustomed to. 


Speed of implementation through a standardized process, from project start to initial import within 4 weeks
Predictable costs through modular components
Data and application functionality under the client’s own control