CodeLogic is installed in your own environment, whether that is on-premises or in the cloud. Behind the scenes, it runs in containers with several services cooperating. We utilize a graph database to track code dependency relationships and optimize performance.

CodeLogic works against application meta-data only. For example, it can show that a method in a class references a column in a database. It may also know the number of instructions in that method and the column type. However, it does not record a copy of the method itself, nor the contents of the column. Your code and database data are never inside the CodeLogic server.

‍

When CodeLogic scans of your application are complete, they are processed to match outbound references with the entities that are likely referenced. Sometimes, a reference will have no known matches. For example, we may see a database call referencing a table that has not yet been scanned. In this situation, CodeLogic keeps a record of the item or items it is searching for (the unscanned table). If that item is scanned in the future, the match will be made then. Data from multiple scans are brought together into a workspace. The end result is a comprehensive dependency graph capturing all the detected relationships within application code, between applications and databases, and across multiple applications through API calls.

CodeLogic software intelligence helps development teams of every size better understand their applications from a macro-view to the data-level. CodeLogic’s different visualizations and interfaces enable various parts of an organization to derive useful information about how their systems work, so they can make accurate and informed decisions across the entire enterprise.