APIs and Open Platform
Limina’s flexible investment portfolio management system is open, which means we embrace connectivity as something positive. The entire platform has been built to assume that any data can come from external providers – be it systems or service providers. This philosophy goes through the system design; even Limina’s Investment Book of Record (IBOR) can absorb data from external IBORs.
APIs are an essential part of enabling the open platform. We’ve taken an API-first approach, meaning any system task can be triggered or performed programmatically.
An API-first Approach
Limina’s Investment Management Platform has an API-first design. API-first means that the interface users interact with doesn’t contain any business logic. In fact, it’s just a display layer and is thin enough to run in the browser.
Instead, all logic resides in the cloud, and the user interface requests any data it needs through APIs. Since the user interface uses APIs, Limina naturally has full API coverage – anything a user can do in the interface can also be done via the API. Thanks to the complete API coverage, you can build any bespoke integration on top of the platform.
1. Easy to Extend
Since you can programmatically trigger anything in Limina IMS, the system can be extended easily to an in-house portfolio optimiser or to include additional custom classifications and analytics data from external solutions.
2. Easy to Integrate
It’s straightforward to connect it to systems upstream and downstream of Limina IMS, ensuring that all necessary data for the investment workflows can be captured in the system. Being an IBOR, Limina IMS is well-positioned to be the data hub that feeds business intelligence solutions such as PowerBI and Snowflake.
Get Away from Database-level Integrations
Investment managers can improve governance with APIs, compared to building dependencies directly to a system’s database. Compared to database structures that often change on upgrades, APIs can be kept unchanged in an upgrade even if the database models change.
APIs should never change; instead, we release a new API endpoint. We keep the old endpoint (v1) in parallel with the new (v2) for a period. In Limina’s case, this is typically 6-9 months, giving you ample time to transition. Limina’s goal is to help you focus on investment returns instead of databases and upgrades, which is why we promote APIs instead of database access.
Control your Integrated Investment Data
As an Investment Data Management Solution, Limina has vast support for data management, including checks of data going into or out of the system. With data quality controls, you can set up validation rules to run and check for data abnormalities and missing items.
We started our mission in 2014 with a blank canvas and a set of principles that we believe are critical for how an Investment Management System (IMS) should be built and delivered:
We believe an IMS should enable change by connecting to any 3rd party system or service provider. If you want to launch new funds or change your operating model, an open IMS should make that faster and more cost-efficient.
Trusting the data in the system is essential for Front Office decisions and governance in operational processes. Your team shouldn’t have to spend valuable time tracking down potential issues; the system should find and flag them automatically.
SUPPORTED BY PEERS
We believe the best customer support for Asset Managers comes when the team you work with have experience in Investment Management. Dedicated team members from the industry learn your business and can assist you most effectively.
FRONT-TO-MID & CROSS-ASSET
An IMS should be cross-asset and cover workflows from start to finish without jumping between systems. This increases productivity, allows superior oversight, and enables operational controls.